Throughout my career, I have been fortunate to learn from many remarkable people. This dedication is for those whose contributions are often invisible, but whose work makes modern technology possible.
For Those Who Rarely Receive The Credit
This website is dedicated to the people who hold technology together from the inside — the infrastructure engineer who fixed a silent failure at 2 a.m., the architect who spent weeks thinking through a decision that most people will never notice was made, the operator who carried the system long after the project team had moved on, the security lead who made the company harder to harm, quietly and without applause.
These are the people behind the curtain. They rarely appear in the press release or the product launch. But the stability, the scale, and the long-term value that organisations depend on — it begins with them.
Good technology, done with care, is a quiet act of service. This is for the people who understand that.
The mentors
The senior architects, principal engineers, and quiet technical leaders who chose, often at some cost to their own time, to explain rather than to perform. The ones who told me when I was wrong without needing me to feel small about it. The ones who let me sit in on the conversations I was not yet senior enough to deserve, because they understood that exposure is most of how this craft is actually taught. I have tried to pass on what I learned from you, imperfectly, and I am still working at it.
The leaders
Technology leaders and programme directors who made room for honest architectural conversations even when the schedule did not particularly want them. The ones who treated "let me check one thing first" as a contribution rather than an obstruction. The ones who accepted the answer they did not want to hear because it was the right one. Good leadership is rarer than it sounds, and the difference it makes to the people around it is enormous.
The architects and engineers
Colleagues across more organisations than I can list — TCS, Conduent, HCL, Accenture, EY, and beyond — whose work I learned from by being in the same room, on the same call, in the same late-night incident bridge. The reviewers who pushed back when I was wrong. The implementers who took an ambitious design and made it actually work. The peers who shared the bits of context I would not otherwise have known. This site is, in a real sense, a synthesis of what I picked up from you.
The operators
The platform and operations teams who carry the work after the architects have moved on. The people on call when something fails at three in the morning. The people who write the runbooks nobody reads until the runbook is the only thing left between the system and a long outage. Much of what I now believe about calm architecture, I believe because I have seen what poor architecture costs the people who have to operate it. The respect I have for your craft is hard to overstate.
The support teams
Service desks, field engineers, and customer support professionals who absorb the friction that complex systems produce and translate it back into something the rest of the organisation can act on. Your work is often the first signal that something is wrong and the last line of defence when something has already gone wrong. Architecture that does not consider you is architecture that has not finished thinking.
The project and delivery teams
Project managers, business analysts, scrum masters, and delivery leads who held the work together through scope changes, resource changes, and the steady accumulation of small surprises that every real programme produces. The ones who translated my architectural concerns into something that fitted on a plan. The ones who told me, gently, when a decision needed to happen sooner than I had budgeted for. You make architecture deliverable, which is to say you make it real.
The wider technology community
The writers, conference speakers, open-source maintainers, and quiet bloggers whose work I have learned from over twenty years. The Stack Overflow answer at the right moment. The architecture decision record that explained something I had been struggling with. The long-form essay that gave me language for a pattern I had been observing but could not name. This site is an attempt to contribute back to that commons, in my own small way, with what I have learned along the road.
If any of the writing here is useful to you, it is largely because of the people above. Whatever is not useful, or wrong, is mine alone. Thank you, all of you.
— Subhakanta Kar, Bengaluru