Discussion about this post

User's avatar
Kris McGar's avatar

I’ve heard many of your points before and I do understand where you’re coming from. I’ve used 3D printers extensively in building drones, so I’m very familiar with the process. And while the comment about 3D printing chips was amusing, it’s not really relevant to the conversation.

For the record, I never suggested we’re going to 3D print our way to mission accomplishment; actually it was a mere option, not the solution . Also, I’m not a scientist—just a retired infantry Marine. That said, no, an infantry platoon shouldn’t be hauling 3D printers on the objective. But an H&S company absolutely should be doing more than pushing all the burden onto the infantry.

The core of my original point is this: the status quo is not just outdated—it’s borderline dangerous in 2025. I’ve seen far too many senior leaders dismiss practical, potentially game-changing ideas simply because they read an article or heard someone’s take, without any hands-on experience themselves. Until we actually get reps and sets with the tech that already exists and start working through the problems with it, the “status quo” will continue to be the fallback—and that’s going to hurt junior warfighters far more than it ever will the decision-makers.

Thank you for the response.

What is your solution?

Expand full comment
the long warred's avatar

Agree. All points. Get your methods and procedures ready;

and with regret based on experience The Enemy Is The Change Agent. NO the system won’t change until the enemy convinces the survivors.

They don’t listen. Or learn.

WHEN the Change Agent creates that space to change;

Here’s my thoughts on winning the Rear Area Battle /LOCs.

Fight back to front by swarming locally, just as for example the Germans always counter attacked after setback, no orders needed. Win the LOC battle rear area to FLOT to restore logistics and security.

https://open.substack.com/pub/thelongnetwarred/p/rear-area-security-and-counter-reconnaissance?r=91o16&utm_medium=ios

Expand full comment
5 more comments...

No posts