We Teach You To Build Your Own Work
The aim here is independence: that you can take a real problem, build something that solves it, and hand it over working. Do that and you can take on clients, start something of your own, and in time employ someone yourself — instead of waiting for a company to decide you are ready.
The software India runs should be written in India
Look at what a shop, a clinic, a school or a small factory around Punjab actually runs on. Almost all of it was written somewhere else, by people who have never been here and do not know how the work is done. These businesses need software built for how they really operate, and they cannot afford to have it made abroad.
That is a gap, and it is a gap that the person sitting in our classroom is in a better position to close than anyone in California. They know the market. They know what a kiryana owner will and will not use. What they are usually missing is the ability to build it — and that part can be taught.
So we teach people to make things, not to apply for things. If the next generation of software for Indian businesses is going to be written here, it will be written by people who learned to build rather than people who learned to interview.
What you should be able to do
Not a list of technologies — a list of things you can do with them.
Take a problem from a conversation to a working thing
Someone describes what their shop or clinic needs. You work out what it really means, decide what to build, build it, and hand it over running. That whole loop, not just the middle of it.
Work for yourself if you want to
A person who can deliver does not need permission to start. Freelance work, a local client, a product of your own — these stop being other people's stories once you can actually build the thing.
Be the one who hires, eventually
The people who employ developers were mostly developers first. If that is where you are heading, the skill you need is building and shipping, not clearing interviews.
Still be useful in ten years
Frameworks come and go. Knowing how to break a problem down, read someone else's code and get a thing into production does not expire when the tools change.
How we work
You write the code, every session
Not slides, not dictation, not copying a finished project off the board. You get a machine and you build, and it breaks, and you work out why. That is the part that transfers.
Real problems, not exercises
The work we set comes from things businesses around here actually need — a booking system, a stock register, a device that reports a reading. Toy problems teach you to solve toy problems.
We teach what we run ourselves
The mentors here build and ship real software, and the tools in class are the ones they use for it. When something in the syllabus stops being what the industry uses, it comes out of the syllabus.
Learn in any order, for one fee
One monthly rate covers the whole catalogue, so nobody picks a subject by what they can afford. Start with Python, move to data, add IoT — it is the same fee the whole way.
What we aim at
Same subjects as anywhere else. Different thing being aimed at.
A placement-focused course
Here
Neither aim is wrong. They are just different, and it is worth knowing which one you are buying.
Straight answers
The questions worth putting to any institute, including this one — and our answers, including where the answer does not flatter us.
No. There is no placement cell, no hiring partners and no drives, and we will not promise you a job. We would rather be useful than sound reassuring. If a placement letter is the main thing you are buying, an institute with a published placement record is a better fit, and we will say so on the day.
Plenty of people will, and being able to build things is what makes that likely — someone who can ship is useful from the first week. What we are saying is that we do not arrange it, and we do not want you choosing us because of a promise we are not in a position to keep.
Come to a demo class and ask the students directly — they will show you what is on their machines. We would rather you saw work in progress and asked the person who wrote it than looked at a gallery we curated.
Ask on the day and meet them. The person taking your class should be someone who writes code outside of class, and you should be able to tell within ten minutes whether they do.
Every session. If you sit through a class here without typing anything, something has gone wrong and you should say so.
You should not, on the strength of a website. We have a small number of reviews and no long record, and pretending otherwise would be the first bad sign. What we can offer instead is that the first class is free, you pay by the month, and you can stop at the end of any month — so the cost of finding out we are wrong for you is one month.
Yes, and it states the months you actually completed. It is an accurate record. The thing that will get you work is the software you can show and explain.
Come and see whether any of this is true
Sit a class. Write some code on one of our machines. Talk to the students without us in the room. It is free, and it is a better test than anything written on a page.