What AI devalues — and what it makes more valuable
AI does not erase professions wholesale; it devalues ways of creating value. What apps, courses, and roles lose — and where data, integration, and accountability grow.
Stuzhuk Lab — Chemistry of Code
Chemistry of Code
← All posts
Tag
enterprise
All blog posts with this tag.
A compact CRNN does not get better because you hit train: the experiment loop
Third UT-pilot note: error diagnosis, one lever at a time, epochs, the dataset, and when the model should stop being squeezed for points.
Empty cells, dittos, and strike-through: OCR should not decide if a measurement exists
UT pilot sequel: five cell kinds, ink, ditto-up-the-column, strike-through, and why heuristics still do not replace a tiny classifier.
Risk-based inspection: why the calendar loses to a system loop
Field notes on RBI: asset portfolio, PoF×CoF, integrity modules, API RP docs, and academy — not a finished product guide.
Handwritten UT forms: why one model is not enough
Field notes from a pilot: computer vision, OCR, vision LLMs, confidence, and operator review before ERP — not a finished production guide.
Can AI Understand a Codebase With 15 Years of History?
Millions of lines, hundreds of tables, dozens of integrations: what AI grasps in hours, where it fails, how teams deploy RAG and repo indexing, and why expert + model beats either alone.
How to Design a Modern ERP System in 2026: From Monolith to Platform
Metadata Driven Architecture, platform engines, frontend stack, and migration strategy — how to build an ERP that evolves for decades without a rewrite every five years.
How to Design a System That Will Last 10 Years
Why systems die from early architectural decisions, not outdated tech — and how to design for change, not features: module boundaries, domain modeling, data, ADRs, and a decade-long checklist.
Why EAV Looks Like a Good Idea — Then Destroys ERP Performance
Entity–Attribute–Value looks perfect at the start: flexibility without migrations. Why JOINs, indexes, and reports break ERP years later — and where EAV fits, and where it does not.
The Most Expensive Mistake in ERP Architecture — Trying to Make the System Universal
Why the illusion of universality turns ERP into an EAV monster: lost performance, typing, and business meaning — and how to build around the domain, not abstract entities.
Why Most ERP Systems Turn Into Monolithic Monsters
The ERP success paradox: exceptions, technical debt, a single database, and the distributed monolith. Why the monster follows business growth and how to slow decay.