2 ms·
Based on roughly 20 years of mentoring junior developers at various points during my career, the ones I look back on and think "that was a good one" have been t
by onion2k 7y ago
Based on roughly 20 years of mentoring junior developers at various points during my career, the ones I look back on and think "that was a good one" have been the ones who want to do the whole job of writing good software. They wanted to write great code of course, but they also got involved speccing out what the software is, in writing tests and documentation, doing QA, seeing their code working for the users, to maintain it, to fix it, and not to just build something that worked today and then forget about it. They were the ones who looked at a bug report and thought "Damn, how did I miss that users would do that?" rather than "The user is doing it wrong".
(Note: This is based almost entirely from working in small software agencies and startups. It might be very different in bigger companies/teams where you get less ownership of a whole problem domain.)