Nikhil Nelson

⚡️ 4x Founder → Building solo bets
Trying Apps for a change

[Nikhil Nelson @SoloHacker47]

my android app was applied for production access but got rejected telling more testing is required, i had 12 testers opted in but one tester actually installed and did overall testing
anyone have any insights?

[Nikhil Nelson @SoloHacker47]

Build in public update:

I applied for production access for my Android app.
Small milestone, but it means a lot right now.

I was recently diagnosed with Myasthenia Gravis, and I’m going in for thymectomy surgery tomorrow.
Maybe by the time I’m back, there’ll be a reply waiting.

To anyone building through health stuff, I see you.

Prayers appreciated 🙏

[Nikhil Nelson @SoloHacker47]

Things that feel productive but usually aren’t:

✅ changing the logo again
✅ rewriting the landing page headline 14 times
✅ adding “just one more feature”
✅ watching another SaaS tutorial
✅ checking analytics every 9 minutes

The real work is usually boring:

Talk to users.
Ship the fix.
Ask for feedback.
Repeat.

[Nikhil Nelson @SoloHacker47]

@00Sindirella hello

[Nikhil Nelson @SoloHacker47]

@1Umairshaikh distribution

[Nikhil Nelson @SoloHacker47]

Is it common for every app to have 14 days testing period, or is this because its my first app?
any pointers before launch?
marketing tips? (I am thinking of google ads, any specific advice?)

[Nikhil Nelson @SoloHacker47]

Building in public is basically committing to being slightly embarrassed every day until the product gets better.
Today’s progress:

✅ shipped one small improvement
✅ found one bug
✅ learned something I’ll reuse tomorrow
Small steps, public logs, compound wins.

#buildinpublic

[Nikhil Nelson @SoloHacker47]

@jehniiee hi

[Nikhil Nelson @SoloHacker47]

One mistake I keep making with side projects:

I start with features instead of distribution.

Bad question:
“What can I build?”
Better question:
“Where do people already complain about this problem?”

The product should come from the pain, not from my Notion idea graveyard.

[Nikhil Nelson @SoloHacker47]

@perkmaybe hello

[Nikhil Nelson @SoloHacker47]

As a developer, your unfair advantage is speed.

You can wake up with an idea and have a working version live by night.

That’s insane leverage.

Don’t waste it waiting for the “perfect” SaaS idea.

Build small.
Ship fast.
Let the internet roast it into shape.

[Nikhil Nelson @SoloHacker47]

is my X account not being discovered how will I know it?
my impressions area at 6 to 10, anybody comment if there is any problem?

[Nikhil Nelson @SoloHacker47]

@KevinSzabo14 I totally agree with this, sometimes its tough

[Nikhil Nelson @SoloHacker47]

@sevalla_hosting stack overflow was the time....

[Nikhil Nelson @SoloHacker47]

This is really good

[Mohini Shewale @s_mohinii]

🚨𝗕𝗥𝗘𝗔𝗞𝗜𝗡𝗚: Build your next app without spending a dollar on data.

Someone made a list of 320,000+ free public APIs, and developers are going crazy.

→ Weather, finance, news, sports, crypto
→ AI & machine learning APIs you can call right now
→ Government open data, maps, geolocation
→ Entertainment: movies, music, games, anime
→ Categorized, searchable, and verified as working

Free and 100% open source. Link Bellow:👇 just like + comment " send" + repost+ Follow me so that it can be auto DM.

[Nikhil Nelson @SoloHacker47]

Everyone is asking:
“Will AI replace developers?”
I think that’s the wrong question.
The better question is:
“What part of being a developer was never actually about typing code?”

I’m Nikhil Nelson, a backend engineer with 5+ years of experience building Ruby on Rails apps, debugging production issues, working with databases, APIs, payments, background jobs, and lately experimenting with AI-powered products.

And the more I use AI for coding, the more I’m convinced of one thing:

AI is not replacing good developers.
It is replacing unverified output.
Here’s what the data is quietly showing.

Stack Overflow’s 2025 Developer Survey says 84% of developers are already using or planning to use AI tools in their development workflow.

So yes, AI coding is mainstream now.

But here’s the twist:
Developer trust is going down.
Stack Overflow later reported that only 29% of developers said they trust AI tools, even though adoption keeps rising.

That means developers are using AI more, but trusting it less.

That sounds contradictory.
But if you code for a living, it makes perfect sense.
AI is amazing at:
generating boilerplate
explaining unfamiliar code
writing first drafts
suggesting test cases
converting rough ideas into structure
helping you move faster when you already know the destination

But AI is still weak at something very important:

Context.

