I just declared a moratorium against AI-written change descriptions (e.g. PR and commit messages, also issues/tickets) from my team.
AI was writing change descriptions that were worse than useless to me as I tried to review PRs: outlining details of the code that could easily be seen by looking at the code, but omitting the higher-level framing needed to understand broadly what the code is doing.
I think people like having AI write these things because the output looks structured and thorough, which makes it feel professional in a way. But this isn't actually valuable. Concise, high-level descriptions are better for everyone. If I need to use my own AI to interpret what your AI wrote then something is wrong. Let AI write code, sure, but for the description, I'd rather see your prompt than your output.
We could maybe have extended agents.md with guidelines on writing descriptions, but this seemed a bit pointless since a good, concise change description only takes a few minutes to write -- not a significant time savings to delegate to AI. At least, it doesn't take long if you understand the code -- and if you don't understand the code, then I'm definitely not merging it.
Cannot wait for teams that build their custom JIRA/Workday replacement/custom CRM to one day turn around and ask:
“Why do we have so much internal software that is buggy / has poor UX + we need to maitain?”
Seen this movie well before AI, when Uber built uChat (custom Slack)
i really don't care about using AI to ship more stuff
it's really hard to come up with stuff worth shipping
i want to ship the same amount of stuff with higher quality both in product and code
I’ve been a Browser Company hater for a year.
I’ve been an Atlassian hater for a decade.
I was formed in the fires of hell specifically for the task of covering this.
Video later today.
Kubernetes anti patterns that belong in the 🗑️ in 2025 🧵 (#10 will trigger many)
1) Secret injection in manifests.
Come on, what are we doing here? We literally have external secrets, the problem is solved. Stop shoving this stuff into manifests.
KINGS WORLD CUP ⚽️
COUPE DU MONDE 7vs7
32 équipes au Mexique
Notre but : être sur le toit du monde.
Soyez prêts le casting de la coupe va être monstrueux.
A partir du 26 MAI sur ma chaîne 😀
@Jseguillon@katia_tal Ça devrait bien se passer vu qu'une autre entreprise a repris l'un des principaux mainteneur pour bosser sur flux: https://t.co/1vYQSWMTfd
ssh has secrets. Too many to share in one tweet. One of which is how it acts as a serial-line processor for secret keyboard functionality you probably never knew about. For example, why, when you press ENTER and then ~ immediately after, does the ~ not appear right away? Thread…
@aderumier De ce que je comprends la version containerd c'est un exécutable donc tu peux faire ce que tu veux et avec cri-o je pense que c'est possible aussi https://t.co/V34MoMFif2
@_Akanoa_@RobertStphane19 Je sais pas si ça aide ton cas d'utilisation mais sur le projet kubespray par exemple on fait en sorte d'avoir un nom et/ou des ressources tagué avec le nom du job de CI pour pouvoir les retrouver et les détruire après "sans avoir à garder de state".