To me this feels like one possible way to group engineers, among many other possible ways.
But I wanted to comment on your other article - about minimalism. I think it has a nice insight about providing contrast to highlight what’s important. So just writing this comment to say thank you, enjoyed reading it.
Hey thanks for that! I really appreciate it.
Well, the architecture of any nontrivial piece of software can also been seen as a puzzle. For example, the theory behind parsers or assemblers is well developed, but the design of every parser or assembler is a unique puzzle, the difficulty depending on the language you’re targeting.
This is a good way to consider teams and team makeups, but not necessarily so useful when building that team to begin with.