Saw the Clawdmeter project today and got inspired to build a Wear OS telemetry dashboard for Claude Code on my Galaxy Watch 🦞
Now I can monitor AI agent usage, reset timers, telemetry and a tiny pixel-art mascot directly from my wrist.⌚
Still prototyping.
I decided to turn all my research, experiments, and engineering discoveries into OptimizeDeals, an AI-native software engineering studio.
Lately I’ve also been using AI to write deeply technical and educational articles.
Latest article
https://t.co/kJQ6yT9Sru
25/ Final thought:
Don’t outsource engineering judgment.
Use AI to accelerate execution and compress iteration cycles.
Keep ownership of architecture, standards, and decisions.
Build repositories for both HUMANS and agents.
That’s where leverage stays.
Most developers optimize for bigger context windows.
Useful, but the real leverage is usually architecture, task design, and token economics.
You don’t always need more AI.
You need better systems.
Here’s how I use Claude efficiently for real delivery. 🧵+
24/ Mental model:
AI throughput =
(Architecture × Task Clarity × Context Efficiency) / Noise
Noise is expensive.
Ambiguity is expensive.
Sprawl is expensive.
--> SUPER EXPENSIVE, especially when you use HIGH EFOOOORT