I like this taxonomy, though it is reductive to try to cram programmers into disjoint "tribes". Individual approaches to programming generally combine from all three, though in different proportion to different individuals.
Personally, I am driven most strongly by the "maker" approach, in that I write programs to be used. I also care deeply about correctness, simplicity, and performance in that order. I hate buggy, unmaintainable programs and the best way I know to make useful programs is to build them out of small, simple, correct components.
Performance is generally a more distant concern, but it really depends where you are in the stack. As you go down, performance becomes essential to usefulness, but the need for correctness doesn't disappear.
Personally, I am driven most strongly by the "maker" approach, in that I write programs to be used. I also care deeply about correctness, simplicity, and performance in that order. I hate buggy, unmaintainable programs and the best way I know to make useful programs is to build them out of small, simple, correct components.
Performance is generally a more distant concern, but it really depends where you are in the stack. As you go down, performance becomes essential to usefulness, but the need for correctness doesn't disappear.
reply