3 ms·
I take issue with the pasta diagram. I was there, in the 1990's, as a working professional not a hobbyist. The popular architecture was, for better or worse, s
by lelanthran 3y ago
I take issue with the pasta diagram.
I was there, in the 1990's, as a working professional not a hobbyist. The popular architecture was, for better or worse, structured as layers, not spaghetti.
Some software from the 80s might meet that definition, but I think it's uncharitable (almost to the point of insulting) to assert that until the 2000s most programmers didn't know how to write anything but spaghetti code.
- marginalia_nu 3y agoThere was a moment when OOP was the new hot thing that code got real noodly, but this was arguably a temporary regresssion.
- jacquesm 3y agoSince Wirth nobody had any excuse. Structured programming was the key to breaking through the few-thousand-lines glass ceiling. Case in point: I tried writing a program to be able to edit sheetmusic and to play it back using the sound hardware in my computer. Endless re-tries of doing this, it would start off just fine and grow and grow and then I would get bogged down. With every iteration it was clear that it was getting better but I never could see it through to the finish. Then I read Wirths book https://en.wikipedia.org/wiki/Algorithms_%2B_Data_Structures_%3D_Programs https://en.wikipedia.org/wiki/Algorithms_%2B_Data_Structures... and even though the book was geared towards Pascal it was like someone had turned on the light. Everything fell into place and suddenly I could write code until I ran out of memory and keep it all organized. Massive change. This was in 1982 or so.
- Kamq 3y agoProper spaghetti code, in my mind, has always been pre-structured code. Which generally means assembly. C is rough to refactor sometimes, but it's nowhere near the kind of "push a couple return addresses and jump into the middle of a function" that used to exist.