notvibescoded

About

One engineer. Zero vibes.

notvibescoded is a dev studio run by Hamza — Full Stack Engineer, Python/Django and React/Next.js, with production AI/LLM experience and a low tolerance for slop.

notvibescoded stacked logo

Hamza

Full Stack Engineer

Python · Django · React/Next.js · AI/LLM · PostgreSQL · AWS · Docker

I'm Hamza, a Full Stack Engineer with two years of professional experience building Python backends and AI/LLM integrations that run in production — plus a computer science degree with top grades in AI, machine learning, and algorithms.

I started notvibescoded because of a pattern I kept seeing: founders paying for software that demoed beautifully and collapsed on contact with users. Forty-thousand-line monoliths. Secrets in client bundles. Databases with no locks. All of it generated in a weekend, all of it somebody's expensive lesson.

The studio's position is simple: AI is a magnificent bricklayer and a terrible architect. I use it where it's strong — speed on well-defined work — and I do the architectural thinking myself: what the system should be, what can go wrong, and what "done" actually means.

The blog is the other half of the studio. Rankings, teardowns, and craft notes — public proof of how I think about software, published twice a week whether or not it wins clients. (It wins clients.)

Principles

How we work, in four lines.

01Architecture before code

Every project starts with decisions in writing: data model, system boundaries, failure modes. Code is the easy part once the thinking is done.

02AI as tool, not author

We use AI the way a carpenter uses a power saw — for speed on well-defined cuts. The design, the judgment calls, and the responsibility stay human.

03Done means maintainable

Tests, review, documentation, rollback plans. If the next developer can't take it over, it isn't finished — no matter how good the demo looked.

04Honest about fit

If AI is the wrong tool for your problem, we'll tell you. If your idea needs a smaller scope, we'll say so. We'd rather lose a project than build the wrong thing.

Have something that needs building properly?

No prompts-to-production pipelines. Just engineering: architecture, tests, review, and code you can actually maintain.

Start a project