About little me

The useful part

I'm a beginner developer with my sights set on backend development and data modeling. Like a lot of people starting out, I didn't come in with a computer science degree or years of professional experience вЂ" just curiosity about how applications actually store, organize, and make sense of data behind the scenes. While frontend gets the visual credit, it's the data layer that quietly decides whether an application is fast, reliable, and able to grow.

How it works

• It sounds simple on paper вЂ" write some queries, design some tables вЂ" but in practice it meant rewiring how I think.
• A few things clicked for me along the way: A good schema is a form of communication.
• Iterating on a design after seeing how data actually flows through it taught me more than any tutorial did.
• Backend work has always felt like the "engine room" of software to me.
• Small differences вЂ" a missing JOIN condition, the wrong key, an unindexed column вЂ" can quietly break correctness or performance, so being deliberate matters.

What to take from it

Things like NOT NULL, UNIQUE, and foreign key constraints catch mistakes early instead...

Details worth keeping

Getting it "perfectly right" on the first try isn't the goal.