Concrete Performance Is Not Driven by Products Alone

What this is

This is a practitioner's notebook, not a brochure. I am not going to name products or tell you what to buy. I will explain how things work, what the specs are actually asking for, and what to consider when you are dealing with a particular problem. If you are an architect, an engineer, a contractor, a producer, or someone building out a data center and trying to understand the concrete side of it, this is written for you.

Start here

Four sections, each built around a real part of the work:

• Data Center Concrete - the construction boom in my backyard, and what it demands from the concrete under it.
• Sustainability, Decoded - EPDs, GWP, Buy Clean, and low-carbon mixes, translated from spec sheet to slab.
• Admixtures 101 - general-terms education on what admixtures do and when they matter. No brands, ever.
• Field Notes - problem-to-solution pieces from the road, on cracking, seasonal pours, and what crews are seeing.

What you will find here

Each section makes a specific promise, so you know where to go.

• Data Center Concrete gives you the concrete side of the boom that infrastructure analysts skip. What hyper-concentrated demand does to a market, what "screened on embodied carbon" means in a bid, and why a data-center slab is its own discipline. Start with the white paper, The Concrete Behind the Cloud.
• Sustainability, Decoded turns the regulation wave into plain English. What an EPD for concrete actually is, whether low-carbon concrete really costs more, how Buy Clean laws work, and how EPDs and LEED differ. If a spec sheet has you guessing, start here.
• Admixtures 101 is the syllabus, built on one rule: no brands. What admixtures actually do, by family. The downsides nobody selling them writes about. And water reducers versus superplasticizers in plain terms.
• Field Notes is the road-level stuff. When a crack is worth worrying about, what crews are seeing with Type IL cement, and the seasonal checklists for hot and cold weather pours.

Why listen to me

I have stood on both sides of the fence: the plant that makes the concrete and the jobsite that places it. Twenty-eight years of it, from the producing side through admixture technology.

My territory is the DC-Baltimore-Northern Virginia corridor, which by my own numbers is the densest data-center corridor on earth, roughly 13% of the world's data centers and 32% of North America's. That matters because the questions landing on me every week, embodied-carbon screening, GWP limits, the Type IL transition, the SCM squeeze, are the ones the rest of the industry is about to face. I am not forecasting the wave. I am standing in it.

And I am not doing this from an office. I drive about 60,000 miles a year, four to six days a week, six to ten hours a day, plant to jobsite and back. The content here is field-sourced by definition. When I say what a compressed data-center schedule looks like at the plant, or what a finishing crew is watching for on a repetitive pour, it is because I was recently standing next to it.

It is not about the follower count for me. I would rather be the person you call when you are stuck than the person with the biggest audience. So I read every message that comes in, and if I can point you in the right direction, I will.

The rules this blog follows

I want to be plain about the rules, because they are the reason this blog is worth reading.

No brands, ever. I never name, rank, endorse, or criticize a specific admixture brand or product, mine or anyone else's. I explain categories, mechanisms, and trade-offs, and I use one pattern: if you are dealing with a particular problem, consider a particular category of solution. Which brand and which mix is a conversation for you and your producer.

No speaking for any employer. The views here are my own. Nothing on this site is a statement on behalf of any employer, and there are no product endorsements. I keep that line bright on purpose.

Neutral by design. On the contested questions, the ones where the spec sheet and the jobsite disagree, I try to lay out what each side is actually seeing rather than pick a commercial winner. Because I have nothing to sell you here, I can afford to be the honest referee. That constraint is not a limitation on this blog. It is the whole point of it. Credibly neutral by design.

How I write here

I hedge before I land, because concrete rewards nuance. I explain the system before the fix, because the fix rarely works in isolation. Every piece ends with something you can use, a checklist, a question to ask your producer or engineer, or a next step, and never a sales pitch. If a piece does not leave you a little more able to handle your own problem, it does not go up.