AMIT
499 posts

AMIT
@itsAMIT00
Exploring networking & backend systems | Building. Breaking. Learning.
Kolkata 가입일 Temmuz 2024
141 팔로잉45 팔로워

I have reviewed 50+ backend projects this year.
The same 3 mistakes show up consistently.
They’re not obvious bugs.
They’re decisions that seem reasonable early on, but don’t hold up as the system grows.
1. Folder structure organized by layer, not by feature
/controllers , /services, /models works well in tutorials.
but in an actual codebase, it fragments related logic.
To understand a single feature like “billing,” I ended up moving across multiple folders.
But couldn’t find it without grepping.
It works at small scale.
But it becomes friction as the codebase grows.
2. One catch-all error handler returning 500
And suddenly everything becomes “Internal Server Error”.
This removes useful signal.
Bad input, missing data, and actual server failures all look the same from the outside.
Results in slower debugging, because you first have to identify what kind of failure you’re dealing with.
These should be treated differently:
400 → Invalid input
404 → resource not found
500 → system failure
3. Configuration read directly inside business logic
Calling os.getenv across the codebases feels convenient early on.
Over time, it introduces hidden dependencies.
Testing becomes harder.
Missing or incorrect values fail at runtime.
Configuration issues are harder to trace.
Loading and validating config once at startup avoids most of this.
None of these are advanced problems.
That’s exactly why they show up so often.
They don’t break the system immediately.
They make it harder to change, debug, and reason about over time.
Most production issues aren’t caused by complex logic.
They come from small decisions that don’t scale well.

English

@piyushgarg_dev There should be a startup for this, which provides the meta keys. I'm pretty sure they'll gain many customers in a short time 😁😁
English

@codersGyan Yeah this is true
Sir I want to know about one thing as a dev whenever I see someone's project get distracted, and a bunch of random thoughts starts coming in my head what a cool project, how they built this and so on rather than focusing on myself
Some advice
English

i built my own OAuth/OpenID Connect server from scratch.
try it: alok-auth.vercel.app
it handles the full Authorization Code flow with PKCE, consent, ID tokens, access tokens, refresh tokens.
see all features 🧵
thanks to @piyushgarg_dev for sparking the curiosity. ♥️

English

@Shivam_Goyal_20 @ChaiCodeHQ @Hiteshdotcom @nirudhuuu @yntpdotme @BlazeisCoding What does it do exactly, could you tell me some internal
English

Built my own cron manager 👉 cron.shivam-goyal.site
Lean, fast, and under my control ⚡
Theirs? Battle-tested infra at scale.
Different tools. Different goals.
What would YOU choose — control or reliability?
#buildinpublic #devtools #backend


English

I went on a date with a witch who lives in a swamp of cat pee in my dreams today. Now you will never forget this information. You will try hard to forget and distract but it only grows stronger. But I shall not allow your suffering for there is a cure. Date the witch in your dreams tonight and you shall forget. No further questions.
English

@IAmManware Oops I miss comma
I heard the news about the company not the news company
English

@itsAMIT00 Idk about the news company but a lot of companies are rolling into this
English

Hey guys, my company is pushing copilot down my throat for productivity. Guess I am a vibe coder from now. Pls don't be harsh on this beginner 🥹
Ps: wtf are these new copilot limits 😾🤮
Manware@IAmManware
Me watching vibe coders crash out all over X
English










