https://bump.sh/blog/git-workflows-for-api-technical-writers
Technical writers are often challenged with keeping API documentation in sync with an ever-evolving API design. This article explores the challenges and solutions for tackling this ongoing struggle, focusing on parallel development and leveraging automation to streamline the process.
https://blog.ploeh.dk/2024/06/03/youll-regret-using-natural-keys/
Beating another dead horse.
https://blog.lambda.cx/posts/freecad-and-git/
How to efficiently version control FreeCAD files using git
https://git.github.io/rev_news/2024/05/31/edition-111/
https://jviide.iki.fi/http-redirects
Instead of redirecting API calls from HTTP to HTTPS, make the failure visible. Unfortunately, many well-known API providers don't currently do so.
I used CVS and ClearCase before moving into Git, and it took me some time to adjust to the fact that the cost of branching in Git is much much less than ClearCase. And getting into the "distributed" mindset didn't happen overnight.
https://www.youtube.com/watch?v=oV8VSBSBrr4
This presentation was recorded at GOTO Chicago 2023. #GOTOcon #GOTOchgohttps://gotochgo.comCharity Majors - CTO at honeycomb.io & Co- Author of Observability...
https://www.youtube.com/watch?v=OTCuYzAw31Y
Brian Fitzpatrick, Ben Collins-SussmanWe often hear engineers lament how hard it is to get anything done inside of a big company. The trick to overcoming thi...
https://www.youtube.com/watch?v=tugPC_JjoOo&t=1s
For more info on the next Devoxx UK event 👉 www.devoxx.co.uk Technical debt is not primarily caused by incompetent developers, architecture astronauts, unre...
@canpolat
@programming.dev