←back to thread

294 points NotPractical | 1 comments | | HN request time: 0.204s | source
Show context
dylan604 ◴[] No.41855041[source]
Take this as a lesson. If you've been a dev long enough, you've worked on a project knowing that how the project is being done isn't the best method with every intention of going back to make it better later, but not at the expense of getting the MVP up and running. You'll also have seen that never actually happening and all of those bad decisions from the beginning still living all the way to the bitter end.

I'm guessing not one person involved would have ever imagined their code being left on a machine just left out in the open exposed to the public completely abandoned by the company.

replies(4): >>41855099 #>>41855913 #>>41856088 #>>41856846 #
Apocryphon ◴[] No.41855099[source]
One just wonders if the cooperative-multitasking BASIC implemented in this machine really was necessary for an MVP. Other than if that just happened to be the sort of programming that the developer at the time was familiar with.

Also, this really is the 'engineering' discipline with the lowest level of craftsmanship and regard for rigor, isn't it? Because the failures are usually intangible, not directly life-threatening.

replies(2): >>41855443 #>>41864957 #
duskwuff ◴[] No.41864957[source]
> One just wonders if the cooperative-multitasking BASIC implemented in this machine really was necessary for an MVP.

I have a feeling that someone already had that hammer ready and was in search of a nail. :)

replies(1): >>41869377 #
1. rasz ◴[] No.41869377[source]
Might be case of a VB6 programmer who graduated to .Net C# but still misses the good old days.