2020 / FOUNDING
ActiveCodeGenTech
Founder and CEO of CodeGenerationTechnologies, connecting software engineering, architecture consulting, and independent products.
Company backgroundABOUT / THE PERSON BEHIND THE BLUEPRINT
A common thread of curiosity, discipline and craft.
I’ve spent much of my professional life understanding how complex software systems fit together, how they fail, and how they can better serve the people who depend on them.
01 / DISPOSITION & CONTINUITY
A common thread.
My work connects enterprise architecture, software engineering, technical leadership, and independent product development. I am interested in the relationships that make a system understandable and in the decisions that allow it to remain useful as conditions change.
I founded CodeGenerationTechnologies, known as CodeGenTech, in 2020. It provides a place to connect engineering and architecture with the practical work of creating software and exploring products.
Outside professional work, my curiosity continues through drawing, music and rhythm, movement, physical practice, and study. I approach these as practices to explore rather than subjects in which experience grants a final answer.
These interests share a foundation: curiosity, discipline, craftsmanship, and a willingness to revise an incomplete understanding.
2021–2024 / STUDY RECORD
Ongoing learningRichfield Graduate Institute of Technology
A period of formal study listed on my public LinkedIn profile. Experience does not eliminate the need to remain a student.
View LinkedIn02 / FIVE COMPLEMENTARY DIMENSIONS
One life, integrated across disciplines.
Engineering and art, intellectual and physical discipline, technological advancement and enduring principles are approached as expressions of a single disposition.
01 / PRIMARY
The Architect
“Before building a solution, understand the system.”
Structure, dependencies, constraints, resilience, and how individual decisions affect the whole.
02 / PRIMARY
The Creator
“An idea becomes meaningful when it takes form.”
Transforming abstract ideas—whether a sketch, rhythm, or software model—into tangible outcomes.
03 / FOUNDATIONAL
The Student
“Mastery begins by accepting how much remains to be understood.”
Ongoing observation, reading, formal study, experimentation, and revising previous assumptions.
04 / FOUNDATIONAL
The Practitioner
“Progress is created through practice, not performance.”
Repetition, patience, and correction across software craftsmanship, martial arts, music, and training.
05 / FOUNDATIONAL
The Steward
“The value of what we build is measured partly by what it makes possible for others.”
Responsibility, family, ethical consequences, and building foundations designed to endure.
03 / THE PRINCIPLES
Understanding, put into practice.
Select any principle to inspect how it connects to the wider blueprint.
01 / PRINCIPLE
Curiosity
Begin with observation. A useful question can expose a dependency that a confident answer has missed.
02 / PRINCIPLE
Understanding
Look for the principles beneath the visible problem. Context gives individual decisions their meaning.
03 / PRINCIPLE
Creation
Give an idea form. A model or prototype makes assumptions visible and invites correction.
04 / PRINCIPLE
Structure
Make relationships legible. Useful boundaries and clear interfaces allow a system to change without losing coherence.
05 / PRINCIPLE
Discipline
Return to the work with patience. Repetition matters when it includes observation and adjustment.
06 / PRINCIPLE
Wisdom
Ask whether a thing is worth building before asking how quickly it can be built.
07 / PRINCIPLE
Responsibility
Consider the people who depend on the result. Capability should be accompanied by care for its consequences.
08 / PRINCIPLE
Legacy
Think beyond the immediate release. Endurance, usefulness, and what a system makes possible for others also matter.
04 / DELIBERATE PRACTICE
Begin. Observe. Begin again.
Drawing, rhythm, movement, martial arts, physical practice, and technical work offer different ways to observe a process and refine it. I approach these as continuing practices rather than claims of mastery.
Pay attention before acting. The first task is to notice what is happening, including what the current model leaves out.
Draft narrative · EDITORIAL SPECIFICATION
On Building a Considered Life
A working statement of principles, open to refinement.
I believe that understanding matters.
That good questions often contribute more than immediate answers.
That meaningful creation requires more than inspiration. It requires discipline, patience, structure, and the willingness to begin again.
I believe that technology should serve people, that complexity should be understood before it is multiplied, and that responsibility should accompany capability.
I am drawn to the intersection of disciplines: engineering and art, reason and imagination, movement and stillness, knowledge and wisdom.
I value independence, but not isolation. Ambition, but not at the expense of integrity. Progress, but not merely for the sake of novelty.
I do not consider learning a stage of life to be completed.
And I do not believe that the things we build should be judged only by their immediate success.
Their endurance, their usefulness, and their consequences matter too.
There remains much to understand, much to practise, and much worth creating.