![]() ![]() ![]() Now here’s the part where I explain that I’m an idiot. ![]() When I’ve been a newcomer to 10+ year old codebases, the best way I’ve found to get a mental model of the whole system is by tracing a call from the UI layer all the way through. I want to be able to step through the code and see a call stack. This means that I try to avoid events, excessive parallelism, and other fun abstractions not because they’re not useful, but because there’s not a clear method hierarchy. Is this code good? Who cares… can I step in and step over? If I can do that, I can understand anything. Debuggability is my number one priority as an experienced developer. I love a good IDE (having worked across various stacks I’m pretty comfortable in Xcode, IntelliJ, and Visual Studio) but when I come back to Node-and just general text editing-I always end up back in Sublime.īut you know what I love more than anything? A good debugger. I’ve been a user of Sublime Text since… forever. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |