Ajith Bhat (ಅಜಿತ್)

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@thekitze At that point, you will miss the mess created by the kids in the car 🙃

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@threepointone Also, we have to make far more decisions in the same amount of time

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@TheRohanVarma https://t.co/TSPEKkwOPL

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@GergelyOrosz Enemy of my enemy.

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@bryncurran Awesome! Congratulations mate!

[Jeff Huber @jeffreyhuber]

OpenAI is shutting down text-embedding-3-small?!?

I strongly believe that if you shut down a closed-source embedding model that you should open-source. Imaging the trillions of tokens that will no longer be queryable.

cc @romainhuet

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

Congrats on the ship! Two ideas worth considering:

1. Invert the model — let users exclude topics (e.g. hide politics) rather than pick them in. Keeps the full following graph intact minus the noise.

2. Allow combining several topics into one tab with an optional filter, to cut the cognitive load of tab-hopping.

A few things I'm running into already:
- Same post shows up in both Tech and AI (duplicates across overlapping topics)
- No indicator of which tabs I've already visited
- Time-sensitive posts feel scattered across tabs and easy to miss

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@denicmarko https://t.co/yfe68qqFK4

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

Watching the Claude Opus 4.7 launch reactions split down the middle today made me want to write down something I've been thinking about for a while — why this exact fight happens every single model launch, and what it's actually about.

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

https://t.co/ZzDBPTwnjm

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

https://t.co/ZzDBPTwnjm

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@thekitze Happy birthday @thekitze !

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

Spotty signal, background noise, rushed sessions — @getjobproof handles it all a lot better now. Big reliability push this week. https://t.co/jaBy9fWpN4

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@PKodmad Hey Duggee, Bluey, and a couple of sticker/colouring activity books. Best of luck. 😂

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

We spent a decade learning that personalised search creates filter bubbles.
Now AI assistants come with persistent memory, quietly shaping responses around what they think you believe.

They’re not hiding answers.
They’re framing them.

Which might be worse.

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@thsottiaux @reach_vb
Do quota resets create a thundering herd?
If everyone’s weekly quota renews at once or gets globally reset after an incident, I’d expect a spike right at the boundary.
Do you mitigate with staggered resets / jitter, or is load smoothing enough?

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

@PKodmad "Works on my machine" 😅
But seriously, just pushed a fix. Should work better now. Give it another try? 🙏

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

Built an app that nags my kid to eat faster so I don't have to. It loops my voice forever. My throat is free. My daughter is not amused 😂

https://t.co/tPhcsMwwTs
ಬೇಗ ಬೇಗ

[Ajith Bhat (ಅಜಿತ್) @AjithBhat]

A few things that help when you're flying blind on vibe-coded Swift:

1. Ask Claude to add logging/instrumentation first, reproduce the bug, then diagnose from the actual output — it reasons much better from evidence than description

2. Ask it to web search the specific APIs it's using — SwiftUI has known performance gotchas per version that are easy to miss

3. Ask it to isolate the slow path into a minimal reproducible case — vibe-coded apps tend to have tangled state, and isolation usually reveals the real culprit