You'll at least need the discipline to include the ticket ID in the message. Links to documentation are ok, but they will likely rot and even if they don't the content may change such that it no longer accurately reflects the commit changes.

Your argument on conventional commits is something I've come to agree with. There are even tools that can generate release notes from conventional commits, and they are premised on the same mistake.

This is the premise of the excellent book Your Code as a Crime Scene. The history and structure of the codebase reveals a wealth of information.

Everything about this trend suggests that we’ll soon look back and find we’ve smothered ourselves in the digital equivalent of asbestos

Conclusions

These findings do not support the hypothesis that COVID-19 vaccines increase the risk of sudden cardiac death in young healthy adults.

OP here. My submission included the "older Windows 11" clause. I did not change it

There are ways to write that are faster and more legible. I recommend looking into the Getty-Dubay style.

Thanks, though I think part of longhard feeling labourious these days is RSI sadly. I did try to correct my scrawl for effort and legibility a while ago, but it just wouldn't stick!

I had pretty terrible RSI (and even more terrible handwriting) and could write much without cramping up or pain. What helped for me was teaching myself proper cursive and fountain pens. Rather than clutching a ballpoint and marking with jerky finger/wrist movements, I now use my arm for larger movements and let the pen glide. It’s helped tremendously. It’s slow going at first but keep at it. Plus fountain pens are pretty fucking cool. Also, paper matters too; but paper and notebooks are another fun rabbit hole.

Ballpoint pens are the worst, especially the ubiquitous cheap ones. Gel pens are better if you're not quite ready to make the leap to fountain pens.

I cannot read dark grey text on a black background

If you've ever used NFS you've used one of the oldest distributed object systems still in use, developed by Sun Microsystems. Variously called Sun RPC, Remote Procedure Calls, or Open Network Computing Remote Procedure Call

I participated in something kind of the opposite of that: multiple microservices in independent repos, but with intertwining dependencies on each other. Adding features meant shotgun surgery across at least 3 repos/services, sometimes more.