Things I've learned about writing software after 12 years
1–10 of 122 posts
Re: Things I've learned about writing software after 12 years
#2I got halfway through this article and then gave up without any idea of what the author learned. Wish the author would have edited this post better.
Re: Things I've learned about writing software after 12 years
#3I got halfway through this article and then gave up without any idea of what the author learned. Wish the author would have edited this post better.
I stopped at about 5 words in with the oddly placed comma and capitalization.
Re: Things I've learned about writing software after 12 years
#4[deleted]
Re: Things I've learned about writing software after 12 years
#5Not sure what all the hate is about. He presented some interesting anecdotes about the quirks of software engineering and then tied it all together with some concrete lessons.
Maybe 5K words without any sort of lists or clickbait titles is just too much for the average reader.
Re: Things I've learned about writing software after 12 years
#6Not sure what all the hate is about. He presented some interesting anecdotes about the quirks of software engineering and then tied it all together with some concrete lessons. Maybe 5K words without any sort of lists or clickbait titles is just too much for the average reader.
Or writing at higher level than a 12 or 13 year old :-)
Re: Things I've learned about writing software after 12 years
#7Excellent piece of writing. Very funny at times, witty like a satirical novelist. Particularly enjoyed the anecdotes from NASA and the author's conveying of the powerful emotional context of high stakes programming.
I pine for a golden, future age of programming where documentation is as he describes.
> This image brought to you by preventable catastrophe, budget overruns, political wrangling, infighting, incalculable complexity, and against it’s best effort, humanity.
Beautiful caption. The dismal history of NASA in one sentence.
Re: Things I've learned about writing software after 12 years
#8We get the software we deserve. Apparently, people aren't ready to spend more money on performance, reliablility and security. When they buy software, they pay the price of a giant ball of mud (if they aren't expecting it to be free!) and they get a giant ball of mud. Simple. You call it insanity, I call it market, supply and demand. Of course, the perfectionists are unhappy about that (being one myself I can certainly empathise) but you have to realize that this kind of perfection in software costs huge amounts of money and requires the most skilled workers in the field.
Re: Things I've learned about writing software after 12 years
#9I got halfway through this article and then gave up without any idea of what the author learned. Wish the author would have edited this post better.
Good heavens, all of the incorrect uses of "it's" are painful. I may be a bit oversensitive but it is very jarring and distracting to me.
Re: Things I've learned about writing software after 12 years
#10Not sure what all the hate is about. He presented some interesting anecdotes about the quirks of software engineering and then tied it all together with some concrete lessons. Maybe 5K words without any sort of lists or clickbait titles is just too much for the average reader.
Or writing at higher level than a 12 or 13 year old :-)
[deleted]