💾 Archived View for station.martinrue.com › martin › c523482e135146848b3653c694f96163 captured on 2023-11-14 at 08:55:32. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-03-20)
-=-=-=-=-=-=-
Top-down design is far less enjoyable that bottoms up design. This is not a current status, yet.
2 years ago · 👍 ser
@prk The space program was undertaken during a pretty fierce rivalry between the USA and USSR; that is fierce bordering-on-nuclear-apocalypse. Do you really think one side would shy away from sabotaging the other in a prestige project like that? · 2 years ago
@marginalia well, there were less software security issue at the time, and the AGC was air gapped... let's even say void gapped :D · 2 years ago
@prk I really think it depends on the domain. There are problems that respond much better to one of the two approaches. Although I do agree that upfront design has gotten a lot of undeserved shit by the agile gang. Upfront design has put men on the moon, agile has given us refrigerators that need to install security updates. · 2 years ago
Guys, I was talking about coding while drunk 😁 · 2 years ago
I might sound like a dinosaur, but top-down is really useful for the main design part. Bottom-up is fine for tech/coding but unless you have at least a glimpse of the big picture, you're doomed to reboot the project from scratch for a v2. · 2 years ago
To me the "write the code that you want to write and build around that" approach is most enjoyable, though results can vary. · 2 years ago
Just to add some more context, here's some relevant research to my joke: https://xkcd.com/323/ · 2 years ago
True! I never understood the top-down thing. I firmly believe in bottom-up · 2 years ago
where's the bottom? 🤣 · 2 years ago