I’ve been in that mindset too — where one rejection starts feeling like proof that maybe you’re not good enough.
That’s the dangerous part. You stop treating rejection as an event and start turning it into an identity.
What changed for me was simple: extract the lesson, fix what you can, and move to the next attempt. Rejection only becomes expensive when you carry it longer than necessary.
Hey @X algorithm —
Connect me with founders sitting on a business problem they KNOW technology could solve, but haven’t had the time or team to build it.
We build AI agents, workflow automations & custom software.
If that’s you, DM me.
Tell me the problem, not the solution. Let’s figure it out.
#Founders #AI #Startups
10 more to hit my first 100 followers on X 👀
If you’re also early here — building in public, shipping something, figuring things out, and starting from almost zero — let’s connect
#BuildInPublic#Startups#Founders#IndieHackers
Let’s roast AI in one line. I’ll start:
AI is that coworker who says “done” with full confidence… then you open the file and realize they understood 60% of the task. 💀
Your turn. 👇
#AI#ChatGPT#Claude
Anyone using @OpenAI Codex or @AnthropicAI Claude Code probably feels this already:
Coding is moving from implementation-first → definition-first.
The valuable work increasingly happens before the agent writes a single line:
problem
→ requirements
→ architecture
→ interfaces
→ constraints
→ acceptance criteria
Then the agent implements.
If your definition is vague, AI gives you vague software — just much faster.
This is basically senior engineering at scale:
define → delegate → review → iterate.
The best developers in the AI era won’t be the fastest typists.
They’ll be the people who can define exactly what should be built.
#AI #CodingAgents #SoftwareEngineering #DevTools #ClaudeCode #Codex
Writing syntax was never the end goal.
Building software that actually solves the problem was.
As AI becomes reliable, the advantage shifts to:
→ understanding the problem
→ defining the system
→ making architectural decisions
→ setting constraints
→ verifying the output
Don’t confuse today’s METHOD with the actual SKILL.
Methods change.
Purpose doesn’t.
Hot take:
Our parents memorized phone numbers and entire routes because there was no reliable alternative.
Writing code by hand is heading toward the same place as memorizing phone numbers.
Useful to understand? Yes.
Something everyone will need to manually do? Probably not.
@OpenAI@claudeai are already pushing us in that direction
I use @WisprFlow now and barely type.
Have I forgotten how to communicate?
No.
Typing was never the purpose.
Expressing my thoughts was the purpose.
Voice simply became a better interface.
I think coding is going through the exact same transition.
Our parents memorized dozens of phone numbers, roads, train routes and bus routes because they HAD to.
Then Contacts and Maps became reliable.
We didn’t become less intelligent.
We simply stopped doing work that machines could reliably do for us.
The purpose stayed. The method changed.
Anyone building something in healthcare in India right now?
Healthtech, hospital software, patient experience, diagnostics, care coordination, AI — anything serious.
I’m exploring this space too and would love to connect with founders/operators actually building.
If that’s you, reply or DM.
#HealthTech #Healthcare #Startups #India #DigitalHealth #Founders
The real gap in healthcare is what happens after the 10-minute consultation.
A patient pays, gets a prescription and medicines, and leaves. But treatment shouldn’t end there. It should continue until recovery—with a clear treatment plan, reminders, follow-ups and callbacks, without adding more workload for the hospital.
Patients don’t just need a prescription. They need to feel that someone is actually managing their recovery.
@theamitdusane Helping hospitals deliver a better patient experience — from appointment to recovery. Mainly with WhatsApp connectivity
Just started in this area last week