Building With AI When You Don't Know Architecture: 5 Checks
Building with AI without architecture breaks around month six. Five checks you can run without reading code, what each answer means, and the cheaper path before a rewrite.
Victhor Araújo
Mainframe and AI: legacy is missing logs and owners, not age
CIO Dive reports AI agents helped sustain confidence in the mainframe. Three checks that tell you whether your system is legacy, and what to do about each one.
Victhor Araújo
Thousands of IF/THEN/ELSE rules: code, engine or spreadsheet
Rules that change weekly belong in versioned data with an owner. Rare rules stay as ifs. When a rules engine pays off, and what the finance spreadsheet really costs.
Victhor Araújo
Why can't IT deliver big projects on time like construction?
Construction slips too. Three contract devices explain the gap: a paid design phase, signed change orders with measurement, and one named engineer of record.
Victhor Araújo
The estimate that wins the deal is the one that slips the most
Every software quote that promises an exact date is selling, not estimating. I have lost deals for quoting the honest number and watched the cheap one arrive later and half-built. Why the lowest timeline is usually the one that slips most, and what to check before you sign.
Victhor Araújo
We audited 31 broken codebases. The same numbers keep coming back.
Every time Revin steps in to rescue a project, the first thing we do is read the code from the outside in. I pulled together what we found across 31 of those reviews over the last 18 months: test coverage, deploys, exposed secrets, who understands what. The sample is skewed on purpose, and that may be exactly why it's useful.
Raquel Reis
Pull request review time in remote teams: 2026 benchmark
Revin compiled PR review time from 100 remote squads in 2025. Market median: 14h. Top quartile (where Revin operates): < 4h. Long tail: 48h+. The difference is not talent — it is process. See benchmarks by team size and model.
Victhor Araújo
AI code review: where it replaces humans and where it does NOT
AI already does 80% of trivial code review. But there are 4 areas only senior humans catch — and ignoring that became an expensive mistake in 2026. Revin combines AI + senior across all clients. See where each wins.
Victhor Araújo
I changed one number in the URL and saw another customer's orders
A client asked me for a second opinion on the app another shop had shipped. Twenty minutes in, changing one number in the address bar, I was reading another company's order on his platform. Login worked; authorization didn't. On the cheapest hole to prevent and the most expensive to find late.
Victhor Araújo
Your last vendor is still logged into your production
Every time we take over a product that ran with another vendor, one finding repeats itself: production keys held by people who left months ago, secrets committed to the repo, a root account shared by five people. A field note on the access cleanup almost nobody does, and why skipping it gets expensive.
Victhor Araújo
Security isn't a feature you bolt on. It's how the team works.
There is one line in almost every software proposal I read: "we'll handle security later". That "later" has a date and a price, and it is rarely the person who promised it who pays. Why security is a team habit, not a backlog item, and how to spot it before you sign.
Raquel Reis
An untested backup is not a backup: the quarterly validation protocol
Most companies have backup configured. Almost none tested it in the last year. When the incident hits, they find out the backup was broken, incomplete, or impossible to restore. See the 4-step protocol senior squads run quarterly.
Victhor AraújoBuilding With AI When You Don't Know Architecture: 5 Checks
Building with AI without architecture breaks around month six. Five checks you can run without reading code, what each answer means, and the cheaper path before a rewrite.
Victhor AraújoThousands of IF/THEN/ELSE rules: code, engine or spreadsheet
Rules that change weekly belong in versioned data with an owner. Rare rules stay as ifs. When a rules engine pays off, and what the finance spreadsheet really costs.
Victhor AraújoWhy can't IT deliver big projects on time like construction?
Construction slips too. Three contract devices explain the gap: a paid design phase, signed change orders with measurement, and one named engineer of record.
Victhor Araújo
Technical debt you cannot see: measuring cognitive debt
The most expensive technical debt is the rule only one person can explain. A 40 minute test to find that concentration, and what to do once it shows up.
Victhor AraújoMainframe and AI: legacy is missing logs and owners, not age
CIO Dive reports AI agents helped sustain confidence in the mainframe. Three checks that tell you whether your system is legacy, and what to do about each one.
Victhor Araújo
PHP 5.6 to PHP 8 or full rewrite: how to decide
Upgrading PHP 5.6 to PHP 8 usually costs less than a rewrite. Three measurements (compatibility, dead dependencies, revenue flows without tests) tell you if your case is the
Victhor Araújo
AI teams ship more code and deliver less: what to measure
PR volume is up and the product hasn't moved. Four measurements that expose where AI turns into debt: review queue, 30-day rework, mutation score and real customer use.
Victhor Araújo
Inherited 200K lines of spaghetti code? The first two weeks
The first two weeks on an undocumented legacy codebase: boot it from scratch, instrument production, map the five revenue paths. And why the day-4 rewrite call backfires.
Victhor Araújo