4 ms·
Just to be clear, your question is: why should a senior developer -- whose job ultimately involves managing a complex set of text files -- understand basic conc
by cyberpunk 3y ago
Just to be clear, your question is: why should a senior developer -- whose job ultimately involves managing a complex set of text files -- understand basic concepts behind the industry standard tooling for managing ... text files?
Complete waste of time, they should be out playing golf with a board member instead, right..
- bluGill 3y agoThey need as much as a junior to get the job done. Then they should focus on the hard problems many of which are not tooling related. However if a different team has made a good ci system they don't need to know how it works, just enough to diagnose a build error they didn't see locally. Likewise, someone needs to know the details of git, but there is no need for everyone to know the details of that mess (git is a particularly bad version control, I wish the world had settled on something else - there are several better choices) so long as you can do the basic commits, merges and checkouts. Most senior developers need to know how to add a text file to cmake (or whatever your build system is), but there is a lot more you can do with a build system that only a few need to know. Senior devs need to be great at the problem domain they are in. That is normally the subsystem they write code in, and good architecture therein. They need to be able to figure out all the tools you list and more, but becoming experts in them all is a waste of time if enough others already are.
- otabdeveloper4 3y ago> they should be out playing golf with a board member instead As a senior developer myself, I approve this message!