It does not fully understand your business rules.
It does not know the weird edge case your team fixed 8 months ago.
It does not know why that ugly conditional exists.
It does not know which “simple refactor” will break billing, renewals, permissions, or production data.

This is why the best developers are not becoming “prompt typists.”

They are becoming reviewers, architects, investigators, and decision-makers.

A METR study in 2025 found something surprising: experienced open-source developers working on real issues were actually 19% slower when using early-2025 AI tools.

Not because AI was useless.
But because real software work is messy.

You don’t just write code.
You understand the system.
You decide what not to change.
You protect the product from confident nonsense.

That’s the hidden skill.
AI can generate code.
But it cannot take responsibility for the consequences.
And that is where developers still matter.

In fact, the 2025 DORA report framed AI as an amplifier.
It amplifies strong engineering systems.
It also amplifies weak ones.

So if your team already has bad tests, unclear requirements, poor review culture, and messy architecture, AI won’t magically fix that.
It will help you create chaos faster.
The future developer will not be the person who writes the most code.

It will be the person who can:

Ask the right question
Understand the system deeply
Spot hallucinated logic
Design clean architecture
Review AI-generated code critically
Write tests that catch real business failures
Ship without blindly trusting the machine

That is the real shift.
Code generation is getting cheaper.
Engineering judgment is getting more valuable.
So no, I don’t think AI will replace developers.
But I do think developers who only copy, paste, and hope will have a very hard time.

The new skill is not “learning to code with AI.”
The new skill is learning how to think clearly when AI makes everything look easy.
Because the dangerous part of AI coding is not that it writes bad code.
The dangerous part is that it writes bad code confidently.
And that confidence can be expensive.

[Nikhil Nelson @SoloHacker47]

Everyone is asking:
“Will AI replace developers?”
I think that’s the wrong question.
The better question is:
“What part of being a developer was never actually about typing code?”

I’m Nikhil Nelson, a backend engineer with 5+ years of experience building Ruby on Rails apps, debugging production issues, working with databases, APIs, payments, background jobs, and lately experimenting with AI-powered products.

And the more I use AI for coding, the more I’m convinced of one thing:

AI is not replacing good developers.
It is replacing unverified output.
Here’s what the data is quietly showing.

Stack Overflow’s 2025 Developer Survey says 84% of developers are already using or planning to use AI tools in their development workflow.

So yes, AI coding is mainstream now.

But here’s the twist:
Developer trust is going down.
Stack Overflow later reported that only 29% of developers said they trust AI tools, even though adoption keeps rising.

That means developers are using AI more, but trusting it less.

That sounds contradictory.
But if you code for a living, it makes perfect sense.
AI is amazing at:
generating boilerplate
explaining unfamiliar code
writing first drafts
suggesting test cases
converting rough ideas into structure
helping you move faster when you already know the destination

But AI is still weak at something very important:

Context.

It does not fully understand your business rules.
It does not know the weird edge case your team fixed 8 months ago.
It does not know why that ugly conditional exists.
It does not know which “simple refactor” will break billing, renewals, permissions, or production data.

This is why the best developers are not becoming “prompt typists.”

They are becoming reviewers, architects, investigators, and decision-makers.

A METR study in 2025 found something surprising: experienced open-source developers working on real issues were actually 19% slower when using early-2025 AI tools.

Not because AI was useless.
But because real software work is messy.

You don’t just write code.
You understand the system.
You decide what not to change.
You protect the product from confident nonsense.

That’s the hidden skill.
AI can generate code.
But it cannot take responsibility for the consequences.
And that is where developers still matter.

In fact, the 2025 DORA report framed AI as an amplifier.
It amplifies strong engineering systems.
It also amplifies weak ones.

So if your team already has bad tests, unclear requirements, poor review culture, and messy architecture, AI won’t magically fix that.
It will help you create chaos faster.
The future developer will not be the person who writes the most code.

It will be the person who can:

Ask the right question
Understand the system deeply
Spot hallucinated logic
Design clean architecture
Review AI-generated code critically
Write tests that catch real business failures
Ship without blindly trusting the machine

That is the real shift.
Code generation is getting cheaper.
Engineering judgment is getting more valuable.
So no, I don’t think AI will replace developers.
But I do think developers who only copy, paste, and hope will have a very hard time.

The new skill is not “learning to code with AI.”
The new skill is learning how to think clearly when AI makes everything look easy.
Because the dangerous part of AI coding is not that it writes bad code.
The dangerous part is that it writes bad code confidently.
And that confidence can be expensive.

[Nikhil Nelson @SoloHacker47]

whats new in the AI world? Its been a while

[Nikhil Nelson @SoloHacker47]

@danmartell yes it is

[Nikhil Nelson @SoloHacker47]

@1Umairshaikh absolutely