Manifesto · Late 2025

The counter-voice
to AI slop.

Why I started ioprodz.

With the AI shift, almost everything about the industry feels like new ground. The entire market is debating model sizes, context windows, prompts — while the mainstream providers profit handsomely from the token-grinding companies building slop on top of their APIs. Almost nobody is talking about the boring engineering that decides whether an AI feature actually survives production.

After 15+ years shipping real software across IoT, telecom, real estate, and fintech, I'd seen this pattern before — different name, same mistake.

The moment it clicked

I watched a team I'd mentored years ago ship a polished, production-grade AI feature in under a month — because they already had TDD, CI/CD, and a clean domain model. A competitor down the street, with 3× the engineers, couldn't get theirs out of preview. Same tools. Same models. Different engineering maturity.

I started ioprodz in late 2025 to be the counter-voice: the one that says the boring engineering is the competitive advantage, and that a small team with the right practices outlasts a big team stacking tokens.

What I believe

Four convictions I'll defend in any room.

01

Shipping AI is an engineering problem disguised as a model problem.

The hardest parts — evals, rollback, observability, domain modeling, cost guardrails — are exactly what every AI tutorial skips. That's where engagements live and die.

02

The teams winning with AI already practiced TDD, DDD, XP, CI/CD before AI existed.

AI didn't make those practices obsolete. It made them a superpower. Mature engineering culture is the invisible moat that compounds exactly when everyone else is scrambling.

03

AI doesn't belong in your feature factory. It belongs in your factory factory.

Automate the internal work first — docs, demos, refactors, metrics, code review. That buys your team time to do the one thing AI can't: talk to the people who actually pay them.

04

By 2028, most B2B SaaS will be 90% autonomous.

Machines ingest feedback, ship aligned changes. The humans on those teams don't write features — they validate, govern, own outcomes, and spend their time with customers. Shortcuts taken now = locked out of that future.

Osmane Kalache
Who I am

Osmane Kalache.

Software engineer, 15+ years. Worked across IoT (home appliances), telecom, real estate, and fintech. Practitioner of DDD, TDD, XP, Conway's Law, fast feedback loops, CI/CD, platform engineering, and DX. Builder of SpecJest (open source) and Polysee — the lab where I stress-test the methodology. Serving Europe / North Africa.

DDD TDD XP CI/CD Conway's Law Fast feedback Platform engineering DX

Ready to leave
the vibes behind?

A tailored 30-minute screening. I'll tell you honestly whether your AI product has a vibe-coding problem or an engineering problem — and what the 90-day path looks like if you want to fix it.