3 ms·
Junior devs solve computer problems using computers. Senior devs solve business problems using computers.
by jl6 7y ago
Junior devs solve computer problems using computers. Senior devs solve business problems using computers.
- jspash 7y agoAnd “ninjas” or whatever the term is for senior+ programmers know when to solve problems without a computer at all! That’s when you’ve reached enlightenment :) And I don’t mean that in a woowoo wishy washy way. I mean that when someone comes to you with a business problem, often the solution can be something as simple as “why not just change the text to say X” or “did you know that dept Y already do that thing? Let’s ask if they will take on this task also” A junior will have already coded 100 lines of “something”. And some seniors I know of will be knee deep in microservices whiteboard sessions by now. The truly great programmers I’ve worked with prefer simplicity first and foremost.
- jl6 7y agoI think you’re describing the currently-terribly-unfashionable-but-still-vital role of architect.
- closeparen 7y agoInterestingly, for us it's the opposite. Senior dev responsibilities are to: a) Get ahead of the computer problems that junior devs would otherwise create in their frenzy to solve business problems (frameworks, infrastructure services, design reviews, etc). b) Clean up the ones they missed (architecture initiatives).
- ken 7y agoI feel like much of this century's computer folk wisdom is just taking "The Tao of Programming" and translating it into modern corporate jargon. s/Novice/Junior Dev/, s/Master/Senior Dev/