Why is the creator of OpenCode pretty skeptical about AI productivity gains, and the hype around AI? A very conversation @thdxr (and lots of truth bombs:)
Timestamps:
00:00 Intro
07:03 Dax’s path into tech
09:04 Early startup experience
13:16 Getting involved with open source
16:13 OpenCode
23:17 Anthropic banning OpenCode
30:34 From terminal to GUI
32:34 OpenCode’s business model
36:33 Why inference is profitable
39:11 GPU bottlenecks
40:54 AI hype
45:50 AI spending
48:47 Dax’s memo
55:41 Dax’s skepticism of predictions
58:58 Engineering culture at OpenCode
1:02:38 How building works at OpenCode
1:05:36 Taste and quality
1:11:32 Dax’s work setup
1:12:35 The role of engineers and EMs
1:15:50 Advice for engineers
1:18:12 Book recommendation
Brought to you by:
• @AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages https://t.co/AKYm4cbVCU
• @WorkOS – everything you need to make your app enterprise ready https://t.co/aiAee0oF5h
• @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable https://t.co/w9y67Gs8ab
Three interesting thoughts from Dax:
1. No AI-native coding agent company is “winning” by being better with AI.
Dax says that none of OpenCode’s competitors are crushing them, and that nobody is using AI so well that others cannot compete.
2. Most software engineers profit from AI as time gained, not increased output — unless you change incentives!
Dax says the natural way for software engineers to “cash out” their AI tooling gains is with time savings, by doing the same work as before, but faster. Until compensation and motivation structures change, most teams should expect output to stay flat while engineers go home earlier. There’s nothing wrong with this, but AI vendors sell a different outcome to CFOs: increased output.
3. AI code generation mutes the “guilt” of doing the wrong thing, but this builds up tech debt.
Pre-AI, writing a hack felt bad, the second time it felt really bad, and by the third time you’d often just refactor in order to fix up the code. Now, the agent hides the hack, which skews devs’ judgment and results in less tech debt being cleaned up.
Really fascinating podcast from @davidsenra and @RickRubin on @FoundersPodcast! Resonated in so many ways with me. The Importance of being curious and and being a listener more than a speaker. Also that it is totally OK not to be motivated everyday but still show up! Great pod!
Rick Rubin: “I've always been true to what I feel and it's worked out. The fact that I've stayed true to what feels right to me, and luckily by the grace of God it has resonated with other people, allows me to continue doing it. But I suppose if that didn't happen I would just make things for myself on a small level and keep doing it and have a real job.”
„Je mehr man sich darüber identifiziert, dass man jemand ist, der Code schreibt, desto schwerer wird man es haben. Weil dann konkurrierst du mit einer Maschine und die schreibt schneller Code als du.“
Whow! Das Interview mit Golo Roden hat bereits mehr als 1000 views auf YouTube! Absolut empfehlenswert
„Das Schreiben von Code war eigentlich nie das Problem“
https://t.co/qULz2zHOtv
I'm not gonna lie, the @Meta layoffs are some of the most dystopian I've ever seen. They got told to work from home, they were sent the emails at 4AM in the morning. Those who weren't impacted have software on their computer that tracks their every move, preparing AI to take their job as well. They're literally training the AI that will eliminate their position as well.
Meanwhile, Meta is raking in RECORD PROFITS.
I am a massive, unapologetic AI enthusiast. Yet, this is NOT the future I had in mind.
I wish for Meta to crash and burn. This is not the way. Literally nobody benefits from this.
I recently read an article about people giving ChatGPT their credentials and using it as a password manager. Whenever they need a password, they just ask ChatGPT.
Please don’t do this. Seriously! Just don’t. It’s a terrible idea!
@0xMovez@bcherny Niklas Gustavsson is just awsome! Had a great episode with him on my podcast where we talked about How Spotify Builds at Scale in the Age of AI
https://t.co/rUplDz8MEp
Creative writing is one of the key skills for the future. Even when LLMs get more powerful, a system for clear thinking and a way to organize thoughts will help you to make the difference.
I am starting to get more and more interest in @Substack platform. My podcast @byndcodepodcast will be there as well. So if you be over there make sure to check out: https://t.co/7gkHGTDPEw
Definitely need to learn more about substack. But like what I see with curiosity!
@timheuer@Airbnb@AirbnbHelp A common thing that I see as well. Things will not get better when they now think we introduce AI to replace human relationship as well. This is all part of saving costs at the point where you build the most trust and a loyal customer base.
@dtraub Lots of challenges we face comes down to distributed systems, system design in form of DDD, and things we do for reliability. We just won a new abstraction on top. Good, well thought out architecture is the key. Will read your article and the Reddit. Thanks for sharing
Tolles Interview mit Golo Roden von The Native Web! Hat Spaß gemacht!
🎧🎙️New Episode Drop🔥
„Das Schreiben von Code war niemals das Problem“
Spotify: https://t.co/24G6eO6Bhb
Apple: https://t.co/BaRyZeEgPK
📺 YouTube: https://t.co/qULz2zHOtv
@Dorizzdt We call that „Eisheiligen“ around here. That’s usually a phase in May were it gets really cold before the summer begins. This is roughly a week and makes the wine grapes taste really good for a great wine. Hope you had great wine as well while you are in this area. Enjoy!