As a former developer, I find the countering-safety-logic a drain

8-9 minutes are usually the very least to have it properly "al dente", but that's the mass-produced mall stuff like Barilla or other cheap stuff. Proper, bronze drawn "no. 5" spaghetti will easily take in excess of 10 minutes.
Hah, reminds me of my friend that started making and serving freshly made egg pasta in his restaurant. People started complaining that it wasn't al dente so he gave up on the idea... :D :D :D
 
mac-cheese-pizza102137245_meredith (1).jpg
 
Back in the old days when one programmer was programming all alone, the one who always had the complete overview about everything, the one who was acutally writing source code, getting good quality products was easier. Today a bunch of young students with almost no experiences in what they do try to work together. Some start into vacation, the others have to continue their work. Once the one in vacation returns he has to continue the work of the others without even knowing about it, where these are leaving into vacation now. I can imagine that it is close to inpossible to work on quite complex projects successfully this way. At least David Braben himself should know about this. :)
This is actually a good point.
The things might be complicated even more: someone decided to leave projects, well because of "new opportunities and new areas" or just got bored or just realized how hard to maintain and develop existing stuff. Or some of developers have been left because they are became too expensive.
Anyway the problem is still here: how to maintain and develop the product.
Nothing new here has been invented yet: as books say, write documentation and clean code.
Setting up the processes requires qualification and experience.
Developing features/UI requires qualified personnel either (most likely not students).
Sometimes decisions taken under pressure (release date and such).

ED is a good example of how some of those can fail.
 
Back in the old days when one programmer was programming all alone, the one who always had the complete overview about everything, the one who was acutally writing source code, getting good quality products was easier. Today a bunch of young students with almost no experiences in what they do try to work together. Some start into vacation, the others have to continue their work. Once the one in vacation returns he has to continue the work of the others without even knowing about it, where these are leaving into vacation now. I can imagine that it is close to inpossible to work on quite complex projects successfully this way. At least David Braben himself should know about this. :)
Yep, my greatest frustration was not my own code or bugs, but interfacing with someone else's bug-ridden code. And more often than not it wasn't a simple, "Hey Joe, this ain't working according to the specs, mind fixing it for me today?" Nope, that rarely was an option, sad to say. Instead I had to resort to "fixing" the broken libraries using my own code that called those libraries, which ended up making my code way uglier than I ever wanted (though it did result in some comical comments). Worse, if Joe did one day get around to fixing his code, then my code needs to be updated to remove my own "fixes". Of course Joe didn't tell me he fixed his code, so I learn about it when my code breaks because it was written to anticipate his code being broken..

I much prefer writing smaller "I'm in control of everything except the OS" software, which is one of the reasons I got out of the business and only program as a hobby these days.
 
It's also quite a competitive industry right now - most places seem to be struggling to retain / hire staff.
 
Back
Top Bottom