Another good set of advices. They're not all technical which is to be expected.
Good set of advices on naming variables, types, etc. Indeed this makes things easier to find in code bases.
Interesting musing about the "software crisis" which was declared in the late 60s. We're coping with it by piling levels of abstractions but clearly we're still not out of it. Our craft still needs to grow.
Good food for thought. Explains quite well the factors which impact software development.
Interesting take about the mantras often used in our profession. They shouldn't be treated as laws, but as proverbs carrying a piece of contextual wisdom. It's thus unsurprising that they tend to contradict each other. This contradiction should make us pause and think.
Hopefully nobody is handling configuration by assuming the user will modify the source code or build scripts by hand. Unfortunately I still encounter it from time to time...
Another example of enforcing conventions using automated checks. This time using Python and Django tricks.
Lots of good advices of course. It goes a long way to improve the quality of the project and the ease to on-board people. This is quite some initial work though.
All good points. Can we improve? Sure. Does it means we do it bad? No. Just do it more when it makes sense.
Very interesting insights from someone who's been practicing this trade for a long time. I agree with most of it, it's inspiring.
Definitely this. The difference between a well performing team and one delivering subpar software is the basics of our trade. Minding your data models, your architectures and the engineering practices will get you a long way.
Interesting how feeling stupid can actually push you toward good engineering practices, isn't it?
To take with a pinch of salt since it has a couple of biases (most notably it focuses a lot on satisfaction) and the sample size is a bit small. A few interesting insights nonetheless. In particular it hints at autonomy, transparency, technical skills and vision as being the most important factors for satisfaction and success within teams. The applied project management method? Not so important it seems if the other factors are satisfied.
Definitely this, mind the complexity you introduce in your code. Looking smart is not the goal here...
As always from Kent Beck, an excellent set of advices to improve you programming skills.
Indeed the example is a bit extreme. Still it illustrate quite well what should be found in a commit message. It needs to tell a story and motivate the reasons behind a change.
Excellent post about code reviews. I particularly like the introduction about the motivations, it's often forgotten.
Understandability is indeed a very important goal. There are easy ways to improve it in a system.
Can definitely recommend. The pre-commit project also make managing those a breeze.
Review of the newest book from Kent Beck, I'll probably check it out and read it.