10x Programmers: Myth Or Reality?

Originally published June 24, 2016

It's time to give the software engineers their due

10x programmers are a hot topic to discuss in the software industry nowadays, so thought it'd be a good idea to share my viewpoint in this regard.

How to Be a Better Programmer: Take Care of Yourself!

If you want to be a better programmer, stop this. Now.
Photo credit by Flickr/osseous

A decade ago, a book called Death March was listed as a bestseller. The book described how insane hours of programming led to health issues:

“Death March is a type of project in which the employees need to overwork for unsustainable number of hours. The project starts feeling like an actual death march as the superiors force their employees to keep on working against their better judgment. The projects had so many parameters that the only way to succeed was by coding more than 16 hours a day, seven days a week—with no break until the project is finished.”

Some years later, another story went viral from a spouse of a programmer who worked at Rockstar games. She said the company expected the developers to work 12 hours a day, six days a week, damaging the programmers’ health.

7 Reasons Why Using SELECT * FROM TABLE in SQL Query Is a Bad Idea

I have read many articles on the internet where people suggest that using SELECT * in SQL query is a bad practice and you should always avoid that. Instead, you should always use an explicit list of columns. That's a good suggestion and one of the SQL best practices I teach to junior developers, but many of them don't explain the reason behind it. 

Unless you explain some reasons why one should not use SELECT * in queries, it's difficult to convince many SQL developers, many of whom have started learning SQL by doing SELECT * from EMP in the Oracle database.