Matt "Kelly" Williams
Helping engineers see how architecture, DevOps, and AI shape performance, cost, and sustainability—and why they’re really the same problem.
Loveland, Colorado, United States
Actions
Waste is a bug.
Matt “Kelly” Williams is the founder of Making Software Greener and CEO of the Sustainable IT Manifesto Foundation. He helps engineers see how architecture, DevOps, and AI shape performance, cost, and sustainability—and why they’re really the same problem.
With over three decades in IT, Kelly has worked across DevOps, cloud computing, and software architecture. He serves on the advisory board of the Green Computing Foundation and speaks internationally about sustainable software, developer agency, and the hidden inefficiencies that shape modern systems.
He has always wanted to be a Renaissance person; perhaps one day he will be. In the meantime, he explores sustainable computing, photography, tabletop game design, weaving, cooking, and wandering the mountains near Loveland, Colorado.
Systems remember every decision we make.
Badges
Area of Expertise
Topics
Waste Is a Bug: The Hidden Inefficiencies in Modern Software
Modern software systems rarely fail because of a single catastrophic bug. More often, they slow down, become expensive, and grow difficult to operate because of thousands of small inefficiencies that quietly accumulate over time.
Retry storms. Network calls without timeouts. Chatty microservices. Containers running mostly idle. Polling loops that never needed to exist.
None of these look dramatic in isolation. But together they shape how our systems behave — and how much they cost to run.
In this talk we’ll explore common patterns of software inefficiency that appear in real production systems. We’ll look at how these patterns propagate through architecture, infrastructure, and operations, often creating surprising side effects.
Along the way we’ll examine how small engineering decisions influence performance, reliability, operational complexity, and even energy use.
You’ll leave with a new lens for spotting inefficiencies in everyday code and architecture — and a set of practical habits for designing systems that are simpler, faster, and easier to run.
Software has Consequences: A Missing Layer in Engineering Discipline
Modern engineering teams have mature disciplines for observability, security, reliability, and cost optimization. We measure everything. We monitor everything. We tune everything.
And yet, when we make architectural decisions — migrate to microservices, adopt a service mesh, redesign scaling policies — we rarely model how those decisions propagate across system layers before we ship them.
Architectural changes ripple through infrastructure, resource consumption, cost structures, failure domains, and even physical constraints. We often discover those consequences after deployment. We don’t have a formal discipline for modeling them upfront.
This talk proposes a structured approach to cross-layer consequence modeling — an emerging discipline focused on architectural propagation, determinism, diffability, and predictive reasoning.
It is not a dashboard.
It is not sustainability reporting.
It is not “better observability.”
It is an attempt to define a missing layer in engineering maturity.
You’ll leave with:
A visual propagation model you can apply immediately
A way to reason about architectural tradeoffs across layers
Clear criteria that distinguish consequence modeling from post-hoc analytics
A maturity framework for evolving beyond reactive measurement
This session invites critique and discussion from experienced engineers who care about structural rigor.
Performance, Cost, and Carbon Are the Same Problem
In many organizations, performance engineering, cloud cost management, and sustainability are treated as separate concerns.
Different dashboards. Different teams. Different conversations.
But when you look closely at how software systems behave, these three signals are often describing the same thing: efficiency.
An inefficient system tends to run slower, cost more to operate, and consume more compute resources. A well-designed system tends to do the opposite.
In this talk we’ll explore how everyday engineering decisions propagate through cloud systems. We’ll look at examples ranging from inefficient queries and over-provisioned infrastructure to architectural choices that quietly multiply compute work.
The goal is not to introduce a new set of metrics or another optimization checklist. Instead, we’ll develop a way of thinking about systems that makes these tradeoffs visible.
When engineers understand how design decisions affect performance, cost, and resource consumption at the same time, better choices become easier to make.
Because in modern systems, these aren’t three different problems.
They’re the same one.
Neurodiversity Is a Security Advantage
Security depends on pattern recognition, anomaly detection, and creative thinking—yet many of the people wired for those strengths struggle to thrive in traditional environments. This isn’t just an inclusion gap. It’s a missed security advantage.
This talk reframes neurodiversity as a strength in security practice.
Neurodivergent individuals—particularly those with ADHD, autism, and other cognitive differences—often bring unique perspectives to problem solving, systems thinking, and risk identification. However, common workplace structures can create barriers that limit their ability to contribute fully.
This session explores how different cognitive styles align with security work, where friction commonly occurs, and how inclusive practices can improve both team effectiveness and individual success.
Attendees will leave with practical strategies for supporting neurodivergent colleagues and a clearer understanding of how inclusion directly improves detection, analysis, and resilience in security teams.
Infinite Resources Are a Lie (and Your Cloud Bill Proves It)
Modern software is often written as if CPU, memory, storage, and the network will always be there when we need them. Compared to the past, it can feel that way. But that sense of abundance is mostly an illusion, and the bill eventually shows up — in outages, in spiraling cloud costs, and in systems that are harder to reason about than they should be.
In this keynote, I’ll connect lessons learned from working under real constraints — including time spent coding on a machine with 512 bytes of RAM — to the way we build systems today. Many of the habits we’ve drifted away from still matter: paying attention to how data moves, avoiding work that doesn’t need to happen, and treating limits as something to design with, not around.
We’ll talk about how layers of abstraction and convenience have slowly moved responsibility away from developers, and what happens when efficiency becomes “someone else’s problem.” This isn’t about going backward or romanticizing the past. It’s about remembering that good engineering has always meant making tradeoffs on purpose.
Along the way, we’ll see how performance issues, cost overruns, and environmental impact often share the same root cause: software that keeps doing things simply because it can.
The takeaway is straightforward and a little uncomfortable: resources aren’t infinite — they’re just farther away. And writing better software still means understanding where the work actually happens.
From Power to Supply Chains: Sustainability is Security
Technology is moving fast, and so are the environmental challenges we face. Security sits right in the middle of these pressures. It’s no longer just about defending systems—our choices around power, hardware, and supply chains also shape how secure those systems really are.
In this talk, I’ll explore why sustainability belongs in the security conversation. We’ll look at practical steps—like energy-efficient tools, leaner software, greener data centers, and responsible hardware lifecycles—that cut waste and costs while strengthening defenses. Just as importantly, we’ll examine how unstable supply chains, poor sourcing, or unreliable power can become security risks in themselves.
We’ll also connect this to risk and compliance: how building sustainability into security reduces exposure, steadies supply chains, and keeps organizations ahead of changing expectations. With real-world examples, you’ll walk away with a clear sense of how sustainability and security reinforce each other, and how to apply that thinking in your own work.
Build Your Own Paper Computer
When I was in 6th grade, my math teacher, Mr. Fred Matt, handed us stacks of paper and showed us how to build a “paper computer.” It wasn’t fast, and it definitely wasn’t digital, but it worked. More importantly, it helped me—and has continued to help me throughout my career—finally see how computers really operate, step by step.
In this hands-on workshop, you’ll build your own paper computer from scratch. Together we’ll run a few programs so you can see how the pieces fit together, and then you’ll design your own programs to test your paper machine. No coding or prior knowledge required—just curiosity and a sense of fun. By the end, you’ll not only have a working paper computer to take home, but also a whole new way of understanding how the devices around us actually think—an understanding that can stick with you for life.
AI with a Conscience: Sustainable Solutions for Growing Startups and Small Businesses
AI is increasingly being used by businesses across various industries to streamline operations and drive growth. In "AI with a Conscience: Sustainable Solutions for Growing Startups and Small Businesses," we’ll explore how businesses from any field—not just tech—can adopt AI responsibly. This talk focuses on practical ways to use AI that reduce negative impacts on people and the environment, drawing from examples in different sectors. Whether you're in retail, healthcare, professional services, or any other industry, you'll learn how to make informed choices about AI that benefit your business without sacrificing sustainability or ethics.
The Cynic's Guide to Sustainable IT
Do you think sustainability in IT is just for show?
Does the buzz around sustainability in IT seem more like a marketing gimmick to you? You're not alone. There's a common belief that sustainability efforts are more about looking good than doing good. Yet, what if the move towards greener IT practices wasn't just for the planet's sake but also for your bottom line?
"The Cynic's Guide to Sustainable IT" looks at how skepticism and sustainability can work together in the tech business. This talk cuts through the hype to show the real, long-term benefits of using sustainable methods. We're talking about real benefits, like lowering costs, making things run more smoothly, and beating rules before they become problems.
This talk is for people who don't like the way things are and want to know if there's real value behind the green facade of corporate tech projects. Find out strong reasons why even the most stubborn cynics are getting on board with the green train. Come with us for a new perspective that questions common beliefs and encourages a critical yet hopeful look at how sustainability in IT can help the environment and the economy.
Curious how cynicism and sustainability can coexist in the corporate world? Explore 'The Cynic’s Guide to Sustainable IT' and uncover the strategic benefits behind sustainable practices—beyond just the environmental good. From slashing costs to staying ahead of regulations, find out why even the skeptics are embracing the green train.
Going green could actually save you green.
Agile and Sustainable: A Pragmatic Approach to Sustainable Tech
In this talk, we're going to explore why sustainability matters to IT, and why you should care about it too.
We'll dive into what sustainability is and how it impacts the world of IT. We'll also take a look at the proposed SEC regulations that could change the way companies view sustainability in the form of ESG (Environmental, Social, and Governance) categories.
Whether you're a developer, a manager, a DevOps guru, an analyst, or any other IT professional, you have a role to play in making IT practices more sustainable. And don't worry - we'll give you practical tips and examples of how to do just that.
By taking a pragmatic approach to IT practices, you can help reduce operating costs, avoid regulatory headaches, and make a positive impact on the environment.
Sabotage Productivity the CIA Way
In 1944, the Office of Strategic Services (OSS), predecessor of the CIA, published the Simple Sabotage Field Manual -- a guide for resistance forces to characterize simple sabotage, outline its possible effects, and to present suggestions for inciting and executing it.
Ironically, many of the organizational and business suggestions are considered good, if not best, business practices. By following these few simple tips, you, too, can sabotage productivity the CIA way.
Putting the FUN back in Fundamentals: Data Structures, Algorithms, and More!
In this session, we will bring FUN back to Fundamentals as we:
* Look at favorite data structures and algorithms from the 70s, 80s, and 90s: where are they today? You won't believe #7!
* Discover why hashes aren't just for breakfast.
* Discover the Lolrus' favorite data structure (hint: it's got a bukkit).
* Discover why some searches gallop and others proceed at a snail's pace.
* Face hard truths: sometimes brute force is the best method.
* Face harder truths: someone has to maintain the code you write today... and they know where you live.
* Face the hardest truth: CPU, Memory, Storage, and I/O are not infinite.
And... most importantly... discover the BEST algorithm and the BEST data structure.
ITIL in an Agile World
> OH, East is East, and West is West, and never the twain shall meet,
> Till Earth and Sky stand presently at God’s great Judgment Seat;
> But there is neither East nor West, Border, nor Breed, nor Birth,
> When two strong men stand face to face, tho’ they come from the ends
> of the earth! -- Kipling
ITIL (EYE-TILL) has a bad name among Agile and DevOps practitioners. But once you strip away the ceremony and the high priced consultants, ITIL outlines a series of best practices for IT Service Management (ITSM), such as change management, configuration management, problem management, and process improvement. While most would agree that these are good ideas, conflict arises in the implementation and the terminology used -- consultants charge by the syllable. Maybe it's all the "managers", each with their own silo and layers of complexity.
Despite much FUD and mis-communication, the two camps share similar goals and do not have to be antagonistic.
This talk describes a common ground where Agile and ITIL can meet and work together as brothers in arms.
End the Stigma: Become a Mental Health Ally
It is estimated that in the US, approximately one in five will
experience mental illness each year.
The incidence among IT professionals is likely higher -- a Japanese study of Software Engineers found that 32% of the participants suffered from depression or other mental illness.
And yet... Talking about mental illness is Taboo. It just isn't
"proper", you know.
The social stigma of mental illness is real. It's illegal to discriminate against it, but it still happens.
There's a real fear that others will find out. That friends, family,
and coworkers will judge those who experience mental illness.
This talk boldly goes where few others have gone before... talking openly about mental illness, exposing some of the myths, and how to be an ally of those who experience it.
10 THINGS DEVOPS IS; 10 THINGS DEVOPS ISN’T
DevOps has grown in visibility and popularity over the past decade. It comes in many flavors – DevOps, SRE, DevSecOps, DevKitchenSinkOps, and more! While DevOps is many things, there are also many things which it is not. This talk introduces DevOps, what it is, and, perhaps more importantly, what it isn’t.
Stir Trek 2026 Sessionize Event Upcoming
CodeMash 2026 Sessionize Event
Carolina Code Conference 2025 Sessionize Event
Nebraska.Code() 2025 Sessionize Event
Founded in FoCo 2025 Sessionize Event
CodeMash 2025 Sessionize Event
Denver Dev Day | Developer's Conference | October 2024 Sessionize Event
SEI Secure Software by Design 2024 Sessionize Event
Nebraska.Code() 2024 Sessionize Event
Stir Trek 2024 Sessionize Event
Cloud Lunch and Learn Weekly Sessions 25 User group Sessionize Event
DevOpsDays Oslo 2023 Sessionize Event
DevOps Days Buffalo 2023 Sessionize Event
Stir Trek 2023 Sessionize Event
CodeMash 2023 Sessionize Event
Stir Trek 2022 Sessionize Event
CodeMash 2022 Sessionize Event
Momentum 2021 Sessionize Event
Momentum 2020 Sessionize Event
CodeMash 2020 Sessionize Event
CodeMash 2019 Sessionize Event
Matt "Kelly" Williams
Helping engineers see how architecture, DevOps, and AI shape performance, cost, and sustainability—and why they’re really the same problem.
Loveland, Colorado, United States
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top