Sign in Subscribe

PowerShell Summit 2026: We Are All Insane, and That Is the Opportunity

To quote Jeffrey Snover, "you are all insane."

Not as an insult. As a diagnosis.

In the literal sense, our model of reality is incomplete. We make decisions based on what we think is possible, then new tools arrive and expose how wrong that assumption was.

That was the real theme I took from PowerShell + DevOps Global Summit 2026.

Snover framed it as a shift in the physics of innovation: from the deterministic certainty of Is computing to the probabilistic Ish nature of AI. Once you accept that shift, strategy changes. Planning changes. Leadership changes.

The Shift We Are Living Through

For years, many of us in the PowerShell space carried quiet assumptions:

  • "I can automate ops, but I cannot build real user experiences."
  • "I can script APIs, but full application workflows are for other kinds of developers."
  • "I can wire tools together, but not create polished systems end to end."

AI is breaking those assumptions in real time.

Now someone without a traditional web background can build a usable GUI. Someone who only wrote admin scripts can scaffold test suites, CI pipelines, modules, and release workflows much faster than before. Someone who avoided complex architecture can now iterate with an AI pair and actually ship.

This is not hype. It is capability expansion.

The important part is not just tool adoption. It is mindset adaptation.

What Summit Sessions Made Clear

Across the repo materials, the pattern repeats: PowerShell is expanding from "task automation" to "system creation."

  • Reusable tooling and module sessions showed that we can productize our automation, not just run it once.
  • Security and policy sessions reinforced that modern automation must be governed by design.
  • Infrastructure and compliance content demonstrated repeatable delivery patterns, not fragile deployment rituals.
  • Observability and resilience talks connected technical quality to long-term team sustainability.
  • AI-oriented and style-guide-driven workflows showed how humans and agents can collaborate with stronger feedback loops.
  • Hardware, home lab, and integration demos proved the platform can stretch from cloud governance to physical-world control.

Individually, each session was useful. Together, they tell a bigger story: the boundary around what a "PowerShell person" can build just moved.

The New Competitive Advantage

The industry will not reward comfort with old constraints. It will reward people who can adapt and innovate with the tools now available.

Snover called out where many leaders are stuck: prayer-based planning. That is what strategy looks like when we have not asked hard questions about control, leverage, and error in AI-enabled systems.

The differentiator is not "who knows the most commands."

The differentiator is:

  • Who can update their mental model fastest.
  • Who can combine domain expertise with AI-assisted execution.
  • Who can turn ideas into durable outcomes without waiting for perfect conditions.

In practice, this means building the muscle to experiment, validate, and ship.

Stop Prayer-Based Planning

If AI introduces probabilistic behavior, then pretending we can manage it with deterministic-era assumptions is operational theater.

Instead, teams need explicit answers to three questions:

  1. Control: Where must outcomes be deterministic, and where is probabilistic acceptable?
  2. Leverage: Where does AI create an order-of-magnitude gain for our team?
  3. Error: What failure modes are tolerable, detectable, and recoverable?

Without those answers, AI strategy becomes buzzwords. With those answers, it becomes execution.

Build a Plausible Theory of Success

Snover's point lands hard: stop half-assing strategy.

A Plausible Theory of Success for a PowerShell team should be concrete:

  1. Define the class of problems where AI-assisted PowerShell will be your force multiplier.
  2. Define non-negotiable guardrails for security, compliance, and quality.
  3. Define feedback loops that expose errors quickly.
  4. Define delivery patterns that can be repeated by the entire team, not one expert.
  5. Define how you'll measure improvement in throughput, quality, and resilience.

This is how you turn uncertainty into advantage.

A Practical Adaptation Playbook

If you want to act on this shift, start with a simple loop:

  1. Pick one thing you previously considered "out of scope" for your background (for example, a GUI for an internal tool).
  2. Use AI to scaffold the first version quickly.
  3. Add quality guardrails: linting, tests, code review, and security checks.
  4. Iterate in small cycles until it is usable.
  5. Capture the pattern so your team can repeat it.
  6. Document where AI output is trusted, reviewed, or rejected.
  7. Revisit the rules monthly as capability and risk both evolve.

This is how constraints dissolve. Not in one breakthrough, but in repeated proof that you can now do what you used to avoid.

Final Thought

If "we are all insane," then the good news is this: our old reality was the limiting factor, not our potential.

PowerShell Summit 2026 reflected a community learning to see differently. With AI in the loop, we can attempt work that used to feel off-limits, and we can do it with increasing speed and quality.

The world is changing from Is to Ish. The winners will be the builders and leaders who adapt their mindset, then operationalize that adaptation with a plausible theory of success.