Weekly interviews w/ top technical founders + leaders, to stay fresh on how software + AI actually work. Hosted by @meganreyno, new eps every Thursday ↓
Joined January 2020
- Tweets509
- Following64
- Followers4K
- Likes490
Technically retweeted
In this video essay for @readtechnically, Sung (Solutions Architect here at @coplane) explains:
- what are FDEs and what do they do
- why you've been hearing so much about FDEs lately
- how this role is going to be critical for the next era of software
youtube.com/watch?v=aDq09Tyf…
Technically retweeted
I Let Claude Code Autonomously Run Ads for a Month, by @readtechnically
open.substack.com/pub/techni…
Technically retweeted
AI and neuroscience, by @readtechnically open.substack.com/pub/techni…
Technically retweeted
There's probably a dozen legit vibe coding tools out there, and this post offers a comprehensive assessment of four of them (Replit, v0, Lovable, Bolt).
read.technically.dev/p/2026-…
Technically retweeted
This article from @readtechnically highlights @Replit as "the most feature rich, well thought out, and powerful" vibe coding tool, receiving the highest score amongst the 4 platforms the author tested.
There's probably a dozen legit vibe coding tools out there, and this post offers a comprehensive assessment of four of them (Replit, v0, Lovable, Bolt).
read.technically.dev/p/2026-…
Technically retweeted
Most people don't realize that MCP started as a weekend project; it wasn't intended as some masterstroke by Anthropic.
This is part of why the spec is so low level, and it's so hard to build an MCP server from scratch. @fastmcp fixes this by doing all of the boilerplate for you:
Technically retweeted
Developers don't read marketing sites. They read docs.
Bad docs = lost users, yet most companies treat documentation as an afterthought.
Collaborated with @readtechnically on this piece about what separates good docs from great ones: read.technically.dev/p/whats…
Technically retweeted
Steve Jobs (or was it Sun Tzu?) once said "if the product needs a manual, the design has failed."
Well, Steve would hate modern software. Everything from Gmail to developer APIs needs docs—and nowhere is this more true than dev tools and infra.
A thread on documentation:
Technically retweeted
I've been getting requests to explain what an "architecture" is in the context of AI:
AI architectures are basically model blueprints. they are the sum of all the decisions you make about what algorithms, data, sizes, and other stuff go into said model.
Technically retweeted
Good to get back to the basics. JavaScript is the most popular programming language in the world...how does it work?
read.technically.dev/p/whats…
Technically retweeted
It’s 2025, and there’s only one question on every company’s mind:
“How do I add as many mentions of AI as possible to our website?”
These “AI Makeovers” have been plaguing the nation. We need a hero to bring them to justice
Technically retweeted
The reason that your engineers are taking forever to build your feature is probably code reviews. They wrote the code, but it's stuck in some kafkaesque review process that doesn't do much anyway. And AI generated code is about to blow all of this up in a big way
Technically retweeted
So @MistralAI is in the news today for releasing their first reasoning modal, Magistral. But what IS a reasoning model, exactly? How do these things, like @OpenAI o3, actually work? 🥖
Technically retweeted
What MCP is, for non-engineers:
The Model Context Protocol helps models like Claude or ChatGPT talk and work with external systems and data in a standardized way -->
Technically retweeted
I wrote about @v0 a couple of months ago, and framed it as an app for building apps. But the underlying model that Vercel built for v0 (the brain) has gotten so good that you can now use it in other tools, to do as you wish
Technically retweeted
This might seem basic at first glance (OpenAI adding existing features to the API) but it's actually a much bigger deal. They are totally changing up the philosophy of how developers should use model APIs, to prepare for a world of agents:
Technically retweeted
1/ My hot take: LLMs haven’t transformed software engineering yet, they’ve just augmented a human-centric SDLC. For a future where autonomous agents will be writing most of our code, we need a completely redesigned SDLC, from IDEs to CI. A thread on what this will look like…
Technically retweeted
With v0, everybody can cook. @readtechnically's latest post shows how anyone can use natural language to build apps.
vercel.fyi/rSh74Ij
Technically retweeted
What's an SDK?
by @readtechnically
read.technically.dev/p/whats…
