4 ms·
Based on my experiences: They shield junior developers from themselves and from upper management. They know how to translate requirements from management into f
by nperez 12y ago
Based on my experiences: They shield junior developers from themselves and from upper management. They know how to translate requirements from management into feasible projects. They perform code reviews and lead the collaborative process of designing a system.
It's more about taking ownership of the process than about the code itself.
I haven't had any developers report to me but might be interested at some point in my career. Over time you realize that having strongly defined processes (while avoiding micromanagement) is at least as important as technical skills, and it requires strong leadership.
- blooberr 12y agoYeah also shielding from other parts of the company. What would make you more inclined to having developers report to you?
- nperez 12y agoSorry for the late response. It's less about oversight, and more about what I could do. In my first full-time development job, I was working under a lead developer who was seriously badass at mentoring people and making sure they knew what they had to do (though I don't think he realized it - it was his first time being promoted to a leadership position!). To this day, when I'm feeling stressed out at work, I'll think "What would Rob have advised me to do?" and it makes me feel more secure about my decisions. Junior developers are often really idealistic and ambitious, and I would like to be in a position where I could reward and facilitate that instead of crushing it (which happens all too often).