Really glad to see the industry converging on this.
Back in May, we wrote "From Vibe Coding to Agentic Engineering" and got on stage at SVB with engineers from Google DeepMind and Mastra to make this exact case:
"You're not just writing code — you're designing the environment that code lives in... letting agents operate within that environment, but always within constraints that make the outcome trustworthy."
Whether you call it an Agent Habitat or Agentic Engineering, the shift is the same: when code generation approaches zero cost, trust becomes the bottleneck.
One piece we'd add: the boundary can't just be a sandbox around the agent. Authorized agents still touch data—so permissions and Row-Level Security have to be compiled deterministically into the database core itself.
Vibe code the edges. Trust the core.
📝 Our essay: https://t.co/V9jcA2LWDr
🎥 Full May 1 SVB panel (just dropped today): https://t.co/AfzIsgNYuU
https://t.co/jaF5y9yJnT
@BrainsAndTennis This looks cool .
At @tennishackery ( https://t.co/K27OUMpqiO) we are building a fast coaching loop based on match play . Would love to explore this more as this will be a very important coaching tool .
@bnp_cricket@varunmurali43@bisibelebhaat@notytony@knittins Yes . Missed ya all . This pod had an awkward start then great banter and then hit rock bottom
- devolved into well reasoned and informed discussions on cricket globalization . Booo
Say hello to Rexie, our mascot for Rex! Superlogical public testing is beginning. We’re working through our mailing list in the order people signed up. Initial testing is limited to macOS but that’ll expand quickly. Welcome, new testers. https://t.co/qNfJnhjnQn
@ThePrimeagen Now more than ever first principles based design and engineering is super super important . The temptation is to abstract away the problem with AIs. Pick the wrong level and you end up with a mess .
@ID_AA_Carmack Tried scratch for my kids during pandemic - it was interesting and visual . But did not help . Learning via Roblox/Minecraft had a better effect . Does it also make sense if programming was taught as a skill that kept pace with the math curriculum ?
How is CI/CD changing because of AI, and what are sensible deployment practices more teams should be doing? Robert Erez is a CI/CD expert, and also my former teammate at Skype. Timestamps:
00:00 Intro
02:09 Canary deployments at Skype
05:01 Joining at Octopus Deploy
06:15 Continuous deployment
10:26 Why Kubernetes won
15:51 Kubernetes on-prem
18:50 How GitOps works
25:00 The uses and limitations of GitOps
31:04 The rise of platform teams
35:51 How AI is changing CI/CD
39:49 Progressive delivery explained
47:31 Rollbacks and roll-forwards
50:14 Feature flags
54:32 How development environments are evolving
57:40 Cloud development environments (CDEs)
1:03:45 Self-hosting CI/CD
1:09:25 Getting started with progressive delivery
1:11:15 Book recommendations
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/AKYm4cctss
• @WorkOS – everything you need to make your app enterprise ready https://t.co/Xxf2A82QmK
• @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. https://t.co/w9y67GsFZJ
Three interesting thoughts from Rob:
1. Roll forward, never backwards.
When a system has state – which typically means it uses databases – then doing a rollback can leave the code talking to a schema that’s no longer in sync. Rob’s advice is to not treat a failure in v2 as a trip back to v1, but rather as a push to v3 with the fix in it.
2. GitOps isn’t actually about Git.
None of the four pillars of GitOps – 1) declarative, 2) versioned and immutable, 3) pulled, not pushed, 4) continuously reconciled – require Git, although Git can work under these constraints. Yet, the term ‘GitOps’ has made the industry dogmatic about cramming everything into a repo – even things like secrets that absolutely shouldn’t be there!
3. There’s a trend of ephemeral environments replacing test/staging environments across the industry.
Companies used to have a few testers fighting over a handful of static test environments, but today, it’s trivial to spin up a full environment, per-feature branch, pre-merge. This is an “ephemeral” environment for evaluating that things work, which is then torn down once something is merged. It helps speed up the feedback process.
Here's my conversation all about @FFmpeg, the legendary open-source software powering most video on the Internet. In the episode, I talk with Jean-Baptiste Kempf and Kieran Kunhya. JB is lead developer of VLC and Kieran is FFmpeg contributor, codec engineer, and the person behind the now-infamous @FFmpeg account on X.
VLC (@videolan), by the way, is also a legendary piece of open-source software: it's a video player that can open basically anything & has been downloaded over 6 billion times.
I think both FFmpeg and VLC are two of the most important and impactful software systems ever created, both open source, and both created & maintained by volunteers: brilliant engineers from all walks of life.
Thank you to everyone who contributed to FFmpeg and VLC, and in general to all engineers giving their heart & soul to building systems used by millions (or billions) of people, and often doing so not for money, status, or fame, but purely for the love of building great software and doing good for the world.
Thank you to the builders! 🙏❤️
Shoutouts in this chat to @ID_AA_Carmack@karpathy@elonmusk@TimSweeneyEpic and everyone who is a contributor & fan of open source!
It's here on X in full and is up everywhere else (see comment).
Timestamps:
0:00 - Episode highlight
2:17 - Introduction
5:35 - Weirdest things VLC opens
9:59 - How video playback works
19:20 - Video codecs and containers
30:07 - FFmpeg explained
51:07 - Linus Torvalds
55:46 - Turning down millions to keep VLC ad-free
1:10:04 - FFmpeg & Google drama
1:29:18 - FFmpeg developers
1:35:55 - VLC and FFmpeg
1:40:29 - History of FFmpeg
1:43:46 - Reverse engineering codecs
1:57:01 - FFmpeg testing
2:01:08 - Assembly code (handwritten)
2:25:26 - Rust programming language
2:34:42 - FFmpeg and Libav fork
2:43:04 - Open source burnout
2:50:51 - x264 and internet video
3:04:07 - Video compression basics
3:11:04 - CIA and fake VLC
3:21:39 - Ultra low latency streaming
3:39:07 - AV2 codec and video patents
3:48:59 - VLC backdoors
3:59:14 - Video archiving
4:05:51 - Future of FFmpeg and VLC
@lexfridman@FFmpeg Half way through the episode and i just don’t want it to end . Amazing stuff and hats off to their work . I use @FFmpeg a lot - and it’s a gift to the world .
@himganj153 Google scoops up most widely available info on this and the discourse was and prob is still LR being the best . Different matter that the TV networks are picking this up . Obv not up to date . tbh If you ask club cricketers they will say they hate LR due to plain laziness 😂
@himganj153 Do try DAC and look for remastered sound channels and chill . Like you I hate wireless buds - constant recharging , carry chargers around , connectivity issues and loss of sound fidelity .
@steipete Indeed 8GB is rough - Apple doing lots of memory precaching just running safari will jack up the memory pressure . Not sure if they are doing other optimizations to make this usable