If Dinosaurs Knew AI was Coming — LinkedIn
If dinosaurs had known The Meteorite was coming, they would have done something about it. We don’t have that excuse.
AI has reshaped how I think, build, and work as an engineer. Not because it replaced anything I do, but because it forced me to decide what I refuse to give up: agency, intent, and engineering judgment.
Recently, during an interview for a Senior .NET role, I was asked two questions that made me articulate that identity clearly. The answers weren’t interview answers — they were reflections of how I build systems and how I work with AI.
I’m sharing them here because they capture the core of who I am as an engineer.
1. What’s a system you’ve built, and what architectural decisions shaped it?
I’m the creator and sole developer of WORKS Commons, an AI‑native platform built on .NET 10, Blazor, EF Core, and LLM-driven signal processing.
But the technology stack isn’t the point. The point is the principle behind it:
AI contributes intelligence, but never intent. The system owns the workflow. The engineer owns the judgment.
Every architectural decision flows from that belief:
- MVVM so the UI can evolve without entangling logic.
- Layered architecture so business rules stay deterministic and auditable.
- Transaction Script + DbContextFactory so data boundaries are explicit and predictable.
- Producer–consumer pipelines so concurrency is controlled, not chaotic.
- LLM signal processing that transforms unstructured input into structured metadata — but never into decisions.
I call the overall pattern Agentic Workflow Architecture, not because the model is the agent, but because the workflow is. The model informs; the system decides.
That distinction is everything.
2. How has AI changed the way you work?
AI hasn’t made me faster by writing code for me. It has made me faster by sharpening how I think.
I use AI as:
- a reviewer that spots edge cases,
- a collaborator that challenges assumptions,
- a research assistant that accelerates learning,
- a documentation partner that enforces clarity.
- a pattern investigator that processes vast amount of data to find what is hidden from plain sight.
But I never outsource the design. I never let the model define the architecture. I never let it decide what “good” looks like.
If anything, AI has increased the importance of engineering judgment. It forces me to be more intentional, more precise, more accountable.
The real point
After answering those questions, I realized they capture the same identity from two angles.
In WORKS Commons, the model provides intelligence, but the workflow retains control. In my daily work, the model provides insight, but I retain responsibility.
This is the line I refuse to cross: AI can amplify me, but it cannot replace my intent.
Many conversations about AI focus on replacement. I don’t see it that way. Replacement is the meteorite. Complacency is extinction. Agency is survival.
AI has already changed software development. The real question is whether we will learn to use it with discipline, clarity, and ownership — or whether we’ll hand over the very thing that makes us engineers in the first place.
The dinosaurs never saw the meteorite coming. We do.

Comments
Post a Comment