Home › About
28 Years In. Still on the Road. That Is the Point.
The short version
I'm Matt Knights. I have spent 28 years in concrete, starting on the producing side and moving into admixture technology, working the DC-Baltimore-Northern Virginia corridor. I drive roughly 60,000 miles a year between plants and jobsites. I write here, in my own name, to explain how concrete performs as a system, in plain terms, for the people who design it, spec it, and pour it.
How I got here
I did not start in a lab. I started on the producing side, where the concrete gets made, and over the years I moved toward the chemistry of it, the admixture technology that changes how a mix behaves. That path matters, because it means I have watched the same problem from both ends: the plant that has to make the concrete work, and the jobsite that has to place it before it sets. Twenty-eight years of standing in both places teaches you that almost nothing about concrete is a single-variable problem.
The territory
My corridor runs from Washington, DC, through Baltimore and into Northern Virginia. On paper it is a sales territory. In practice it is the densest data-center corridor on earth, holding roughly 13% of the world's data centers. That is not a small thing for concrete. It means the specs are getting stricter, the sustainability pressure is real, and the pours are large and fast. I spend 6 to 10 hours a day in my vehicle, four to six days a week, moving between plants and jobsites. The material for what I write does not come from a search bar. It comes from the windshield.
How I think about concrete
I think in systems, not products. Concrete performance is not driven by products alone. It is driven by how mix design, materials, production practices, quality control, and business objectives work together as a system. Change one piece and you move the others. So when I explain something here, I try to start with the system and only then get to the specific thing you are dealing with. It is a slower way to explain, but it is the honest one, and it is the one that actually holds up on a jobsite.
Why I write
Not for the status. I would rather be the person you call when you are stuck than the person with the most followers. My aim is narrower and, to me, more useful: to be a go-to voice in this niche, someone who can take a confusing spec or a cracking slab and explain it in a way that helps. I would rather publish one thing that is genuinely useful than ten that are just noise. This has been a long time coming, and I am building it to last.
The disclaimer, plainly
Everything on this site is mine. The views are my own. I do not endorse, rank, or criticize any product or brand, my employer's or anyone else's. Nothing here is a statement on behalf of any employer, and I do not name mine. This is general-terms education for the industry, written by one practitioner who wants to be useful. When a question touches something specific, I answer it as a category and a trade-off, never as a brand. That constraint is deliberate. It is what lets me be the honest referee instead of one more sales voice in the feed.
About Matt - Questions
What does Matt Knights do?
I work in concrete admixture technology, helping producers improve how their concrete performs. Before that I spent years on the producing side. Twenty-eight years in the industry, most of it in the DC-Baltimore-Northern Virginia corridor. I write here in my own name to explain how concrete works, in general terms, for the people who design, spec, and place it.
Why should I trust what you write?
Because it comes from the road, not a textbook. I drive about 60,000 miles a year between plants and jobsites in the densest data-center corridor on earth. The questions I write about are the ones I am actually dealing with that week. And because I take no product positions, I have no reason to sell you anything.
Do you represent your employer here?
No. Everything on this site is mine and mine alone. The views are my own, there are no product endorsements, and nothing here is a statement on behalf of any employer. It is general-terms education, nothing more.
Working through a mix, a spec, or a pour problem?
I spend most days between concrete plants and jobsites, and I read every message. If I don’t know the answer, I usually know who does. No pitch — ask away.
Ask me on LinkedIn or send a question here