Understand the system.
Before reducing a problem to one component or layer, understand enough of the surrounding system to know what actually matters.
About
From digital hardware and system architecture through firmware, software, graphics, imaging, and technical analysis.
The Engineer Behind the Practice
That probably explains why my career has taken me across the full digital design cycle, from digital hardware and system architecture through firmware and software. I’ve always been drawn to the problems that require understanding more than one layer of the system.
Over time, that work expanded into graphics, GPU systems, imaging, computer vision, simulation, and visualization. Although the technologies changed, the underlying kind of problem remained familiar: understand how the pieces interact, get specific about what the system is actually doing, and work through the boundaries between disciplines when necessary.
For much of the last decade, I have also applied that engineering background as a technical expert in intellectual-property litigation. That work has included patent, trade-secret, and copyright matters involving complex software and digital systems, including matters involving Fortune 100 companies.
Radiant Perspectives brings those parts of my work together: hands-on engineering and technical analysis grounded in the same underlying engineering perspective.
Career Arc
The technology has changed across my career, but the work has consistently involved understanding systems deeply enough to move between layers when the problem requires it.
ASIC and RTL design, digital systems, architecture, and the behavior of hardware below the software layer.
Working at the hardware/software boundary, where implementation details on both sides shape the behavior of the complete system.
C/C++, GPU and graphics systems, visualization, imaging, computer vision, simulation, and performance-sensitive software.
Applying engineering analysis to patent, trade-secret, and copyright disputes involving software and digital systems.
How I Work
Before reducing a problem to one component or layer, understand enough of the surrounding system to know what actually matters.
Move from broad descriptions to architecture, implementation, behavior, interfaces, and the technical evidence needed to answer the real question.
Some problems belong squarely within one discipline. Others require understanding how hardware, firmware, software, graphics, or imaging interact.
Explore the Practice