My career in software development happened back in the days of MS-DOS, before Windows really took hold. I developed a system that recorded the inspection of Fir

My career in software development happened back in the days of MS-DOS, before Windows really took hold. I developed a system that recorded the inspection of Fire Safety equipment like Fire Extinguishers, Hoses, etc. My initial estimate for the time required to build the system was 2 months, it actually took 3. Then the client looked at it, and it met all the requirements, but was unusable in practice. I then worked onsite for a year, and learned so much about software usability by seeing it in use. After that year, we deployed it to 10 other sites. Other than having a summer intern once, it was a solo effort. The code was written in Turbo Pascal, with some code on the hand-held computers written in a language called PL/N. (A variant of PL/1 for the Norand corporation handhelds) I wrote all my own text editing/forms handling libraries, and everything else I needed. Version control was using pkZip to archive the source code onto 3.5" floppy disks. Tying it back to the article in question, I can't imagine what it's been like with the push for "sprints" and all the rest in software development over the past few decades. I can see how it would drive you to burnout. I'm very thankful I missed it. Y'all have my sympathy.