I agree slack is important, but I’m not sure that using the lower bound for sprints (or “time boxes”) would work well. martinfowler.com/bliki/Sla…

Interesting thoughts on LLMs in production: huyenchip.com/2023/04/1…

Really nice visual intro to load balancing algorithms: samwho.dev/load-bala… (h/t Kostas)

Lots of playgrounds here I was unfamiliar with: jvns.ca/blog/2023…

Interesting way to measure dependency freshness (and therefore some of the risk): libyear.com

Whatever measure is used, I feel people need to focus on this (and other elements of dependency risk) far more than is typically done.

Interesting theory on where the term database sharing came from: www.raphkoster.com/2009/01/0…

Instagram does lots of interesting Python optimisations. Example of strict modules: instagram-engineering.com/python-at…

Yet more microservices thoughts: www.craigkerstiens.com/2019/03/1…

Interesting thoughts on where generative AI is taking the software industry: redmonk.com/jgovernor… (h/t Simon Willison)

Strongly agree with (1), somewhat with (2), agree with (3) and (4) and strongly agree with (5): chaordic.io/blog/serv…

Really great tutorial on building a LLM based on iMessage chat history: www.izzy.co/blogs/rob… (h/t Simon Willison)

Pretty light on content, but good links out: stackoverflow.blog/2023/04/1…

Interesting approach to deprecating code: sirupsen.com/shitlists

The EU does some good things, but tends to overreach a lot too: pyfound.blogspot.com/2023/04/t…

Interesting thoughts on downtime: neuroleadership.com/your-brai…

Thoughts on incident reviews: newsletter.pragmaticengineer.com/p/inciden…

The developer learning curve here is exactly what I have observed (and went through): www.mindtheproduct.com/overengin…

More microservices thoughts: www.bennadel.com/blog/3944…

Interesting post on using a monorepo and ‘living at HEAD’: www.tweag.io/blog/2023…

Good intro to precommit, with a Django focus: builtwithdjango.com/blog/impr…

More microservices thoughts: vlfig.me/posts/mic…

Interesting definition of legacy code in this episode, as code where you can no longer communicate with the author. I quite like this, although probably more as a guideline than a rule. overcast.fm/+F4RCVYuD…

Excellent advice on creating PRs: mtlynch.io/code-revi…

Classifying comments (some of these would be docstrings in Python): antirez.com/news/124

“people are not fungible resources” - somehow people seem to lose this knowledge as they move up the management ladder. jacobsingh.name/the-case-…