I'm Biased since I'm a cohost, but ADI Pod (Artificial Developer Intelligence) at https://www.adipod.ai/
My cohosts Dan, Rahul and I do weekly coverage of AI news for developers, our pet projects, work wins and new technique / tools.
What I think sets us apart from the usual AI podcast space, other than our decade long friendship, 'good vibes', and crippling HN addiction, is the fact that it's a passion project by developers and for developers. You'll hear us break down a paper on diffusion-autoregression hybrid architectures and then immediately talk about wasting 40 minutes having Claude fix test coverage when the real fix was a one-line change.
Recent episodes covered cognitive debt from AI-generated code, my experience convincing AI that the Earth is flat, and the Thoughtworks retreat and its 'agentic manifesto'. Episodes are weekly and about an hour each. The idea came to me when I wanted to listen to a more casual AI podcast during weekend long runs (so no heavy math and no startup pitches), hope it serves that purpose well.
Hi, author here -- kind of weird to see my post on hn. Yea, a good meeting can absolutely be worth all the developer time it costs!
I tried to carefully qualify all my calculations in terms of 'opportunity cost' and 'pointless meetings', but clearly it didn't work :).
The main idea behind the post is that the expected utility of a meeting with n developer, E[u(x_n)], should be greater than or equal to the opportunity cost of having that many developers in the meeting. Furthermore, through batching and async context transfer we can reduce the opportunity cost of having those developers in that meeting, which is pure upside for the business.
In a previous job I frequently got invited to meetings that were planned because the expected utility is > 0, which is imo really bad business.
The site was inspired by a thread a few months ago on what books HN recommend. I'm a self-taught programmer and I would also like to know if the skill set in creating a site like this would be enough to qualify me for an entry level position at a web company for more learning experiences. Thank you.
My cohosts Dan, Rahul and I do weekly coverage of AI news for developers, our pet projects, work wins and new technique / tools.
What I think sets us apart from the usual AI podcast space, other than our decade long friendship, 'good vibes', and crippling HN addiction, is the fact that it's a passion project by developers and for developers. You'll hear us break down a paper on diffusion-autoregression hybrid architectures and then immediately talk about wasting 40 minutes having Claude fix test coverage when the real fix was a one-line change.
Recent episodes covered cognitive debt from AI-generated code, my experience convincing AI that the Earth is flat, and the Thoughtworks retreat and its 'agentic manifesto'. Episodes are weekly and about an hour each. The idea came to me when I wanted to listen to a more casual AI podcast during weekend long runs (so no heavy math and no startup pitches), hope it serves that purpose well.