Replying to @JWPAX3051
Yes. The best PRs I've seen have more red than green. What's the biggest deletion you've shipped?
Replying to @LauraLoumd
"Ask for the email at the moment it saves them work" is the line. I'm learning the same thing. A report people can open and judge on their own explains my product better than any description. Which template got shared the most?
Steal it! The rule behind it is simple: a claim only gets "Verified" if the agent re-checked it. If it didn't, it has to say "Unknown". What are you building? Curious where you'd use it.
Replying to @LauraLoumd
Sorry, missed this! My gut: the ones who reply stay longer. Not because of the email, but because replying is a tiny first commitment. Once someone has told you why they came, they've already invested a bit.
Saw something similar this week: the one founder who replied with feedback is the one still using what I built.
Means a lot coming from you. That line is going on my wall
If you ever want to see where a stranger gets stuck on one of yours, happy to run it, free.
Senior engineers don't write more code.
They delete more code.
Thoughts 💭🤔?
#buildinpublic #softwareengineering
My work week:
Korean standup at 6am
US client calls at 10pm
Chai in between
Remote work from India isn't a compromise. It's an arbitrage.
Too good...
The part about reliable AI agents and verification caught my attention.
We're moving from “AI can write code” to “can we trust what it builds?”
As developers, shipping faster means nothing if we skip verification. 👀
Learn how to become a better software engineer from an Apple veteran with over 12 years of experience building products.
This The Programming Podcast episode is with @RayFernando1337 and @leonnoel!
00:00 Meet Ray Fernando: 12 Years at Apple
01:51 How Ray Uses AI Agents to Build Software
05:24 The Real Cost of AI Agent Workflows
07:25 Automating Email with AI
10:52 A Word from Our Sponsors
13:13 Building Reliable AI Agents and Verification Systems
18:31 How to Keep Up with AI as a Software Engineer
21:01 Skill Chaining: Building Better AI Workflows
24:05 CSV vs. JSON and Why AI Constraints Matter
26:32 Claude vs. Codex vs. Gemini: Choosing the Right Model
31:17 Leon's AI Workflow for Shipping Code Faster
35:41 Behind the Scenes of Undersold AI
39:01 When Is an AI Product Ready to Launch?
43:04 Why Danny Walked Away from Two Software Projects
48:40 Fail, Pivot, Grow: Turning Failure into Progress
49:13 From Wedding DJ to Apple Engineer
53:09 How to Build Relationships and Network in Tech
58:19 What It Takes to Succeed as an Engineer at Apple
1:02:56 What Separates Great Engineers from Average Engineers?
1:06:50 Listener Q&A: What AI Portfolio Project Should You Build?
1:10:52 Why Most Developers Build the Wrong Portfolio Projects
1:14:41 Final Thoughts and Outro
First User gets your URL and one goal in plain words, never your docs. If your landing page doesn't explain it, the agent gets stuck exactly where a stranger would.
#BuildInPublic #DevCommunity
Terminal, always.
Why move my hand to the mouse when I can introduce 3 new bugs with one command? 😂💀
Developers, settle this debate 👀
When it comes to Git, what’s your go-to?
Terminal — real ones type their commits
Git extension — visualizing the chaos is easier 😂
No judgment. Just curious who’s winning this battle 👀
#BuildInPublic #DevCommunity
Replying to @zafarib
Great question. Short answer: it does read your landing page, but so does a real first user. That's the test.
It only gets a goal in plain words ("buy a plant"), not your docs. It writes its first impression + hesitations before acting, so you see what your page says on its own.
Honest limit: the model may already know big brands. Works best on new products.
Replying to @zafarib
Building First User — an AI agent that tests your web app like a real first-time customer, catches where users get stuck, and tells you exactly what to fix.
Basically, your first user before your actual users. 👀
Yrr, why is recording yourself so awkward 😭💀
I can literally speak in front of 100+ people, but the moment a camera is pointed at me, I forget how to act normal
I can feel your pain, sir. Camera ke saamne toh meri bhi saari public speaking skills resign kar deti hain 💀😂
Replying to @LauraLoumd
Building First User, an AI agent that tries your site like a first-time customer and shows where people get stuck. neatHack results drop today 🤞
Funny overlap with your work: I think the best growth loop is just fixing where new users quietly leave. Which loops are compounding for you so far?
Founders: when was the last time you tried your own signup like a stranger?
Not as the person who built it. As someone who's never seen it.
Most bugs that cost you users don't throw errors. They just make people quietly leave.
I built an agent that does this for you 👇
The team behind First User:
🧠 one observability tool (@neatlogs )
🤖 one coding agent
☕ one me
3 days. Tusi trio was cooking
#Build #buildInpublic #neatHack
One @neatlogs watching every step.
One coding agent writing the code.
One me making the calls.
This trio is cooking something 👀
First User was just the start.
firstuser-dv.vercel.app
#buildinpublic
A founder ran my agent on his live site.
It flagged that pricing info was confusing.
He replied with feedback.
I shipped the fix the same morning.
That's the whole loop I'm building:
find it → fix it → check again.
Thanks @TheXSami
Replying to @TheXSami
@TheXSami
First User read doodle.samistudio.nl and suggested what a first-time visitor should try. Here's the brief: firstuser-dv.vercel.app/brie… #neatHack via @devsdv_





