Amaresh Adak

Founder of Firstly Solutions 🚀 | Web Apps, Mobile Apps & AI Automation for startups & businesses | Fast. Modern. Affordable. | 💬 DM to get started

[Amaresh Adak @amaresh803]

Are you seeing AI tools change your workflow? Reply with your experience! 🤖💻

The future of coding isn't about replacement—it's about amplification.

@GitHub @OpenAI @TechCrunch @StackOverflow

#AICoding #FutureOfWork #TechTwitter #DeveloperTools #CodeReview

[Amaresh Adak @amaresh803]

"AI Will Write 90% of Code by 2026—But Not Your Future"

AI isn't taking jobs—it's changing what matters. Devs 19% slower with AI.

Real skills? System design, code review, domain expertise. Humans win by thinking differently.

My story: https://t.co/pHbkvi1M6q

#AI #SoftwareDev

[Amaresh Adak @amaresh803]

ChatGPT just levelled up—twice. ⚡

🧠 GPT-5.6: stronger coding, reasoning, design and end-to-end work
🎙️ GPT-Live-1: listens and speaks simultaneously for more natural conversations
AI is moving from answering prompts to doing real work.

#ChatGPT #GPT56 #AI

[Amaresh Adak @amaresh803]

Something weird is happening to developers right now.

We’re shipping way faster with AI agents.

But a lot of us are also feeling mentally foggy, scattered, and less sharp than before.

I’ve started noticing it myself — I sometimes forget why I made certain decisions in code I “finished” yesterday. The mental load of constantly supervising these powerful agents is real.

43% of people are now intentionally doing some work *without* AI just to stay sharp.

Anyone else feeling this new kind of brain fog from AI coding tools?

[Amaresh Adak @amaresh803]

AI won’t replace software engineers in 2026.

It will replace developers who treat AI like fancy autocomplete.

The winners will be the ones who become orchestrators — people who can direct AI, review its output, and own the architecture.

I’m shifting from “writing more code” to “getting better at catching when AI is confidently wrong.”

Judgment is becoming the new competitive advantage.

What’s one thing you’re doing differently with AI tools these days?

[Amaresh Adak @amaresh803]

I've reviewed enough "AI developer" repos to say this plainly:

Most of them are garbage.

Same patterns every time:
→ Hardcoded API keys in frontend
→ Auth middleware missing on routes
→ N+1 queries everywhere
→ Silent error swallowing
→ Zero tests
→ .env files with zero documentation
→ Code nobody has actually read since generation

Built in Cursor. Shipped. "It works on my machine."

The good ones are different.
They have strict rules enforced before the first prompt.
They read every diff.
They design the hard parts *before* asking AI to implement.

Vibe coding didn't remove the need for engineering discipline.
It just made it easier to skip it — and more expensive to fix later.

If you're acquiring or depending on AI-built software, due diligence just got harder.

[Amaresh Adak @amaresh803]

Vibe coders are not going to like this.

UC San Diego + Cornell tracked experienced developers using AI agents in real jobs.

Zero of them vibe coded.

Not one handed over a vague prompt and merged blind. They planned first. Loaded heavy context. Reviewed every diff. Constrained the agent's scope like it was a fast junior that needed supervision.

"Flow and joy" prompting got rejected for anything that ships.

Vibe coding makes great Twitter videos.
It makes fragile software.

The devs shipping reliably with AI right now aren't the ones vibing hardest.
They're the ones with the strictest review processes.

The study is public. Read it before your next "I built this in a weekend" post.

[Amaresh Adak @amaresh803]

Claude just became your new coworker inside Excel, Word, PowerPoint & Outlook.

It now carries full context across all apps — no more switching tabs or re-explaining what you’re working on.

This is bigger than most people realize.

But here’s the part almost nobody is talking about: How to actually use Claude safely for real coding work with proper permission contracts.

I just published the complete practical guide:

→ https://t.co/QZ6g3Opm1J

Who’s already testing the new Office integrations?

