Frontend Developer @Meta Ex @bookingcom @Flipkart
Amsterdam, The Netherlands
Joined October 2009
- Tweets56
- Following102
- Followers23
- Likes72
Wrote an article on how Amazon optimizes for page load performance. There are a lot of lessons here that are especially beneficial for e-commerce companies
blog.debugpai.com/speed-matt…
Grappling instead of landing strikes is a more humane way to physically restrain a person and resolve a conflict #wrestling #bjj
All the best with your future endeavors Ankeet. I'm sure you'll succeed at whatever you choose to do with your lively spirit 🙂
I would vote for marking it as incorrect. Destroying information gives too much power in the hands of the people who make the decision of what information is correct.
Fresh Off the press: Understanding how Apollo Cache normalizes data (using apollo devtools)
#apollo #graphql debugpai.com/learn-apollo-ca…
Aliasing Preact correctly for Server Side Rendering
debugpai.com/aliasing-preact…
#preact
I set mine up with @hashnode. I can use markdown and redirect my own domain name. So I'm not tied down to the platform. And also they help with promotion, metrics, comment system
I'm quite curious as to how you're solving i18n. Unfortunately I won't be able to make it at that time. Will this be recorded so I can watch it later?
Deepak Pai retweeted
Dead code elimination is a process wherein code that is not used is excluded from the code that is executed. 🤘 🦾
Written ✍️ by @debugpai
#javascript #HashnodeCommunity #devcommunity
debugpai.com/dead-code-elimi…
Published my first article today on my new blog:
Dead Code Elimination in Javascript (debugpai.com/dead-code-elimi…)
Deepak Pai retweeted
Hi everyone! I'm excited to release my first e-book today on JS Promises. The USP is that it will teach you how to build Promises step-by-step.
At the end of the book you'd have created the perfect Promise implementation, else money back!
Buy it now at gumroad.com/l/aplus
If you see this error in chrome console it shows the line number of code where its logging it from. Then you can attach a breakpoint there and rerun your code to debug it further. If the error is in node you can still use chrome to debug it.
