All of that is to say: you can use AI and show that you care. It's about intention and attention. Think about the purpose, don't delegate your thinking, reread before you submit, and make sure you're willing to stand behind it, especially when others will build on it. Just like before, less is more.
People say they're a good manager because their team likes them or their team is happy. Wrong! You're a good manager if you make them more effective: treat people as individuals, align their motivations with the work, create psychological safety, give honest feedback, and show up as a real person.
The idea that AI is turning everyone into a manager is an oblivious take on what good management requires. It reduces management to task delegation and checking results. It's the kind of view you arrive at if you've never experienced what good management looks like.
Guess what, people care about doing work they believe in with people they care about. When AI strips away visible effort and intention, it comes across as dismissive or meaningless, even if the output is correct. It can feel like no one did the work which breaks how we relate to each other at work.
Highly recommend this podcast with Charlie Warzel and Jonathan and Melissa Nightingale on AI in the workplace: insights on how poorly curated AI output erodes trust, what humans value at work, and why management is a skill and not just delegation. More in replies: www.youtube.com/watch?v=ncmu...
NEW POST
Modern hardware is fast, but software often fails to leverage it. @withcaer.com guides their work with mechanical sympathy. They distill this into principles: predictable memory access, awareness of cache lines, single-writer, natural batching
martinfowler.com/articles/mec...
I first ran into PID controllers while working on cache eviction. They're a simple way to keep systems on target as load shifts. I wanted to better understand them, so I reimplemented one in Go and put together a walkthrough: konradreiche.com/blog/an-intr...
Leading Go code review nit: putting helper types or functions above the main exported identifier. It reads like Go needs forward-declaration. Because you can define in any order, let's order by importance.
When I open a file I want to see the main characters, not the background actors 🎬
AI-assisted code reviews can be incredibly powerful. But I'm starting to get wary of them as a first pass. If AI decides what you see and question, it'll interfere with your independent thinking and, worse, give a false sense that you've done some of the work, so your own review ends up weaker.
Partial blame to Microsoft and Zoom for normalizing the need to install new software just to make video calls, despite browsers being perfectly capable. They make it extra hard to even find the web-only links.
simonwillison.net/2026/Apr/3/s...
@industrialempathy.com I had to trim this to fit 300 characters. I hope that's okay, because unlike on X, where you make the rules, others here get to quote you 😉
"Software is free as in puppies. It will pee in your bedroom and eat your furniture. The weight of every line of code is real. We will need to maintain it. We will need to port it. It goes into the context window. Someone will get paged at 2 a.m. unexpectedly." ― @industrialempathy.com
"In a thoughtful piece, Azeem Azhar, the technology writer, describes his efforts to safeguard 'the space where ideas arrive before they’re shaped'. But how many of us will put in such careful, reflective effort to protect our most generative spaces of thought?"
I was happy to see JetBrains release modern Go guidelines for AI agents. That said, we added go fix ./... to our formatter and CI, and it quietly solved most of it. The Go team keeps surprising by turning rules into deterministic tooling.
Great read from @apenwarr.ca. Reviews don't scale. Each approval step turns minutes into days of waiting. They catch issues, but after the code is written. The system already allowed them. Repeated comments point to missing boundaries and unclear APIs apenwarr.ca/log/20260316
If adding less code feels impossible, that's a signal that we should consolidate what already exists instead of extending it.
AI increases how fast we can add solutions. It does not increase how much system complexity we can hold in our heads.
Watching capable engineers ship large amounts of AI-generated code at an impressive velocity.
It was never hard to add more code.
The hard part is adding less.
We optimize locally. A new problem appears, so we add another piece of code that solves it. The system becomes harder to reason about.
„There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.“ — C. A. R. Hoare
I've just released a new version of the "sh" #golang module, including initial Zsh support in shfmt, as well as many improvements and fixes to the parser and interpreter 🎉
📣 The #GopherCon Call for Speakers is officially closed!
A huge thank you to everyone who submitted a talk proposal. We received 150+ submissions, and our Evaluation Committee is now diving into the review process.
Stay tuned as programming is expected to go live in early May.
#RoadToGopherCon
Congrats Jayme! I have a feeling this won't be the last time you land something that touches systems all over the world.
This one is pretty funny go.dev/issue/77934.
Turns out a struct used for Go ←→ Linux syscalls use int64 when Linux expects int32.
But by chance this can't cause a bug because:
1. it is the last field of the struct
2. the size of the struct doesn't change since C aligns int64 to 8 bytes on 32 bits
Less than 24 hours until the @gophercon.com call for speakers closes. I started editing my proposal, then remembered the German word "verschlimmbessern" (to improve something for the worse). Turns out it was already where it needed to be. Threw out the edits 👋🗑️
Excellent example of how a data race can produce a value that was never assigned. This is what undefined behavior can look like in practice: go.dev/play/p/HuIoL...
This is such a great example! I believe you can use wg.Go() to make it even more readable.
Very cool Go library from @dronnix.bsky.social. It implements a Black-White Array, an ordered structure with O(log n) operations but far fewer allocations than B-Trees. Cache-friendly and supports duplicates github.com/dronnix/bwarr
🎤 The #GopherCon stage is calling…
Dreaming of your mic drop moment? Just 2 weeks left to wow us with your #golang talk proposal!
Submit by March 4th 👇
sessionize.com/gophercon-20...
#RoadToGopherCon
“Using go fix to modernize Go code” by Alan Donovan — https://go.dev/blog/gofix
#golang
It's conference talk proposal season again! In 2024 I had the privilege of reviewing 233 proposals as part of the GopherCon review committee. Most scored below 3/5, not because they were bad, but because they missed the critical piece. I wrote up what I learned: konradreiche.com/blog/what-go...
"That said, here is a neatly self-contained Go module for convenience."