Learning to Build Software With Almost Nothing

I don't think I have a special talent for technology. I studied software development because I was placed in it, not because I chose it. What I did have was a stubborn habit of finding a way to keep learning when the easy route was closed.

If you are starting without much, this is what worked for me.

Start with what you have

In my first term of software development, I didn't own a computer. So I wrote code in my notebooks, and I drew my interface mockups by hand.

It sounds like a limitation, and it was, but it also forced me to think before I typed. When you can't run your code, you learn to read it carefully.

Borrow, and use every minute

Later I began borrowing laptops from friends who had them, for an hour or two at a time. I gave them back the moment I finished. Those short sessions taught me to arrive prepared, with a list of exactly what I wanted to try, because I might not get another chance that day.

I spent that time on W3Schools, especially its HowTo section, which is where I first learned JavaScript. By the third term, my parents had bought me a laptop of my own, and it changed everything.

Fundamentals before ambition

My first project idea was a YouTube-like video site. I had a friend with me and about five HTML tags between us. We didn't even know JavaScript existed. We asked older students how it would work, and they told us we needed a database, but nobody could tell us what kind, because that was taught the following year.

We gave up on the project, and I went back to basics. Looking back, that was the right choice. Solid basics carry you further than a big idea you can't build. I still remember the day I finally understood how border radius worked. I celebrated, because I used to struggle with it.

Prepare for being offline

Our holidays were about two and a half months, and I had no internet at home. Before the term ended, I downloaded a full Node.js and MongoDB tutorial series from a YouTube channel called The Net Ninja, because I knew I wouldn't be able to stream it.

During the break, I followed the tutorials and built my first real project from scratch. When I hit errors I couldn't solve, I sometimes walked to a school in my community just to use their internet long enough to find the answer.

If your connection is unreliable, plan your learning around it. Download before you leave, and save your questions until you have a connection.

Build one real thing

That holiday project was a simple school management system. When I showed it to my teachers, I was told I was the first student in my grade to ever bring a working project like that to the school. They gave me access to the computer lab.

That access mattered more than any single lesson. It meant I could practice whenever I wanted, on any machine, with the school's internet. One real project opened a door that good grades alone hadn't.

Spend on the right thing

Eventually I bought a course on Udemy, 100 Days of Python. Someone helped me buy it, and it taught me the Python I used later for backends and for the AI work that followed.

You don't need many courses. You need one good one that you actually finish, and a project to apply it to.

Then find your first real problem

Before my last year of high school, I built a complete website for a school, and it was my first paid project. It is still in use today. Nothing taught me more than making something that someone depended on.

What I would tell you

Talent is the wrong word. What I actually had was curiosity, a willingness to look silly while I learned, and the habit of turning every obstacle into a plan. Those are all things you can start today, with a notebook and nothing else.