I learned the hard way about the beauty of backups and the 3, 2, 1 rule. And snapshots are the GOAT.

Even large and (supposedly) sophisticated teams can make this mistake, so dont feel bad. It’s all part of learning and growth. You have learned the lesson in a very real and visceral way - it will stick with you forever.

Example - a very large customer running our product across multiple servers, talking back to a large central (and shared) DB server. DB server shat itself. They called us up to see if we had any logs that could be used to reconstruct our part of their database server, because it turned out they had no backups. Had to say no.

I am one… but I’m the only one I know at my company and socially.

The lists are quite similar with a slight reordering in the top 7 or 8. I guess both lists are a representative sample of developers… But there is one interesting difference:

IEEE: Python, Java, C++, C, JS, SQL, Go TIOBE: Python, C, C++, Java, C#, JS, VB (!), SQL

In IEEE, VB is way way down the list. Do IEEE members use VB less?

I’m always amazed that C still scores so high, but I’ve been told there is a lot of embedded work still going on.

Keep in mind that this is for « typical IEEE members », which I am pretty sure is not a great representative sample of programmers in general.

How many of you programmers out there are IEEE members?