in which more paths are charted towards code independence - Technomancy
A post on how git forges might be, or can be.
Care: The missing ingredient
Someone saying that giving a shit is what matters when it comes to writing good code. I agree.
A sufficiently detailed spec is code
In agentic circles I am seeing a degree of cope where folk are saying that good software development was all about the spec all along, and all you need is the spec.
Really though? Really?
MCP Vulnerabilities Every Developer Should Know - Composio
I've not really got into the whole MCP thing yet. I know it's a thing, I just haven't really paid proper attention to it. This feels like a thing I should file away for future reference.
What Is Code Review For?
Good post about the point of code reviews, and also about how they're probably more important than ever now.
The Final Bottleneck
Having really dived into my first "agent-based" project, just to see how the process really feels, I can vibe with this article.
AI Makes the Easy Part Easier and the Hard Part Harder for Developers
A pretty reasonable view of what AI in software development could be, should be, but at the moment isn't being.
What Actually Makes You Senior
Being in a senior role I find I often run into resistance, especially from product manegers, when it comes to trying to really get to the bottom of some requirement. Sometimes I find myself second-guessing if I should bother.
This article was a good reminder that I should bother.
Your job is to deliver code you have proven to work
A take on the use of "AL" in coding that I find fits my view.
Everything I know about good API design
Interesting article to consider when thinking about what is and isn't a good API design.
Mistakes I see engineers making in their code reviews | Hacker News
Interesting article relating to ideas on how to conduct a good code review. I've chosen to link to the Hacker News thread where I first found it, rather than the blog post itself, because this is one of those HN threads where the comments are a worthwhile read too.
Conventional Comments
Similar to conventional commits, I guess. Reading through this I'm not a fan and I can't imagine I'd ever use it; but it's an interesting approach.
“Don’t Mock What You Don’t Own” in 5 Minutes
An interesting article on what should and shouldn't be mocked when writing tests.
How I take work notes as a developer
I'm a big fan of keeping notes as I work, as I develop software. I like to /try/ and take a lab notebook approach where possible. But, to this day, I've not really settled on the "one right approach".
Here's someone else's approach...
What is TSDoc? | TSDoc
A proposed standard for "docstrings" for TypeScript. Well, not docstrings in the Lisp/Python sense, but comments that can be used to document an API in place and allow for the generation of documentation from them.
Code review antipatterns
While most of the article is written as a joke, I've seen some of these "dark side" approaches for code reviews done by actual people who don't seem to want to use code review to lift everyone.
Saving this so I can relive the trauma.
The comedy and tragedy of detailed feedback
Good opinion piece about code reviews in different environments, contrasting FOSS and corporate styles and impact. I think there’s some good, if obvious, advice in here.
My favourite Git commit
I've long disliked the approach some people take of writing one-word git commit messages. While this example might be a wee bit over the top, I'd much rather see this level of care over the craft.