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.
“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.
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.
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...
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.