Learning to Think Like an Engineer

I didn't know what any of it meant at first — frontend, backend, database, API. I just knew I needed to understand enough to actually build something.

I didn't know what any of it meant at firs frontend, backend, database, API. Words I'd heard people use casually, the way you hear medical terms and nod along without really knowing what they describe. I just knew I needed to understand enough to actually build something, not just imagine it.

So I started from the beginning, the honest way watching videos meant for absolute beginners, reading explanations three times over because the first two didn't stick, closing tabs that assumed too much and finding ones that assumed nothing. It felt embarrassing some days, going back to basics at this stage of life, learning things a college student picks up in a semester.

What helped more than any single tutorial was just asking questions constantly, to anything that would answer AI tools, forums, whatever I could find at midnight when a human wasn't available to ask. Some questions were probably obvious to anyone with the background. I asked them anyway. I stopped caring how basic a question sounded somewhere around the third week, once I realized the alternative was staying stuck and pretending I understood.

Slowly, piece by piece, a shape started forming. Not expertise nowhere close but something like a map. Enough to know what a frontend actually does versus a backend, enough to have an opinion about how a platform should be structured before someone else built it for me, enough to ask better questions the next time I got stuck.

I think what I was really doing, without fully realizing it at the time, was trying to think like the kind of person who could build this piece by piece, borrowing understanding from wherever I could get it, until enough of it started to feel like mine.

I'm still learning. I'll probably always be learning this part. But I stopped needing to know everything before I let myself start.