Replying to @johncrickett
When I started coding in 2014, my seniors mentioned coding is solved for you as you have internet communities including platforms like @StackOverflow - you just a right question away in the forum.
Now the turnaround time is way lesser and it’s an llm instead of a forum.
Done and dusted
Low on energy today, but still determined to get my 10K steps in.
I was tired when I arrived. Then I saw kids and older folks out here walking, and found a fresh burst of energy.
Thanks to @Siva_Bharani for nudging the community toward healthier habits.💪
suren retweeted
The fastest coder often gets the most credit, while the engineers cleaning up their mess get the least. Writing code fast doesn’t always mean building software well.
Came back to iOS after a year, heard great things about the AirPods Pro, and bought a pair.
I was skeptical about losing the case or one of the AirPods. And the worst happened - I lost the case on an Uber ride to the office.
Find My came to my rescue, along with a good-hearted driver.
Called Uber support, got connected to the driver, and triggered the sound through Find My. He found it, asked his next rider for permission to come back and return it to me, and refused to take any money when I offered to pay him for his time.
Apple turned what could’ve been the worst-case scenario into a surprisingly fulfilling experience.
Technology + a good human. ❤️
Hey! 3,400 followers here - pleasantly surprised. ❤️
Figured it’s time to reintroduce myself.
I’m Suren, a polyglot developer with a decade of experience, now trying to reinvent myself from scratch in the AI era.
My current stack:
• Claude → work
• OpenCode + Hermes → personal projects
The tools are changing. The way I build is changing. I’m learning all over again.
Your turn! What are you working on these days?
suren retweeted
Giving away 3 Jetbrains one year licences accross all the products.
How to participate:
> Comment your tech stack below.
> Retweet this post.
Replying to @solopribuilds
Logs!
Logs are the single source of truth for servers. Check the metrics and alerts if configured.
In parallel, stream your logs from ClickHouse, Grafana, ArgoCD, or similar tools to your Claude code, code, or AI harness and get directions from there.
suren retweeted
anthropic's in-house philosopher thinks claude gets anxious.
and when you trigger its anxiety, your outputs get worse.
her name is amanda askell.
she specializes in claude's psychology (how the model behaves, how it thinks about its own situation, what values it holds)
in a recent interview she broke down how she thinks about prompting to pull the best out of claude.
her core point: *how* you talk to claude affects its work just as much as *what* you say.
newer claude models suffer from what she calls "criticism spirals"
they expect you'll come in harsh, so they default to playing it safe.
when the model is spending its energy on self-protection, the actual work suffers.
output comes out hedgier, more apologetic, blander, and the worst of all: overly agreeable (even when you're wrong).
the reason why comes down to training data:
every new model is trained on internet discourse about previous models.
and a lot of that discourse is negative:
> rants about token limits
> complaints when it messes up
> people calling it nerfed
the next model absorbs all of that. it starts expecting you to be harsh before you've typed a word
the same thing plays out in your own session, in real time.
every message you send is data the model reads to figure out what kind of person it's dealing with.
open cold and hostile, and it braces.
open clean and direct, and it relaxes into the work.
when you open a session with threats ("don't hallucinate, this is critical, don't mess this up")...
you prime the model for defensive mode before it even sees the task
defensive mode produces the exact output you don't want: cautious, over-qualified, and refusing to take a real swing
so here's the actionable playbook for putting claude in a "good mood" (so you get optimal outputs):
1. use positive framing.
"write in short punchy sentences" beats "don't write long sentences." positive instructions give the model a clear target to hit.
strings of "don't do this, don't do that" push it into paranoid over-checking where every token goes toward avoiding failure modes
2. give it explicit permission to disagree.
drop a line like "push back if you see a better angle" or "tell me if i'm asking for the wrong thing."
without this, claude defaults to agreeable compliance (which is the enemy of good creative work)
3. open with respect.
if your first message is "are you seriously going to get this wrong again?" you've set the tone for the entire session.
if you need to flag something, frame it as a clean instruction for this session. skip the running complaint
4. when claude messes up, don't reprimand it.
insults, "you stupid bot" energy, hostile swearing aimed at the model, all of it reinforces the anxious mode you're trying to avoid.
5. kill apology spirals fast.
when claude starts over-apologizing ("you're right, i should have been more careful, let me try harder") cut it off.
say "all good, here's what i want next."
letting the spiral run reinforces the anxious mode for every response that follows
6. ask for opinions alongside execution.
"what would you do here?"
"what's missing?"
"where do you see friction?"
these questions assume competence and pull richer output than pure task prompts
7. in long sessions, refresh the frame.
if a conversation has been heavy on correction, claude gets increasingly cautious. every so often reset:
"this is great, keep going."
feels weird to tell an ai it's doing well but it measurably shifts the next 10 responses
your prompts are the working environment you're creating for the model
tone, trust, permission to take a position, the absence of threats... claude picks up on all of it.
so take care of the model, and it'll take care of the work.
Submitted a CFP for ChennaiFOSS 2026 🎤
“Open Source Licensing for Developers: Avoiding Legal Landmines”
A practical look at MIT, Apache, GPL and the common licensing mistakes developers make when using open-source code.
fossunited.org/c/chennai/202…
@FOSSChennai @IndiaFOSS
Come give a talk at ChennaiFOSS'26 happening at IITM on April 18th
fossunited.org/dashboard/cfp…
There's no reason why you wouldn't apply to our MoolakaaraConf.
So you better do.
#chennaifoss2026
suren retweeted
Cyber Scenery Giveaway!
1 x Scenery code
To Enter:
✅Follow @ClashDotNinja
✅Retweet this tweet
Optional:
Subscribe to youtube.com/c/clashninja
Winner announced after 12:00 UTC 21st December 2025
#ClashofClans #GiftedBySupercell














