Tanzim Hossain

Backend Engineer
Building scalable backend systems.
Open Source • System Design

[Phoenix.dev @0xphxdev]

Excited to share that I've been accepted as a contributor to @freeCodeCamp !

I'm grateful for the opportunity to write tutorials that help developers understand backend engineering, system design, and how frameworks work under the hood.

I'm looking forward to contributing articles on topics like TypeScript, NestJS, Spring Boot, distributed systems, and software architecture.

Thanks to the freeCodeCamp editorial team for the opportunity. Time to start writing.

#Backend #TypeScript #Java #SystemDesign #freeCodeCamp

[Tanzim Hossain @0xTanzim]

@0xphxdev Burn 🔥 money 💷

[Tanzim Hossain @0xTanzim]

@EOEboh Backend failed at the validation layer. If you're not explicitly checking email format, age range, and role permissions before the write, you're just a passthrough.

[Tanzim Hossain @0xTanzim]

@YashHustle_22 System design. It's the foundation everything else sits on. Master that, and picking up the rest gets easier.

[Tanzim Hossain @0xTanzim]

@theBuoyantMan The 10x cost difference is real, but the real win is that even with multiple passes it's still cheaper than one shot at GLM. Makes you rethink the pricing race.

[Tanzim Hossain @0xTanzim]

@cline This is the kind of test that actually matters. Half the cost for better quality? That's a real win, not a leaderboard number.

[Phoenix.dev @0xphxdev]

Most React apps don’t become messy because of React.

They become messy because nobody planned the architecture.

After working on growing codebases, here are 10 lessons I learned about production React architecture 🧵

[Phoenix.dev @0xphxdev]

I’m honestly amazed at the persistence of atheists

[Tanzim Hossain @0xTanzim]

@0xphxdev Not yet

[Dr Milan Milanović @milan_milanovic]

𝗬𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗵𝗮𝘃𝗲 𝗮𝗻 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺. 𝗬𝗼𝘂 𝗵𝗮𝘃𝗲 𝗮 𝘀𝘁𝗮𝗴𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺.

What I've seen in my career is that most teams pick architecture based on hype, not real needs. They see how Netflix runs microservices and assume that's the answer. A 5-person startup running microservices isn't engineering. It's cosplaying.

Here's what you need to know about each one:

𝗠𝗼𝗻𝗼𝗹𝗶𝘁𝗵 → You're still figuring out what to build. A monolith lets you move fast, refactor easily, and deploy one thing. Start here, especially if you're a startup. And make it modular.

𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 → Multiple teams stepping on each other. Deployments take hours. One bad change breaks everything. That's when you split, and only along real team boundaries. If you can't afford a platform team, you can't afford microservices.

𝗦𝗲𝗿𝘃𝗲𝗿𝗹𝗲𝘀𝘀 → You want to stop managing infrastructure for workloads that don't need it. Works well until vendor lock-in creeps in. By the time you notice, migration costs are enormous.

A well-structured (modular) monolith beats poorly designed microservices every time.

You can mix them too. Monolith core with serverless for specific workloads is often the right call.

Stop choosing architecture for where you want to be. Choose it for where you are.

[Tanzim Hossain @0xTanzim]

@Umesh__digital AWS 😑

[Tanzim Hossain @0xTanzim]

@javarevisited @grok which one?

[Tanzim Hossain @0xTanzim]

@tapasadhikary I think he is a genius but wastes his time, manually writing code when he can save time and spend time on architectural decisions.

[Tanzim Hossain @0xTanzim]

@tapasadhikary A & B both

[Tanzim Hossain @0xTanzim]

@cryptorover @grok that is the reason for war?

[Tanzim Hossain @0xTanzim]

@GlobeEyeNews Terrorist Trump who is bombing at girls' schools

[GitHub @github]

Copilot is powerful—but it gets dramatically better when you give it the right context.

Here are 4 practical context-engineering techniques to improve Copilot’s accuracy 🧵👇

[Tanzim Hossain @0xTanzim]

@tapasadhikary 😢 😢 I HAVE THIS BAD HABIT

[Tanzim Hossain @0xTanzim]

@tapasadhikary https://t.co/ePJSVWKbP2

[Dmitrii Kovanikov @ChShersh]

People ask me how to learn C++

My advice: learn Assembly first.