Afnan Hussain

17/01/2026

Software development has changed a lot.
AI made coding feel too easy.

I still turn AI off once a week.
I do it to keep my brain sharp.

I build products and test ideas with AI.
But I code solo to train my core skills.

Why I code without AI:
→ I design logic by thinking hard.
→ I debug without hints.
→ I learn why code works.

↳ Result:
✓ My confidence grows.
✓ My fundamentals get sharper.
✕ My dependency stays small.

When I solve problems alone:
→ I remember patterns.
→ I spot edge cases.
→ I fix bugs faster later.

If you are new:
→ Code without AI to build basics.
→ Use AI later to speed up.

If you are senior:
→ Code without AI to stay sharp.
→ Use AI as a teammate, not a crutch.

AI should amplify skills, not replace them.
Keep the balance and own your craft.

Turn off tools to train your mind.
Keep AI as your helper, not your boss.

Code intentionally.
Practice deliberately.

P.S. Do you code without AI sometimes? (Yes/No)

10/01/2026

The database is the real product.
The UI is just a view.

You can redesign your UI in a sprint.
You’ll live with your schema for years.

UI bugs are annoying.
Data bugs are existential.

Think in tables, not pixels.

08/01/2026

07/01/2026

SQL dev → পরিষ্কার টেবিল, স্পষ্ট নিয়ম → দ্রুত ফিক্স।
NoSQL dev → অসংখ্য document ফরম্যাট → সময় লাগতে পারে।

04/01/2026

I rewrote my Next.js app in

03/01/2026

I shipped a Node.js app in 7 days.

(without Docker hell or CI gremlins)

I was the dev staring at logs at 2 AM.

You know the prayer:
Every junior node js developer praying is:
Ya Allah, I arranged 3,241 npm packages.
Please let none of them break in production.

I fixed that with three rules.

→ Keep deps tiny.
→ Audit weekly.
↳ Remove stuff you don't use.

→ Freeze versions.
→ Lock package-lock.
↳ No surprise upgrades.

→ Test fast.
→ Write one failing test first.
↳ Then make it pass.

✓ Deploy to a staging branch.
✓ Rollback plan ready.
✕ No blind pushes at midnight.

I learned to trust small changes.

Ship small. Ship safe. Ship often.

Your codebase will thank you later.

P.S. Did you lock your package versions today? (yes/no)

01/01/2026

I left PHP/WordPress after years on the stack.
Now I'm moving parts to Node.js.

1. You can't just walk away

A decade of PHP code still runs core logic.
Billing, auth, and integrations all depend on it.

2. The dependency surface is huge

☑︎ Business logic embedded in PHP
☑︎ Third‑party plugins and extensions
☑︎ Scheduled jobs and cron workflows
☑︎ Existing CI/CD and deployment scripts

3. Incremental migration works best

Replace services one by one.
Keep PHP for what’s stable.
Introduce Node for new features.

4. Real migration examples

- Move APIs to Node.js microservices
- Keep legacy admin panels in PHP
- Gradually port background workers
- Reuse databases and shared schemas

Migration checklist that helped me:

You map dependencies first.
Prioritise low‑risk services.
Create small APIs in Node.
Swap traffic gradually.
Monitor and rollback when needed.

This isn't about killing PHP.
It's about pragmatic evolution.

Save this for later. Repost for others.

12/04/2025

I think ChatGPT is the best AI for research 📚. It almost replies like a human 🤖💬 — and it even knows my zander! 😄✨

What is your opinion❓

10/04/2025

16 Oct 2021, 04:12