These days, everyone talks about their tech stack.

It’s on Twitter bios, portfolio sites, pitch decks. Frontend stack. Backend stack. AI stack. No-code stack. Sometimes it feels like the tools matter more than the thinking behind them.

After nearly 10 years of working across web development and graphic design, I’ve learned something simple:
A tech stack is not a flex. It’s a reflection.

When you’re starting out, your stack is usually borrowed. You use what’s available, what’s popular, what tutorials exist for. That’s normal. I started there too; designing with Canva, building with WordPress, editing with Photoshop. Those tools helped me ship, learn structure, understand layout, and most importantly, finish things.

Over time, something changed.

I became less interested in tools and more interested in systems.
How things connect.
How data flows.
How a product survives years, not launches.

That’s when “stack” stopped meaning software and started meaning philosophy.

I believe in function-first design.
I value purity, doing more with less.
I like clean systems that are quiet, understandable, and durable.

Even though I work deeply in data, I don’t believe data tools should feel heavy or intimidating. Good system design should reduce noise, not add to it.

So when people ask about my tech stack today, this is what it looks like; not because it’s trendy, but because it fits how I think and how I build.

My Current Tech Stack

Backend

PHP (vanilla, custom MVC)

Python (data processing, scripts, automation, analysis)

MySQL / MariaDB

SQLite (for lightweight tools and MVPs)

Oracle SQL

Frontend

HTML, CSS, Vanilla JavaScript

Bootstrap

Custom utility-style CSS (Tailwind-inspired, not framework-heavy)

Systems & Data

SQL-first data modeling

Large text and CSV dataset ingestion

Custom search and indexing systems

Infrastructure

Linux (Ubuntu / Mint)

Shared hosting & VPS

Apache / Nginx

Design & Media

Canva, WordPress, Photoshop (still used when appropriate, not primary)

CapCut for video and documentary-style content

This stack didn’t appear overnight. It’s the result of years of building, breaking, simplifying, and choosing clarity over complexity.

Note to New Builders

If you’re early in your journey, don’t stress about your stack.

Use what helps you finish projects.
Use what helps you learn fundamentals.
Your stack will evolve as your thinking evolves.

In time, you’ll stop chasing tools and start designing systems.
And when that happens, your tech stack won’t be something you copy from others; it’ll be something that naturally fits you.

That’s when it really starts to matter.