codeinabox@programming.dev to Programming@programming.devEnglish · 14 hours agoWhat we lose when we stop codingnewsletter.humanwhocodes.comexternal-linkmessage-square4fedilinkarrow-up133arrow-down12
arrow-up131arrow-down1external-linkWhat we lose when we stop codingnewsletter.humanwhocodes.comcodeinabox@programming.dev to Programming@programming.devEnglish · 14 hours agomessage-square4fedilink
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up15·13 hours agoNon-coding architects has been a well known organizational red-flag for decades. Non-coding people always lose track of reality, and it’s a disaster to give them decision power over fine-grained technical choices. Now, I don’t really know how that maps into non-coding software developers, but I’m not optimist.
minus-squarekibiz0r@midwest.sociallinkfedilinkEnglisharrow-up3·6 hours agoIt’s a matter of feedback loops. It’s the same problem as when you divide teams by front-end/back-end, or implementation vs testing, or features vs platforming. When you don’t have to feel the pain of your decisions, you’re going to make bad decisions.
Non-coding architects has been a well known organizational red-flag for decades.
Non-coding people always lose track of reality, and it’s a disaster to give them decision power over fine-grained technical choices.
Now, I don’t really know how that maps into non-coding software developers, but I’m not optimist.
It’s a matter of feedback loops.
It’s the same problem as when you divide teams by front-end/back-end, or implementation vs testing, or features vs platforming.
When you don’t have to feel the pain of your decisions, you’re going to make bad decisions.