Pinned Tweet
On my way to learn AI by building an app:
✅ Figure out user flow
✅ GraphQL resolver to upload the CSV
Next up:
⏳ UI (although I like Altair 🤪)
⏳ Job Queue for the AI stuff
I recorded a screencast this time
#code #buildinpublic
teapaw.org/swashata/status/194318…
I have the basic app (Nextjs & my old own GraphQL server) up & ready and have figured out to have AI analyze the statements. Next 👉
- Create API & UI
- Ready the MVP
- 🚀 😅 🙀
I thought I'd share some code sneak peek too 😬
teapaw.org/swashata/status/194103…
Nice try @urbancompany_UC , you are now blocked 🤣 Send me a letter when you actually become a phone app to count my missed calls
Swas retweeted
How I do code reviews these days: more code = more selective human review i.e. don't read all the code.
1. Every PR gets a multi-agent first pass. It should find bugs, verify them, rank by severity, suggest fixes. Approval stays a human call on anything that matters.
2. Low blast radius changes on less sensitive code (there's often a lot!) can skip a deep human review once that review is clean. This helps keep the explosion of PRs manageable.
3. Core / sensitive paths still need an owner and human sign-off. That's where you spend time: verification, constraints and earning trust in what the agents can safely cover. You want to keep recoverability.
Agents do the first pass and humans cover blast radius.
Great question from @GergelyOrosz!
Oh come on! I like AI a lot, but this is just overstatement on steroids
With Codex, @asana finished a frontend test migration from Enzyme to React Testing Library in two calendar weeks—a project expected to take five more years.
openai.com/index/asana/
















