=> 👽 martin

Top-down design is far less enjoyable that bottoms up design. This is not a current status, yet.

3 years ago · 👍 ser

Actions

=> 👋 Join Station

9 Replies

=> 👽 marginalia

@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? · 3 years ago

=> 👽 prk

@marginalia well, there were less software security issue at the time, and the AGC was air gapped... let's even say void gapped :D · 3 years ago

=> 👽 marginalia

@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. · 3 years ago

=> 👽 martin

Guys, I was talking about coding while drunk 😁 · 3 years ago

=> 👽 prk

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. · 3 years ago

=> 👽 isoraqathedh

To me the "write the code that you want to write and build around that" approach is most enjoyable, though results can vary. · 3 years ago

=> 👽 martin

Just to add some more context, here's some relevant research to my joke: https://xkcd.com/323/ · 3 years ago

=> https://xkcd.com/323/

=> 👽 seamustbn

True! I never understood the top-down thing. I firmly believe in bottom-up · 3 years ago

=> 👽 defunct

where's the bottom? 🤣 · 3 years ago