3 ms·

Thanks for clarifying. I think I will give it a read, even if just to see what your fresh perspective looks like. The personal branding stuff sounds very intere

Thanks for clarifying. I think I will give it a read, even if just to see what your fresh perspective looks like. The personal branding stuff sounds very interesting and useful also. EDIT: I would like to note that the IMHO most mentally and technically difficult part of a developer career is maintaining the same mission-critical legacy codebase for years at a time. That's not something I really expect to get a lot of insight around from this book and your personal experience, but I'm also not sure what exactly advice around that problem would look like (probably just the tried-and-true military motto of "embrace the suck"). Either way, just my 2 cents about coding careers.

swyx 6y ago
thank you for having an open mind, and also being willing to say what others are already thinking, but doing it nicely :) agreed on the maintaining legacy bit. I spent some time on that in the sr dev chapter, but it was mostly collating what others have said. i think its impt that jr devs be aware this is a big part of the job, and also that "technical debt" often pays incredibly well because it is so challenging and the skillset to handle it well is so rare.