2 ms·
Nah, it's about favouring bad programming practices, not thinking about the architecture of the software and giving developer experience a bigger role than end
by spookie 1y ago
Nah, it's about favouring bad programming practices, not thinking about the architecture of the software and giving developer experience a bigger role than end user experience. All these stemming from a push to get to market earlier or making employees replaceable.
- taeric 1y agoI'd guess less on "bad programming practices" and more "prioritizing development speed?" Mostly inline with your next point. We value getting things released and do not have a solid process for optimizing without adding new things. Ironically, it was specifically the longer feedback cycle of long builds and scheduled releases that seems to specifically have given us better software?
- spookie 1y agoFair, I just think there is a huge overlap between bad practice and speed of development. The latter fuels the former in many ways.
- taeric 1y agoOh, I likely fully agree with you on it. I'm just pointing at the hazard that a lot of these practices aren't, intrinsically, bad. Rapidly getting something done is, generally, a good thing. I'm not entirely sure how to make it not the priority, but it does feel that that is the problem.