A good list of code smells to pay attention to in Rust. Also provides patterns to avoid such smells.
A good reminder that you don't want your code base clean to the point of being sterile. You have to fight off the mess yes, but some of it can stay if it provides affordances.
An interesting set of principles for code reviews.
An explanation about where the SRP comes from and what it really means. It's very often misunderstood or overlooked.
I'm not fully aligned with all of this article. That said, it's an interesting way to frame the topic of how we're having to make tradeoffs all the time.
Easy to misunderstand as an elitist stance... But it's not the way I read it. Churning more code faster isn't going to help us, you need to take the time for people to grow and improve. It's not possible to achieve if you're drowning in eager beginners.
A good reminder that long hours are not a sign of success with your project... on the contrary.
There's a big "if" of course, don't just throw your tests out of the window. But indeed, they need to bring value... so start by having really good tests.
A good explanation of why the concept is important, also comes with a nice list to get started.
The question is always valid. I like this particular answer.
A short list of common code smells that people need to know.
Both approaches have their pros and cons of course. Whatever you pick, it has to start with a care for quality shared within the team.
Definitely this, too often I see projects treating the technical debt as one-off large tasks. Really it's something you should deal with bite sized and over time.
I don't think I'm ready to give up just yet... Still, I recognise myself so much in this piece it feels like I could have written it (alas I don't write as well).
Nice illustration on how you can hunt down complexity in your codebases. It is obviously a slow process but comes with nice benefits.
Indeed feels bad when there are so many problems in the example of LLM based completion you put on the front page of your website...
Nice piece. In an age where we're drowning in bad quality content, those who make something with care will shine. They need to be supported.
If you expected another outcome on the average developer job from the LLM craze... you likely didn't pay attention enough.
It definitely has a point. The code output isn't really what matters. It is necessary at the end, but without the whole process it's worthless and don't empower anyone... It embodies many risks instead. I think my preferred quote in this article is this:
"We are teaching people that they are not worth to have decent, well-made things."
Interesting ways to look at processes and their outcomes. Depending on the mental model you won't ask the same questions when investigating incidents.