←back to thread

Good Software Development Habits

(zarar.dev)
362 points mmphosis | 1 comments | 17 Nov 24 16:34 UTC | HN request time: 0.207s | source
Show context
zombiwoof ◴[17 Nov 24 19:08 UTC] No.42166201[source]▶
Seems like the definition here of software is always “maintenance” of something as is, like replacing the boards on Theseus

Sometimes software is hard and 10x engineers just need to rewrite the whole thing or replace large systems

To subscribe to some world where we have to do that in “small changes” limits us

We shouldn’t make process to the weakest engineers

replies(6): >>42166367 #>>42166537 #>>42167411 #>>42167508 #>>42167881 #>>42174018 #
1. necovek ◴[17 Nov 24 21:33 UTC] No.42167508[source]▶
My experience tells me that it's both faster and higher quality to do things in small steps than leave it with your "10x engineers" (everybody thinks they are the one, right?) to "just" rewrite from scratch — and I've got plenty of proof in my close-to-20-years of career (I've never seen that go smooth; I've been a part of dozens of iterative "replace large systems" that were pretty uneventful).

As for the "weakest" engineers, even the "strongest" engineers are weak sometimes (bad day, something personal, health issues, sleep deprivation...).