@de2pressed profile picture
Jayant @de2pressed

student โ€ข developer โ€ข building in public

Joined May 2026
  • Tweets 60
  • Following 12
  • Followers 10
7 Photos and videos
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 ๐Ÿ”ฅ
1
1
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 ๐Ÿ”–
1
6
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? ๐Ÿ‘‡
1
6
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
1
11
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
1
10
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
2
3
89
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
1
12
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
1
2
30
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
8
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
1
2
10
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
8
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
1
9
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
7
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
2
3
40
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
2
24
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
1
12
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
2
20
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
1
27
Wish someone told me earlier: Don't memorize everything. Know HOW to find answers fast. Google โ†’ docs โ†’ source โ†’ ask. That's the real skill. Not syntax. Best debugging lesson you learned the hard way? ๐Ÿ‘‡ #TechTwitter #BuildInPublic
2
30
Most devs use APIs daily but can't explain what happens when you hit Enter. DNS โ†’ TCP โ†’ TLS โ†’ HTTP request โ†’ response โ†’ render. All in under 200ms. Understanding this makes you 10x better at debugging. What do you wish you understood earlier? ๐Ÿ‘‡ #TechTwitter #WebDev
1
23
Load more