@Jodo_in Eng Director by day, Dad in evening, hacker at night.
Joined August 2009
- Tweets 2,975
- Following 235
- Followers 546
- Likes 1,776
271 Photos and videos
Apr 5
While working with Claude, I spent some time understanding how compaction works. The short version is: the system doesn’t really “remember” everything, it rewrites the conversation into something shorter.
1
42
Apr 5
I’ve written this down properly with examples and what this means in practice: codingdash.com/post/understa…
1
1
30
Apr 5
This is part of a larger series on building systems on top of Claude: codingdash.com/series/automa…
#Claude #AIEngineering #AgentDesign
25
Mar 28
Most teams are still treating Claude like a smarter autocomplete.
That works until it doesn't, and when it breaks, it breaks in ways that are genuinely hard to debug. Not errors. Inconsistency. Context drift. Outputs that were fine yesterday and aren't today.
I've been thinking about why some teams compound on this and most don't. Turns out it comes down to one thing they do differently from the start.
Wrote it up: codingdash.com/post/treating…
#claudecode #softwareengineering @AnthropicAI
1
5
51
Mar 22
1/ During the 2015 Chennai floods, our data centre went dark. What I remember most isn't the outage. It's what Vishnu and I built in response.
1
1
4
80
Mar 22
4/ 10 years later the ideas we tried and shelved at Exotel are now funded product categories.
Sentiment analysis on calls. SOP to workflow automation. Voice biometrics.
The vision always existed. The capability layer just arrived.
But the infrastructure layer hasn't caught up. 95% of AI voice pilots are failing. Less than 1% of contact centres have autonomous agents in production.
1
1
68
Mar 22
5/ I wrote the full piece. Field report from inside the infrastructure.
The graveyard of correct ideas. The concurrency problem. The India opportunity. The pricing model that's being made obsolete.
codingdash.com/post/state-of…
4
63
Mar 21
I started blogging on codingdash.com in 2014 as a college student. Same blog. Still running.
The name came from @codinghorror's Coding Horror, named after an icon in Steve McConnell's Code Complete, used to flag cautionary examples of bad code. That lineage felt right, and codingdash stuck. It's been my corner of the internet since.
Shipped a redesign this week. The second one since starting, the first redesign I did in 2020, inspired by @Stammy's site. This one was overdue not because something broke, but because the site had quietly fallen behind the person writing it.
Short note on what changed: codingdash.com/post/a-new-co…
5
74
Feb 22
I spent a long time looking for an AI code review tool that actually fit how my team works. Tried a few. None felt complete.
Hidden costs. No control over which model runs. Guidelines that were either too generic or too rigid to customise. And when things broke, no visibility into why.
So I built one over a weekend and open sourced it.
PRLens — bring your own Claude or GPT-4o key, bring your own guidelines, runs as a GitHub Action in your own pipeline. No new vendor. No black box.
Still early, lots to build. But the foundation is there and I'd love collaborators who've felt the same frustrations.
github.com/prlens/prlens
1
6
108
Feb 21
Most AI-powered products hide their real cost structure. They bundle model inference into a flat subscription or per-seat price, the same way early SaaS bundled AWS costs. But there's a key difference: AI model pricing is dropping 50-200x per year and the provider landscape shifts every few months.
When your cost base is that volatile, bundling it creates problems:
- You can't pass savings to customers as models get cheaper
- You can't let customers bring their own API keys (which they increasingly want)
- You can't give enterprises the compliance visibility they'll legally need by August 2026
The question every AI builder should ask: what is my product worth independent of the model running underneath it?
If the answer is clear, decouple the burn and prove it.
codingdash.com/post/your-ai-…
2
4
83
Jan 26
The Joel Test turned 26, @spolsky.
Source control? That's oxygen now. Daily builds? Elite teams deploy hourly.
Here's the 2026 version—12 new questions for modern engineering teams.
codingdash.com/post/the-codi…
1
4
139
29 Nov 2025
If you start behind, you cannot walk at the same pace as those who began ahead. The train is moving. You have to run.
#GrowthJourney #StartBehind #CatchTheTrain #Mindset #BlogPost
codingdash.com/post/catch-th…
1
6
193
9 Feb 2025
Another year. As of Feb 2025, the journey continues—every upgrade, every tweak, still feels like day zero. #WorkstationEvolves #DeskSetup 🚀
1
4
347
27 Nov 2025
I usually refresh my workspace every February, but this year I moved the upgrade forward to November. A cleaner desk, better setup, and a more organized reading corner.
As always, my junior auditor stopped by for a quick quality check. 💛📚
3
114
28 Jun 2025
Published a new article: Invisible Bugs codingdash.com/post/invisibl…
#CodeReview #TechDebt #InvisibleBugs #AI #SystemDesign #DeveloperVelocity #BlogPost
1
3
128
27 May 2025
Finally pulled together a proper Bookshelf section on my blog.
It includes some of the most impactful books I’ve read around tech, leadership, and systems—as well as what I’m currently reading.
Check it out. codingdash.com/bookshelf/
1
1
5
140