The industry wants you to specialize. They want you to be a React Dev
or a Python Dev.
We reject that. In the Garage, we are Generalists. We
build compilers on Monday and mobile apps on Friday. It's raw, it's
messy, and it's how you actually master Computer Science.
We don't have a rigid roadmap. We have a compass. We don't know exactly what we will build next month, and that is the point.
Below are the Archetypes, examples of the complexity we tackle. We might set out to build a Compiler and end up building a Database engine instead. We follow the curiosity of the Batch.
e.g., Building a C Compiler, a Database Engine, or a Memory Allocator. We strip away the libraries to see how the metal works.
e.g., Coding a Neural Net without PyTorch, or writing a Physics Engine. We tackle the algorithms that scare other developers.
e.g., Procedural generation, Sound synthesis, or 3D Shaders. We use code to make something that looks beautiful.
e.g., A real-time Chat Server, a Load Balancer, or P2P file sharing. We learn how computers talk to each other.
e.g., IoT drivers, Raspberry Pi controllers, or custom firmwares. We make code touch the real world.
Whatever the batch votes for. A crypto miner? A search engine? A retro game emulator? We build what excites us.
Monday morning. We release a "Brief." It’s not a tutorial. It’s a
requirements doc.
"Build a Redis clone that handles concurrent connections. No
external libraries allowed. You have 14 days."
You go dark. You read whitepapers, RFCs, and documentation.
This is the hardest part. You aren't copying code; you are
researching architecture. The struggle is where the
neuroplasticity happens.
You write code. It breaks. You fix it. It leaks memory. You
rewrite it.
You share your progress in the Discord. You realize everyone else
is struggling too. You keep building.
Submission day. We don't grade you. We review you.
We look at your variable naming, your concurrency model, and your
git commit messages. We give brutal, constructive feedback. Then
we merge.
You're scared you'll stare at a blank screen for 14 days and fail.
You think:
"I'm not smart enough to read this technical paper."
While you build, our mentors build too. And we record it.
No editing. No scripts. Raw footage.
You will see us get confused. You will see us Google basic
errors. You will see us open 20 tabs to understand one paragraph
of documentation.
This isn't a tutorial on "How to type code." It is a masterclass
on "How to figure sh*t out."
By watching a Senior Engineer struggle through the docs, you
unknowingly learn how to read them yourself. We demystify the
research process.
After the deadline, the "Raw Logs" and the Code Repos are
unlocked.
Because you tried (and maybe failed), and then watched us build
it, the concepts finally click. You go from "I'm lost" to "I'm
an Engineer."
We don't build products for clients here. We build projects for ourselves. The goal isn't a perfect portfolio; it's the scar tissue you get from debugging a race condition at 2 AM.
We deliberately pick projects that are "too hard." You will get stuck. You will break things. That isn't a bug; it's the curriculum. The learning happens when you are banging your head against the wall, not when you are copying a tutorial.
Everyone is a learner here. Whether you are a Junior Dev or a CTO, when we are building a Physics Engine from scratch, we all start at zero. Ask the "dumb" question. It's likely everyone else is thinking it too.
We do code reviews. We tear apart architecture decisions. Not to be mean, but to be better. Leave your ego at the door. Your code is not you. We support each other by being honest about the code.
When one person figures out why the memory allocator is leaking, they share it. The Garage is a multiplayer game. We struggle alone, but we succeed together.
You spend your days in Jira and your nights fixing minor bugs in a legacy codebase. You are tired of meetings. You miss the thrill of creation.
You know React and Python, but you feel like an imposter. You don't know how a computer actually works. You want to stop being a "Coder" and become an "Engineer."
"Do I have to use Rust? Can I use JavaScript?"
Use whatever tool solves the problem. We might suggest C for a
memory allocator and Go for a chat server.
But if you really want to write a Compiler in JavaScript?
Sure. We’ll just grab popcorn and watch the stack
overflow.
Every quarter, we pause the experiments to compete. Build something wild. Win hardware.
We only have one plan. You are either in, or you are out.
Equivalent to ₹1,500 / month.
Less than a gym membership.