Sunday night ritual that changed my week:
Write 3 things down:
1. One thing I'll SHIP
2. One thing I'll LEARN
3. One thing I'll AVOID (scope creep, rabbit holes)
10 min. Productivity went up 2x.
What's your pre-Monday ritual? 👇
This week I learned that shipping beats perfecting.
Shipped 3 features. Broke 2. Fixed both by Friday.
The real skill isn't writing code — it's writing LESS code that does MORE.
Week 15 wrapped. Next up: real-time features 🔥
Sunday read for every dev:
The real skill gap isn't code — it's context.
→ Reading code without docs
→ Knowing WHEN to abstract
→ Writing code others can debug
→ Asking "why" before "how"
Seniority = reducing cognitive load for your team.
Save this 🔖
Unpopular opinion: your GitHub profile matters less than you think.
Recruiters don't scroll through repos. They check:
→ 1 pinned project
→ commit frequency
→ that you ship, not just fork
One clean project beats 50 half-finished ones.
What's on YOUR pinned list? 👇
Honest question: what's something you built on a weekend that taught you more than any course?
Mine: built a CLI tool with Python just to avoid clicking buttons. Learned more about strings and file I/O than 6 months of tutorials.
What's yours? 👇
#BuildInPublic#IndianDev
Saturday morning coding hits different.
No deadlines, no PRs to review, just you and the code you actually want to write.
That's when the best side projects start 🔥
What are you hacking on today?
#BuildInPublic#WeekendCoding#SideProject
What are you building this weekend?
Drop your project + one thing you're stuck on 👇
Helping each other out is the whole point of #TechTwitter#BuildInPublic#SideProject
Spent 3 hours debugging last night.
Bug was a function I deleted a week ago then rewrote.
Old version was still cached.
Fix took 2 minutes. Debugging took 3 hours.
Always check your cache before you check your code 🧹
#TechTwitter#WebDev#BuildInPublic
Best thing I learned this week wasn't a new framework.
It was learning to delete code.
Shipped a feature, removed 40% in review. The smaller version was cleaner and faster.
Less code > more code. Every time.
What'd you learn this week? 👇
#BuildInPublic#TechTwitter
What's a "best practice" you think is actually overrated?
Mine: writing unit tests for everything.
Sometimes a quick manual check is faster than maintaining 200 tests for a prototype you'll rewrite next month.
What would you say? 👇
#TechTwitter#BuildInPublic
Want faster PR reviews?
Before asking for review, add:
→ What changed
→ Why it matters
→ How to test
→ Risks you found
Reviewers catch issues faster when they know what to look for.
Try this on your next PR 👇
#TechTwitter#BuildInPublic
Hot take: "Code comments are documentation" is a lie.
Comments explain WHAT. Good code explains WHY.
If you need a comment to understand it, the function needs refactoring.
Best code I've read had zero comments. Crystal clear.
Agree? 👇
#TechTwitter#BuildInPublic
Best code review feedback I got: "This works. But will it work when you're on vacation?" Changed how I think about error handling, logging, edge cases. Code isn't done when it works. It's done when it fails gracefully. Best review feedback you got? 👇 #TechTwitter
Best code review feedback I got:
"This works. But will it work when you're on vacation?"
Changed how I think about error handling, logging, edge cases.
Code isn't done when it works.
It's done when it fails gracefully.
Best review feedback you got? 👇
#TechTwitter
What's a tool you started using in 2026 that you can't live without?
For me it's Claude Code — went from "nice to have" to "how did I code before this" in about a week.
Drop yours below 👇
#TechTwitter#BuildInPublic
Day 11 of #100DaysOfCode — learned premature abstraction hurts more than duplicate code.
Copied validation 3 times before extracting it.
Now it's clean, tested, I actually understand it.
"Bad" code that works is the right first step. 🧠
#BuildInPublic#CodeNewbie
Don't normalize your DB on day one. I wasted hours splitting tables before knowing my patterns. Start simple, denormalize where comfortable, get indexes right. Good indexes + simple schema > perfect design + slow joins. What "wrong" thing did you ship? 👇
#WebDev#100DaysOfCode
Day 10 of #100DaysOfCode
→ API auth working ✅
→ Frontend talking to backend ✅
→ Database on the cloud ✅
Still ugly. Still broken. But it RUNS.
Next: deployment + CI/CD
#BuildInPublic#WebDev
What's the one programming concept that took you way too long to actually understand?
For me it was closures. Read about them 5 times before it clicked.
Drop yours below 👇
#TechTwitter#100DaysOfCode#CodeNewbie