Here's a product feature which the world is going to need a whole lot more of over the coming months and years: default hard budget caps. I'm talking about the feature of pay-by-usage services and APIs that lets you say "after $X/month, cut this thing off and return errors". These need to be hard limits. Soft caps, "after $X/month, send me a warning email", will not cut it.

Coding agents, and personal agents (coding agents wrapped in a less threatening UI), greatly reduce the friction of spinning up code that can do useful things. Sometimes those things cost money - calls to paid APIs, or hosted web applications, or systems that can bill for additional storage and compute.

Nobody wants to wake up to an email sent at midnight warning about a budget limit and find that, while they slept, their rogue service had consumed several hundred (or several thousand) more dollars of usage.

An argument against this is that businesses don't want their hosted applications to start throwing errors because some budget was exceeded. I expect that most businesses and individuals would prefer errors to a surprise $10,000+ bill.

I think hard budget caps need to be the default. If someone wants to live dangerously they should be able to do that, but it needs to be on an opt-in basis. Have a nice, clear checkbox somewhere prominent:

Remove the budget cap. My application will not be shut down if I exceed the configured budget limit, and I will be responsible for subsequent charges.

The service I most want to see this from is AWS. I've heard plenty of stories from people who refuse to use AWS for personal projects out of (justified) fear that a runaway service might bankrupt them. I've also heard stories from people who didn't anticipate this and ended up seriously burned.

... and it turns out AWS finally launched spending limits a few weeks ago! From their announcement New AWS experience helps builders get started and ship faster on 16th September:

When you're ready to upgrade to a paid plan, you can set a monthly spend limit for your project based on your usage patterns so that you stay within your budget. If a project's usage reaches its spend limit, your project is paused for that month.

See also Create a spend limit in AWS Settings, though that page warns that "We're currently releasing our new experience to a limited number of customers." Here's hoping that hits general availability for existing accounts soon.

Google Cloud launched a similar feature in July, called Spend Caps, which lets you "set a monthly financial cap on specific services within a project". Looks like this is becoming a trend!

In an ideal world, our agents could help with this. It would be great if agents started biasing towards recommending providers with hard budget caps, and warning new and inexperienced builders against deploying applications using uncapped services that might get them into trouble.

Tags: amazon-web-services, ai, coding-agents

An estimated 2.3 million cancer cases worldwide in 2024, about one in eight, were attributable to infections, according to a study published in The Lancet Oncology. "This recent Lancet data is a profound reminder that a significant portion of our global cancer burden is fundamentally preventable," said David Greenberg, MD, of Hackensack Meridian Jersey Shore University Medical Center, in a news release. "We have historically siloed infectious diseases and oncology, but they are deeply intertwined. By shifting our focus toward aggressive infection control, we can literally vaccinate and treat our way out of millions of future cancer diagnoses." From a report: The study found that an estimated 2.3 million new cancer cases were attributable to infections globally in 2024, equivalent to 12% of all cancer cases. Of these, the largest number (760,000 cases, or 4%) were caused by H. pylori, followed by HPV (750,000 cases, or 4%), HBV (360,000 cases, or 2%), EBV (260,000 cases, or 1%) and HCV (160,000 cases). More than three quarters of infection-attributable cancers occurred in low- and middle-income countries. Eastern Asian had the largest burden, with 990,000 cases (42% of the global total). Rates were also higher than the global average in sub-Saharan Africa, Central and Eastern Europe and Southeast Asia.

Read more of this story at Slashdot.

This beta update fixes several bugs reported in the previous build, and fixes compatibility for some effect plugins.

Changes since 5.2 Beta (build 9762):

• Fixed tooltips not displaying for the History and Layers windows
• Fixed compatibility for the Content Aware Fill effect plugin
• Fixed a bug that was causing the Dynamic Draw effect plugin’s output to have its alpha channel reset to opaque
• The mouse wheel can now be used to scroll menus other than Effects and Adjustments when they can’t completely fit onto the screen
• Optimized the performance of the canvas when at zoom levels >100% to use less memory bandwidth. This should reduce power usage on laptops.
• Wine: Improved text rendering quality and stability by using DWriteCore
• Wine: UI animations now work

Download and Install

This build is available via the built-in updater as long as you have opted-in to pre-release updates. From within Settings -> Updates, enable “Also check for pre-release (beta) versions of paint.net” and then click on the Check Now button. You can also use the links below to download an offline installer or portable ZIP.

You can also download the installer here (for any supported CPU and OS), which is also where you can find downloads for offline installers, portable ZIPs, and deployable MSIs.

For the experimental builds for Wine, you can go here to download them.

