Day 1: I had zero tech background. A friend told me to try Claude Code.
Day 60: βΉ1L/month contract with a UK AI company.
Here's every project I built in between π§΅
Fix was a small background watcher that drops a .done file the moment the result file appears. The agent watches for that instead of guessing.
Stalls went to zero.
Building alerting across two environments taught me the real risk isn't a missed alert.
It's a prod alert landing in your dev channel, and nobody trusting the system after that.
So before any feature: a guard so prod events can't post to dev. 55 tests on that one rule.
My agents can write code now. Writing it was never the problem. Trusting it is.
So I built a gate: when Claude tries to commit its own code, a hook stops it and sends the diff to a different model first. No review, no commit.
One model writes. Another signs off.
@adxtyahq Use an SLM or a smaller model, faster LLM to convert the pre-final result into the validation layer.
This is the classic deterministic vs probabilistic issue with using LLMs, very few reliable ways to get through it.
A client wanted to know the moment their app broke, without drowning in alerts.
Backend through one tool, frontend through another. The rule that mattered: only alert on what's new or just came back.
Alert fatigue kills monitoring faster than missed errors do.
I started listening to Teen Taal last year, and it quickly became one of my favorite podcasts.
For those who don't know it, it's an absolute banger by @kuldeepmishra , @kkstau and @007asifkhan
But after hundreds of hours of listening, one question kept coming back:
"What all have they said about a specific person, place, book, food, or topic over the years?"
That curiosity turned into a side project.
Over the past few months, I indexed 262 episodes and 71,000+ moments from Teen Taal to create a discovery app for the show.
Now you can:
π Search anything
A name, city, book, movie, or even a half-remembered Hindi phrase. Instead of just finding an episode, you'll get the exact moments where it was discussed, complete with transcript snippets and one-click playback.
π Browse TT Staff Letters
One of my favorite parts of the show. Explore letters by sender, see where they were read, and jump straight to those moments.
ποΈ Full episode pages
Transcript and player side-by-side. Click any line in the transcript and start playing from that exact point.
βοΈ Shareable clips
Found a great moment? Share it directly.
π Curated episode lists
Perfect for discovering classic Teen Taal rabbit holes.
Honestly, this has completely changed the way I listen to the podcast.
Would love for fellow Teen Taal listeners to try it out and share feedback.
Link in the first reply π
Be visibly competent.
If you have skills but others do not know about them, you will never get the opportunities you deserve. Make your abilities visible, and ensure that what you bring to the table is impossible to ignore.
Be visibly competent.
If you have skills but others do not know about them, you will never get the opportunities you deserve. Make your abilities visible, and ensure that what you bring to the table is impossible to ignore.
The pre-commit gate won't let anything through without a review receipt from Codex. Different model. Separate pane. Writes its findings before any commit lands.
One machine. One person. Seven projects moving at once.
Here's my actual terminal setup for running parallel Claude Code agents.
7 workspaces. 5 agents inside one project right now. A separate Codex reviewer as its own pane.
This is how I stay coherent across multiple projects at once.
Each agent gets a pane in the right column. They don't talk to each other. They write results to files. The orchestrator in the left pane reads them and decides what's next.
Context per agent stays clean. No single session accumulates 200k tokens of noise and starts making bad calls.
@naw103 Exactly!
After all the orchestration and decision making, context is too high for it to write code. Handing off to a separate agent to maintain a low context window becomes essential.
cmux + good guardrails is the answer to this problem
Keeping the context window clean will be the most important skill in 2026
It's easy once you set it up!
Can someone please build this already?
An IDE that automatically switches models based on the task. Cheap models for simple edits, Claude/GPT for the stuff that actually needs reasoning.
And let me configure the routing rules myself
@adxtyahq Use a multi agent orchestrator like cmux and make the rules and skills yourself
Handoffs to different models based on use case is quite the need of the hour right now
Hit me up if you want to know how to set it up
@shrav_10 100% true. Youtube Music will pull bangers from your teenage years and play them just at the right moment.
Spotify has better playlists, though