Architecture Review Library · Corey Crooks
How the software
actually works.
Follow one action through a product I built, from the screen to the code that makes it work. Or explore how I would redesign the systems behind a local business.
- Verified vs. assumed, always labeled
- Whole-system reviews, not only UI
- Implementation tradeoffs
9.
Published reviews
5.
Industries
7.
Methodology stages
5.
Inside the build
Featured case studies
Deep reviews worth starting with
Most portfolios prove someone can ship an interface. This library documents the complete reasoning chain behind a digital system: business goals, UX, system boundaries, APIs, authentication, data, caching, observability, CI/CD, migration risk, and the tradeoffs behind each decision.
For a product I built, I follow a single user action through the implementation. For a business review, I start with its public website and explain what I would change, how I would migrate it, and what I would measure.
Audience
Engineering managers · Staff engineers · Principals · Architects · CTOs
Bias
The simplest architecture that satisfies the actual business need
Evidence
Verified observations, explicit assumptions, and recommendations kept separate
Methodology
How I review a business from the outside.
For independent business reviews, these seven stages connect what a customer sees today with the system I would recommend building.
Executive Summary
What the business does, who its users are, the major opportunity, and the recommended direction.
Current-State Review
Navigation, information architecture, brand hierarchy, accessibility, SEO, performance, conversion paths, and publicly observable behavior.
Redesign Rationale
Why the experience should change—user flows, hierarchy, responsive behavior, accessibility, content design, and measurable UX goals.
Architecture Review
Frontend, backend, APIs, authentication, authorization, data, caching, storage, jobs, integrations, observability, deployment, and system boundaries.
Engineering Decisions
Decision, context, alternatives, tradeoffs, consequences, operational impact, and business impact.
Migration Strategy
Phased delivery, sequencing, compatibility, rollback, risk controls, observability, and cutover approach.
Future Architecture
The target system, why it fits the business, how it scales, and which complexity is intentionally avoided.
The rule
No invented facts.
No proprietary code.
No copied assets.
Technology is recommended only when its value is justified.
Proof of thinking
A résumé summarizes experience. These reviews show the decisions.
Tradeoffs, migration reasoning, and evidence discipline—open any of these to evaluate how I work.
The library
Browse by industry or search
Find a product walkthrough or a business review by name, technology, or industry.
9 of 9 reviews

Homeward Guide Co.
Who gets the dining table?
Read review
Infall
Where does the light go?
Read review
Lightcourt
How Today remembers where a reply belongs
Read review
SnapDash
How a coffee mug becomes a point
Read review
SpireVault
Where does a relic’s win rate come from?
Read reviewBirmingham Bridge Tavern
A well-loved Pittsburgh tavern publishes its menu, specials, and events as freeform brochure text. The right system is a modular monolith with structured content and one reliable inquiry path, and an explicit refusal to build anything distributed.
Chris Driscoll Plumbing
A burst pipe and a bathroom remodel have different response expectations and different failure consequences. This plumber's site funnels both through one page and one form, and the lead pipeline behind it deserves to be the real project.
Revelation Plumbing
A trust-heavy Pittsburgh plumber publishes two different phone numbers across its public surfaces. That is a data-integrity failure, and fixing it takes ownership and monitoring, not a copy edit.
Shootin Bull Tavern
A well-rated Murrysville tavern has no website on its listing at all. The right first system is a nearly static site that answers where, when, and how to call, and the discipline not to build anything more until evidence demands it.
About & contact
Senior software engineer focused on architecture, modernization, and systems that remain operable after launch.
I work across application architecture, APIs, integrations, cloud systems, migration, and long-term maintainability. I care about clear system boundaries, justified technology choices, measurable outcomes, and delivery plans that respect business continuity. This library makes that thinking public.
Full bio & principlesTalk architecture
For engineering roles, architecture reviews, modernization work, and system-design conversations.
Opens your email client with a draft. No message is stored on this site until a form backend is configured.