When headline news reports massive profit spikes for energy conglomerates like Exxon and Chevron alongside quotes like "we're making a freaking fortune", it is easy to view the story strictly through a political or macroeconomic lens.
For everyday consumers, the reality hits directly at the gas pump and in monthly utility bills. But for software engineers, developers, and tech workers, this growing divide between legacy energy profits and consumer financial strain raises deeper questions about our industry:
How does energy volatility impact our compute infrastructure and cloud costs?
What role do our technical architecture choices play in global power consumption?
How can developers navigate career stability when cost of living rises faster than tech compensation?
1. The Cloud Is Built on the Grid
As developers, we are accustomed to abstracting physical infrastructure into simple software declarations and managed services. But beneath every virtual machine, serverless function, and cloud database lies a physical data center consuming real electricity.
When oil and natural gas prices surge globally, cloud providers—AWS, GCP, Azure, and regional data centers—face direct operational cost increases. Data centers require massive amounts of power not just to run processing units, but to cool them continuously.
While hyperscalers continue investing in renewables, much of the world's power grid remains tied to fossil fuel markets. When legacy energy companies post record windfalls during geopolitical or supply crunches, those underlying energy costs trickle down to every tier of the software stack:
Cloud bill inflation: API pricing, bandwidth, and managed database rates scale upward as hosting costs rise.
Cost-conscious engineering: Efficient code and resource optimization shift from optional best practices to critical financial imperatives for startups and enterprises alike.
2. Green Tech Stack vs. Legacy Extraction
The contrast between modern tech industry initiatives and legacy energy couldn't be starker:
Primary Driver:
Legacy Energy Dynamics: Commodity scarcity & price surges
Modern Tech Imperative: Efficiency, optimization & compute scale
Environmental Impact:
Legacy Energy Dynamics: Carbon extraction
Modern Tech Imperative: Minimizing carbon per API call or transaction
Economic Model:
Legacy Energy Dynamics: Record profits during consumer squeeze
Modern Tech Imperative: Open-source leverage & shared utility
As developers, our daily architectural choices directly influence real-world compute demands:
Algorithmic Efficiency: Prioritizing efficient data structures and algorithms isn't just about passing technical interviews—it reduces CPU cycles, power draw, and cloud costs.
Resource Management: Spinning down idle instances and leveraging auto-scaling ensures we aren't powering idle servers around the clock.
Green Hosting: Choosing data center regions powered primarily by nuclear, wind, or solar energy reduces the carbon footprint of our applications.
3. The Cost of Living Pressure on Developers
It is easy to assume tech workers are insulated from broader economic shocks, but cost-of-living increases affect every tier of the workforce:
Remote Work Realities: High electricity and heating bills mean home office overhead costs have climbed significantly for remote engineers.
Tech Hiring Shifts: While legacy commodities rake in windfalls, tech companies continue to optimize headcount, demand higher productivity, and scrutinize software budgets.
Side Projects & Startups: Bootstrapping a software product becomes harder when basic living expenses eat up disposable income.
4. What Can We Build About It?
As software engineers, we have a unique superpower: we write the software that optimizes real-world systems.
If you are looking for meaningful side projects or open-source contributions in this climate, consider:
Energy Efficiency Tooling: Contributing to CLI tools and libraries that measure local CPU energy consumption and process efficiency.
Open Source Energy Tracking: Supporting open-data platforms that monitor grid carbon intensity in real time.
Smart Home & Automation Systems: Building home automation integrations that optimize household energy usage during peak pricing hours.
Final Thoughts
The gap between record corporate windfalls and individual economic strain is a sobering reminder of how brittle traditional systems can be.
As developers, we may not control global energy markets, but we do control how efficiently we build, the infrastructure choices we make, and the problems we choose to solve. By prioritizing computational efficiency, pushing for clean-energy cloud providers, and building open tools that solve real-world problems, we can help build a tech ecosystem that works for everyone—not just the few making a "freaking fortune."
Sources
Fortune: Exxon and Chevron post massive profits as Trump brags about energy companies making a "freaking fortune" ahead of midterms (October 30, 2026).
Goldman Sachs & Industry Reports: Economic analyses on energy markets, inflation trends, and cost-of-living impacts on everyday consumers.
Top comments (1)
The strongest part of this piece is the reminder that “the cloud” is a physical system. It’s easy to forget that a serverless function is ultimately electricity and cooling, and that framing makes efficiency feel like an engineering responsibility rather than a nice-to-have.
I’d add a few nuances that might sharpen the argument:
Energy prices don’t map cleanly onto cloud bills. Hyperscalers typically lock in long-term power purchase agreements and run large renewable portfolios, so a spike in oil prices doesn’t flow straight into API pricing. Natural gas and regional electricity markets matter more for data centers than crude oil does, and energy is only one part of the cost structure alongside hardware, networking, and staff. The pass-through is real but slower and more diluted than the post suggests. It would be interesting to see actual pricing history set against energy costs.
The biggest efficiency levers are usually architectural, not algorithmic. Micro-optimizing data structures matters less for most teams than right-sizing instances, eliminating idle environments, tuning autoscaling, cutting cross-region traffic, and managing log and storage retention. Those changes tend to produce the largest savings in both cost and energy. For AI workloads, model choice, batching, caching, and routing smaller models to simple tasks can matter even more.
Green region selection has a catch. Choosing a low-carbon region is a good lever, but latency, data residency rules, and capacity limits constrain it. Carbon-aware scheduling, shifting flexible batch jobs to times or places with cleaner grid mix, is often more practical for non-latency-sensitive workloads. Tools like the Green Software Foundation’s Software Carbon Intensity spec and open datasets on grid carbon intensity give teams a way to measure rather than guess.
Measurement comes first. Many teams can’t say what a request or a pipeline costs in either dollars or carbon. Tagging resources, adding cost dashboards, and including cost and energy budgets in design reviews usually surfaces waste faster than any individual optimization.
On the cost-of-living section, I agree the pressure is real, though I’d keep it separate from the infrastructure argument, since the two stories have different causes and different fixes.
Your project ideas are good, and I’d love to see a small tool that surfaces estimated carbon per CI run or per deploy. Have you seen any teams put numbers like that into their pull request workflow?