3 ms·
"Everything should be built top-down, except for the first time" (from Perlisms, 1970s or so). Approaches to neatly building a well-understood thing are radica
by nine_k 4y ago
"Everything should be built top-down, except for the first time" (from Perlisms, 1970s or so).
Approaches to neatly building a well-understood thing are radically different from approaches to building / tweaking / rebuilding a new, so far untried thing.
Software engineering is most valuable around the latter kind of thing; the former kind of thing is usually already built and open-sourced.
- hinkley 4y agoHow often have you gotten to build things for the second time? The dilemma there is that most of us only get to build things for the second time if we are working on a copy-cat product from a competitor, and those are not the sorts of projects we glorify. Everyone wants to work on new ideas, not copy-cats.
- 7thaccount 4y agoPerl had a "write one to throw away" philosophy that you should write a quick and dirty prototype to understand the business problem and then you could design the full thing with an actual understanding for how things work. Stuff was still complex back then, but probably a lot simpler. I doubt it's possible for a project past a certain size.
- nine_k 4y agoA lot of contract and some corporate work is about building things n-th time. A web form like many other web forms, a CI pipeline like many other CI pipelines, etc. Nothing fancy; 99% like last time elsewhere, just reshuffled to match the local conditions. It's not exactly the same thing, but the amount of well-known stuff in it is pretty large. Here's where frameworks like Rails, or Django, or Next.js shine: they have much of the expected, n-th time code factored out, you need to glue predefined parts in predefined ways, and get an expected result.