Ruby developer. CTO. Swimmer. Always trying to write more
There are lots of ways to characterise and evaluate engineers but I like to think of us along a single spectrum. At one end is electronics, binary code, assembler, registers and interrupts. At the other end of the spectrum is graphic design, art, photoshop, user experience, etc. Ok, you’re quickly going to point out that this should actually be multi-dimensional space but I’m a bear of little brain so let’s stick with this.
Generalists are not “better”. That generality has limits (don’t ask me to write assembler!) so the position along that spectrum matters. Likewise, the cost of generality is that you’ll never be as good as a specialist.
I like to think about this position/breath/ability equation when evaluating my skills, hiring new engineers or evaluating the needs of a team