​

---

BONUS: Why AI Needs More Than Silicon Valley Moonshots With Salima Bhimani

AI is changing the work of software teams, but Salima Bhimani argues that the bigger question is not only what AI can automate. In this BONUS episode, Salima shares what she learned inside Alphabet's moonshot ecosystem, why breakthrough ideas may be hiding in plain sight, and how more people can become moonshot makers when technology meets lived intelligence.

Invention Starts in Real-World Constraints

"Invention is something that is always happening in relationship to something that's in the world."

 

Salima traces her view of invention back to a family history of migration, adaptation, and rebuilding under constraints. Her roots go from India to East Africa, where her family had to learn new languages, new land, and new ways to survive. That experience shaped a practical view of innovation: invention is not only the work of a lone genius in a lab. It often starts in friction, necessity, and the daily encounter between people and the systems around them.

We May Be Thinking Too Small About Innovation

"We've actually shrunk our ability to see what's out there in the world by limiting who's in the room."

 

Salima respects what Silicon Valley has built, from search to self-driving technology to AI. But her challenge is that the dominant innovation model often starts with a small group defining the problem, building a product, and then deploying it into the world. That can miss the collective intelligence already present in the places where the problems live. For software leaders and agile practitioners, the question becomes sharper: what would change if discovery started earlier, closer to the real ecosystem, with more forms of expertise present before the solution is framed?

AI as Infrastructure, Not the Destination

"The software itself is not just the solution. The software is the catalyst."

 

Salima argues that many organizations are still focused on AI as a tool for optimization: saving seconds, making teams more productive, or automating parts of the work. Those uses matter, but they can keep leaders thinking too narrowly. When AI becomes infrastructure, it becomes part of the platform that unlocks growth, capacity, and new ways to work across a system. In software organizations, that means shifting attention from "what tool should we apply?" to "what outcome could this platform make possible?"

Breakthroughs Come From Asking What the World Needs

"The greatest breakthroughs come from people really sitting down and asking what the world needs or doesn't need."

 

Working around Alphabet's moonshot environment taught Salima that breakthrough ideas are not only born from research labs or visionary founders. The next generation of innovation may come from people asking better ecosystem-level questions: how education changes with AI, how talent changes, how information is consumed, and how the labor market shifts around new infrastructure. The barrier to entry is lower now, which means more people can stand in the place where moonshots are imagined.

Third-Space Moonshots Bring the Lab to the Street

"Technology is not the breakthrough. Technology is a partner that allows us to unlock something in a system."

 

In Invent Now, Salima describes third-space moonshots as the convergence of three forces: technology as a co-partner, complex systems such as health, education, mobility, or energy, and human ingenuity from lived experience. This is not simply adding more people to a workshop. It is a different way of discovery, where an engineer, a scientist, a historian, and a street vendor may each see an opportunity the others would miss. As Vasco framed it, this is about bringing street smarts to the lab, and the lab to street smarts.

Humanity Is the Moonshot

"Humanity is the moonshot, not technology."

 

The Zimbabwe Bush Pump example in Salima's book challenges the usual mental model of moonshots. It may not look like a Silicon Valley breakthrough, but it asks a deeper question: who gets to define what counts as invention, and what kind of impact matters? AI may help us build more, faster, and with lower barriers. But Salima's point is that the real opportunity is not replacing human ingenuity. It is helping more people bring their lived experience into the act of building what their communities, teams, and systems actually need.

Becoming a Moonshot Maker

"It's a book to spar with. It's not a book to just read."

 

Salima does not describe Invent Now as a playbook. She describes it as an invitation to spar with ideas, disagree, and use the book to provoke new thinking. For Scrum Masters, agile coaches, product leaders, and software teams, that invitation is practical: stop treating AI as the whole story, and start using it as one partner in a broader discovery conversation. The biggest opportunities may already be visible to people inside the system. The work is to notice them, bring the right knowledge together, and build from there.

About Salima Bhimani

Dr. Salima Bhimani is the author of Invent Now: The Next Leap in Moonshots and CEO of 10X Responsible Tech. A former Alphabet chief strategist for responsible technology, business, and leaders, she worked across Waymo, Wing, DeepMind, and Google X. Her work focuses on AI, moonshots, and inclusive innovation. LinkedIn

 

You can link with Salima Bhimani on LinkedIn, learn more at salimabhimani.com, and read her book Invent Now: The Next Leap in Moonshots.

 

Download audio: https://traffic.libsyn.com/secure/scrummastertoolbox/20261003_Salima_Bhimani_BONUS.mp3?dest-id=246429