For most of my career, chip design followed a familiar rhythm (beyond the short, exciting architectural exploration stage).
Simulate. Debug. Iterate. Repeat.
It's a rhythm every designer knows well. And for a long time, we accepted it as the cost of doing serious engineering. Complex systems demand rigor. Rigor demands repetition.
But somewhere along the way, something subtle happened.
We didn't just accept repetition — we normalized waste.
The Quiet Tax on Engineering Talent
Across teams and domains, I've watched exceptionally capable engineers spend a disproportionate amount of their energy on work that added little new insight:
- Coordination overhead (meetings, emails, spec chasing) - Rewriting boilerplate testbenches - Chasing spec changes - Tool setup and context switching - Post-layout rework due to poor instructions - Repetitive debugging for the same failures across corners - Porting the same design over and over across technologies without smart tools
...and the list goes on.
None of this work is intellectually hard. All of it is cognitively draining.
The tragedy isn't the time lost — it's the attention lost.
When engineers spend their days reacting, they lose the space to ask better questions.
---
Curiosity Was the First Casualty
Curiosity is what draws people to engineering in the first place. It's the instinct to ask why, what if, how far can this go.
But curiosity requires slack — mental room to explore beyond the immediate failure or deadline.
When workflows are dominated by repetitive tasks and constant coordination overhead, curiosity gets squeezed out. Engineers become efficient problem-solvers, but reluctant explorers.
And that's when design turns into grind.
---
Empathy Is Missing from Our Tools
Most EDA tools are brilliant at what they were built to do. They simulate, verify, optimize, and sign off.
What they don't do is understand how engineers actually work together.
Collaboration today often means:
- Spec drift across versions - Late discovery of conflicting assumptions - Surprises that surface only when schedules are tight
The cost isn't just delays — it's friction between teams.
Empathy, in an engineering context, means recognizing where energy is drained unnecessarily and designing systems that remove that burden.
We've rarely asked our tools to do that.
---
Imagination Is What Remains Untapped
When repetitive work dominates the day, imagination becomes a luxury.
Instead of asking:
- What if we re-architect this block? - What assumptions are we carrying forward unnecessarily? - What does the next generation actually need?
We ask:
- Why did this fail again? - Who changed the spec? - Did I miss an email?
The difference between incremental improvement and real architectural progress often comes down to whether engineers are given space to imagine alternatives.
A Shift Is Inevitable
As systems grow more complex, coordination itself becomes a first-order problem.
No amount of individual brilliance can compensate for workflows that fragment intent, duplicate effort, and bury insight in artifacts that no one revisits.
This isn't a tooling failure as much as a design philosophy gap.
If we want better chips, we need better ways to support the humans designing them.
That means restoring:
- Curiosity — by removing needless repetition - Empathy — by reducing coordination friction - Imagination — by freeing engineers to think architecturally again
AI changes what's possible here — not as a replacement for judgment, but as a way to offload the work that never should have consumed expert attention in the first place.
---
Looking Forward
I've spent the past several weeks exploring this frontier — informed by nearly 20 years building and reviewing complex silicon with world-class teams.
That exploration is now taking shape as AIDAChip: AI-native workflows for semiconductor design that restore curiosity, empathy, and imagination to the chip development process.
We're working with select analog/mixed-signal and digital design teams to validate this vision.
[!highlight] This isn't about replacing engineers — it's about amplifying them. - Handling the coordination overhead so teams can focus on creative problem-solving - Removing the grind so engineers can shift to architecting - Freeing attention so imagination becomes possible again
---
Join the Conversation
If you're interested in being part of this journey:
- Request early access for your team: aidachip.com/request-access - Follow our progress: linkedin.com/company/aidachip - Share your thoughts: What would you focus on if AI handled the repetitive parts of your work?
For those thinking deeply about what comes after "design and grind" — I'd love to hear from you.
--- Our Logo: Restoring What Was Lost
The AIDAChip logo shows something simple but powerful: AI agents and human engineers, hand in hand.
It represents our mission to restore what repetitive work has taken away:
Curiosity — When AI handles the grind, engineers have space to explore deeper questions.
Empathy — When coordination is automatic, teams collaborate instead of colliding.
Imagination — When attention is freed, engineers can architect the future instead of debugging the past.
The handshake in our logo isn't just symbolic—it's a promise. AI and humans, working together. Not one replacing the other, but both amplifying what the other does best.
That's the future we're building.
That's AIDAChip.