Skip to content

Alex Carr

Data & Solutions Architecture from the field.

  • Home
  • Blog
  • About

Home

Hi, I’m Alex Carr — a data and solutions architect. I’ve spent my career in the gap between how technology is supposed to work and how it actually does. Here I share real experiences from the field, what I think, and what I’m still figuring out. Honest takes and respectful debate — feel free to join in.

  • Two contrasting scenes under the heading "The work will be prioritized either way. The question is how." On the left, a team calmly arranging priority cards into an agreed order on a board together. On the right, the same cards flying loose as individuals grab at them, surrounded by clocks, calendars and a shadowy figure.
    A Project List Is Not a Priority List
    When leadership doesn’t rank the work, it still gets ranked — by whoever pushes hardest. A project list is an inventory, not a prioritization.
  • Also worth noting: your three Post 3 images are already uploaded with alt text set — you're ahead of the checklist there.
    The Hidden Work Behind AI’s Fastest Deliveries
    AI can compress the build. It can’t do the requirements work that makes the build possible — and leaving that out of the update costs more than credit.
  • Architecture by altitude: four roles on an altitude scale — Director at 30,000 ft (vision & strategy), Manager and Enterprise Architect at 15,000 ft, Technical Architect at 10,000 ft, engineers at ground level.
    Architecture by Altitude: Who Should Be Doing What
    How deep in the weeds should each architecture role go? A field guide by altitude — Director, Manager, Enterprise Architect, and Technical Architect.

Proudly powered by WordPress | Theme: Smart Portfolio by Code Work Web.