Excellence is a word I have been thinking about quite a bit lately.
It first captured my attention during a recent bout of imposter syndrome. As a software architect, I went through a period when I felt that I did not live up to my own image of what the role should be. There were—and still are—so many technologies, patterns, languages, and practices I did not know. I felt an expectation to know everything, have an answer for every question, and make every decision correctly.
It became overwhelming. I found myself looking in the mirror and facing something of an identity crisis: Was I really cut out to be a software engineer? Even after doing this for more than a decade, did I actually have what it takes?
Excellence Is Not Perfection
As I wrestled with those questions, I happened upon the word excellence. It struck me that excellence was not really what I had been demanding of myself. What I had been pursuing was perfection.
There had to be a meaningful difference between those two ideas.
Definitions of excellence often focus on:
- The quality of excelling or possessing good qualities to a high degree.
- An outstanding quality—something in which a person or thing excels.
Definitions of perfection, by contrast, focus on:
- The state of being entirely without flaw or defect.
- The act of making something flawless or complete.
The distinction is subtle, but important: excellence means developing good qualities to a high degree; perfection means having no flaws at all.
The Impossible Standard
Once I internalized that difference, I began to understand why I had struggled so much. I was holding myself to an unattainable standard.
I believed I had to design and build the perfect systems, choose the perfect technologies, and understand them all perfectly. That is a lot of without flaw to expect from one person—and an impossible expectation given our limited time and capacity.
No wonder I felt like an impostor. Measured against flawless perfection, we are all impostors.
Excellence offers a healthier and more useful standard. It does not require us to know everything or get everything right. It asks us to care about the quality of our work, to learn from what we get wrong, and to keep improving.
That shift loosens the grip of imposter syndrome. We no longer need to prove that we are perfect. Instead, we can expect ourselves to learn, grow, and become a little better over time. Your rate of growth may be different from mine, but comparison is not the point. What matters is that we continue moving forward.
Excellence in Software Engineering
For me, applying this idea to software engineering means giving myself permission to try new things, build new products, write new blog posts, and put my creativity into the world without waiting until everything feels perfect.
The work does not need to be flawless before it can be valuable. It needs to be thoughtful, useful, and better informed than what came before it.
That does not mean lowering the bar or using imperfection as an excuse for careless work. I still believe deeply in craftsmanship, sound engineering practices, and building quality software that solves meaningful problems. The pursuit of excellence is demanding—but it makes room for experimentation, mistakes, feedback, and change.
Perfection tells us not to begin until failure is impossible. Excellence asks us to begin, learn, and improve.
A Continual Pursuit
As you follow along or interact with my work, know what I expect of myself: to keep learning, keep growing, and do a little better than I did before.
The things I build and share will not be perfect, and they do not need to be.
Some ideas will not connect. Some projects will contain bugs or lack important features. Some conclusions will change as I gain experience and encounter better information. When that happens, I will strive to listen, course-correct, learn, and make the work better.
That is why I created Exalynt—a name inspired by excellent. It is a place to explore, encourage, and support excellence in software engineering through continual improvement. It is where I can share what I am learning, build useful things, and contribute to a craft I genuinely enjoy.
Future posts will continue exploring this pursuit from two perspectives: my own journey of learning and growth, and the broader question of what it means to be an excellent software engineer. There is a lot contained in that question—craftsmanship, judgment, communication, architecture, leadership, curiosity, humility, and the responsibility to build software that genuinely serves people.
I do not expect to provide one definitive answer. Instead, I want to examine these ideas honestly, share what experience has taught me, and remain open to refining my thinking along the way.
This post is only an introduction. There are many directions the pursuit of excellence can take us, and I am excited to explore them. I hope you will join me on the journey.
