✳flâneur — a map of the web's best reading

Lessons learned in 35 years of making software – Jim Grey

dev.jimgrey.net · 3,527 words · saved by 1 readers

Today (3rd July, 2024) is my 35th anniversary working in and around the software industry. All but 18 months of that have been spent on software development teams; those errant 18 months were spent editing technology books. I figured out fast that it wasn’t for me, and came right back home to the software industry. In 35 years, I’ve learned some strong lessons. Maybe they’re ones you’ve learned yourself already. We all learn at different paces and at different times! Do things in the most straightforward way possible. It’s easy to fall into the trap of clever solutions, or clever applications of technology, or overbuilding something because you’re anticipating the future. Don’t do it. You will hate yourself for it later when you have to maintain it. Build the thing in the simplest way you can, as fast as you can. You can improve it over time as needs demand. There is no substitute for working software in Production. I can’t believe now that I have been part of 18-month release projects

Lessons learned in 35 years of making software – Jim Grey on software management Skip to content Lessons learned in 35 years of making software Today (3rd July 2024) is my 35th anniversary working in and around the software industry. All but 18 months of that have been spent on software development teams; those errant 18 months were spent editing technology books. I figured out fast that it wasn’t for me, and came right back home to the software industry. Me, working infinitely hard at one of my career stops In 35 years, I’ve learned some strong lessons. Maybe they’re ones you’ve l

Explore this link on the map →

related reading