I agree that all engineers tend to write too much code and overcomplicate solutions. This post is all about Keeping it Simple. I really liked the description of the three phases that every software engineers go through. Worth reading.
29 behaviors is a lot but this read has a lot of gems in it. For example: “Know the difference between a premature optimization and a show-stopping optimization that NEEDS to happen”, “Become a power-user of your development tools”, “Always code review your own work first”. I suggest reading it slowly, start with a few behaviors a day and spend time thinking about them. (Credits to NatanS)
Pushing forward the series of posts on how to be a better programmer. This one is from Kent Beck, Technical Coach @ FB. Unlike previous posts this one has mainly short tips. Some of the tips may seem obvious while others are more difficult to understand but I found all of them great. Must read.
Source: Mastering Programming
Another post in the series on how to write good code. The five concepts mentioned in this post are awesome and obvious at the same time.
Another great post about software development. All of the sections under “Don’t build for the future, build for future change” are simply a must read.
Another great post in the series of how to be a great software engineer. I like this one specifically because most of the ideas are practical and feasible.
The subject is debatable and different people have different opinions on “what does a senior develop do”. I agree with most of the statements in this post, especially “humble and respectful, honest and transparent,”.
One of the best posts about “legacy code”. Starts with defining what is spaghetti/legacy/bad code. Then why to avoid the “Big rewrite”. Finally concluding with how to fix it. The best take away IMO is The Boy Scout Rule: “Every time you are in the code base, leave the code cleaner than you found it.”
A new fresh way to look at development experience. From Junior to intermediate to Senior.