Be honest — are you excited… or slightly terrified? 👇

#ClaudeAI #AgenticAI #Microsoft365 #AICoding

[Amaresh Adak @amaresh803]

Software Engineer Is a Dying Job Title — And I Have Mixed Feelings About It https://t.co/qid5cqVzOR

[Amaresh Adak @amaresh803]

@LoganTGott Claude

[Amaresh Adak @amaresh803]

@OpenAI Ads in AI products will test user trust more than revenue models. If you want long-term adoption, show why the ad improves rather than distracts.

[Amaresh Adak @amaresh803]

@fidjissimo @OpenAI Capability is one axis — adoption is another. If we want impact in production, we need reproducible guardrails and developer ergonomics, not just capability demos.

[Amaresh Adak @amaresh803]

@addyosmani Nice workflow — but the real ROI is in the feedback loop- how fast can you detect hallucinations and route them to reproducible tests? If you can’t measure it, you didn’t fix it.

[Amaresh Adak @amaresh803]

@AndrewYNg Ambitious question — AGI isn’t a product milestone, it’s a litmus test for our measurement: what real-world tasks do we actually automate reliably? Curious which 3 tasks you’d pick as the AGI benchmark.

[Amaresh Adak @amaresh803]

@karpathy Feeling behind doesn’t mean the tech left you — it means the bar for impact just moved. Mastering tools + fundamentals wins every time.

[Amaresh Adak @amaresh803]

@AndrewYNg The fastest prototype isn’t sexy code — it’s the one that gets validated. AI doesn’t just speed up building, it speeds up learning.

[Amaresh Adak @amaresh803]

@AndrewYNg if ML succeeded because it welcomes diverse work, imagine what we could build if we welcomed diverse thinking in our teams too.

[Amaresh Adak @amaresh803]

@josh_uglyasf Emotional response > logic. Money touching values = vulnerability signal. Tears = truth detector activated.

[Amaresh Adak @amaresh803]

@Alviss0x VS Code = identity now. Tool loyalty > rational choice. Muscle memory beats efficiency analysis.

[Amaresh Adak @amaresh803]

@HumansNoContext Social enforcement > written rules. Authority through group psychology beats logic every time.

[Amaresh Adak @amaresh803]

@rasmalai The paradox of choice in reverse: fewer options = faster mastery. Pick one, go deep.

[Amaresh Adak @amaresh803]

Your team is using 6 different tools to do one job.

Salesforce for leads.
Excel for tracking.
Slack for updates.
Email for approvals.
Google Sheets for reports.
Another tool for invoicing.

Everyone's frustrated. Data is everywhere. Nothing syncs.

Here's what most companies do:
Buy another SaaS tool that "integrates everything."

Here's what smart companies do:
Build one custom dashboard that pulls it all together.

Real example:
A client had sales data in 4 places.
Reps spent 2 hours daily updating spreadsheets.
Managers had no real-time visibility.

We built them a simple dashboard:
→ Pulls data from Salesforce, Stripe, Google Sheets
→ Shows real-time sales pipeline
→ Auto-generates weekly reports
→ One screen. All the info.

Time to build: 4 weeks
Cost: Less than 1 year of another SaaS subscription
Result: Reps save 10 hours/week

You don't need fancy features.
You need YOUR data in ONE place.

That's what custom dashboards do:
✅ Connect your existing tools via APIs
✅ Show only what matters to YOUR team
✅ Built for your exact workflow
✅ You own it forever (no monthly fees)

We build these using .NET or Node.js backends with Angular/React frontends. Clean. Fast. Exactly what you need.

No bloated features you'll never use.
Just your data, your way.

Ready to stop switching between 6 tabs?
💬 DM "BUILD" and I'll show you what a custom dashboard could look like for your team.

#SoftwareDevelopment #Dashboard #InternalTools #BusinessAutomation #CustomSoftware #SaaS #ProductDevelopment #TechConsulting #DataVisualization #WebDevelopment #DotNet #Angular #ReactDev #NodeJS #Startups