4 ms·
I've put over 200 tips like that on my website: https://umaar.com/dev-tips/ https://umaar.com/dev-tips/ Each tip has a textual explanation, and an animated gif
by umaar 5y ago
I've put over 200 tips like that on my website: https://umaar.com/dev-tips/ https://umaar.com/dev-tips/
Each tip has a textual explanation, and an animated gif if you're a visual learner (I know, I need to scrap gifs and move to regular videos).
There's a lot of tricks there which can hopefully improve your development and debugging workflows. Let me know if there are specific things you'd like to see. A few people have asked for how to find memory leaks.
- ajcp 5y agoAmazing! Thanks so much for this.
- deleted 5y ago[deleted]
- Felk 5y agoSpeaking of memory leaks, I once had to debug a memory leak caused by console log entries. Objects that are logged to the console are prevented from being garbage collected, even if the console was never opened. That includes DOM nodes or I think also handles to WebGL textures.
- franklyt 5y agoThat’s interesting. I’m guessing console.log appends to the window object somewhere, which is a fairly common method of image preloading.
- umaar 5y agoInteresting, I think that's because logged objects are "live", so you can inspect their current state, not just the state at the point of logging.
- stexx 5y agoGreat thing! Do you support rss feeds, so that I can stay up-to-date?