Changes
We track 17 posts about Changes from 15 engineering blogs. Most active: Red, Soundcloud, CodeName One. Latest post: Oct 3, 2026.
Companies writing about Changes
Recent posts
How to Detect Breaking API Changes with TypeScript and OpenAPI (opens on the source site)
Build a CI pipeline that catches breaking API changes before runtime with oasdiff spec diffing and openapi-typescript type checks in GitHub Actions. Continue reading How to Detect Breaking API Changes with TypeScript and OpenAPI on SitePoint.
Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts (opens on the source site)
Red Hat ·
Upgrading your web server layer can mean an afternoon of dependency updates or 3 months of effort troubleshooting breaking changes. With Red Hat JBoss Web Server (JWS) 7 now generally available—bringing Apache Tomcat 11.0.21, Jakarta EE 11, and Java 17—here is what actually impacts your builds and deployments. The post Upgrading to Red Hat JBoss Web Server 7: Key changes & impacts appeared first on Red Hat Developer.
2 Changes Made Our Azure Durable Functions 3X Faster (opens on the source site)
For one of our projects, we run a nightly job that generates a batch of files. It’s a long process: pulling records from an upstream system, calling several APIs to gather info about each one, generating a file per record, and writing the results back to storage. For a small batch, this works fine, but […] The post 2 Changes Made Our Azure Durable Functions 3X Faster appeared first on Atomic Spin.
We Stopped Waiting for Platform Changes to Find Us (opens on the source site)
A daily Codex task now reads official Apple and Google notices, traces each requirement to Codename One source and build output, and turns verified gaps into fixes before the deadline.
AI seminars — just one of the big changes at LernerPython (opens on the source site)
July and August are often when people take a break or go on vacation. But for me, this summer has been super busy, full of writing and improving LernerPython based […] The post AI seminars — just one of the big changes at LernerPython appeared first on LernerPython.
Preview ESC Changes with Environment Overrides (opens on the source site)
Pulumi ·
Pulumi ESC makes it easy to store configuration and secrets for your Pulumi programs, and with Approvals for ESC you can review and approve changes before they go live. The new --override-env flag lets you preview any environment change, including an unapproved draft, to see exactly how it would affect your stack before it becomes the latest version. Example scenario Your team stores production app configuration in ESC and has enabled Approvals to keep bad values out of critical infrastructure. But one important question remains: how can reviewers properly validate a configuration change…
Treating Pricing Changes Like Code Deploys (opens on the source site)
Making large pricing changes safe to run, safe to resume, and safe to undo.Most days, shipping code to production at Thumbtack is a non-event. You merge your change, a deployment pipeline takes it from there and it rolls out while you monitor the rollout. If a deploy stalls, the system already knows which step it stalled on. If it goes wrong, rolling back is a button away. It’s the return on years of platform work, so routine now that we mostly forget it’s there. Which is the point: Safety is built into the road, not into how carefully each person drives.Changing pricing data never had that…
Upcoming Changes to the Nearby Connections API (opens on the source site)
Android ·
Posted by Wei Wang, Engineering Manager, Android BeTo User privacy and transparency are core to the Android experience. To better align with these principles, we are updating the default behavior of the Nearby Connections API regarding how it interacts with device radios. What is changing? Previously, the Nearby Connections API could automatically toggle Wi-Fi and Bluetooth radios ON to facilitate connections without explicit user intervention. Moving forward, the API will no longer automatically enable these radios for 1P and 3P applications. What this means for developers If your app relies…
Why Carve markup Changes How You Author Rich Text in Shopware 6 (opens on the source site)
One Source, Ten Surfaces Every Shopware shop hits the same wall eventually. You need rich text somewhere the core doesn’t give you a WYSIWYG - a category landing blurb, a brand story on the manufacturer, a formatted paragraph inside a shipping mail - and you’re left with two bad options. Paste raw HTML into a…
Every Choice Changes Everything: The Show (opens on the source site)
About 3 weeks ago, Leo Laporte and I recorded the first episode of what will be a new monthly show on the TWiT network. Naming things is hard, and we almost voted on the name, like we did for Stack Overflow, but we quickly landed on Off By One with
How AI Changes the Role of Applied Scientists (opens on the source site)
Levi Boxell, Tilman Drerup, Alexandr LenkThe Economics Team at Instacart is an applied science team that operates at the intersection of machine learning engineering and economics. Similar to other applied science teams, our work involves a good chunk of engineering, steeped in statistics, math, theory, and strategy. And while that is still at the heart of what we do today, the surprisingly rapid emergence of artificial intelligence has also fundamentally altered our work in ways that we did not see coming.With this post, we want to provide a brief check-in and share an analysis of the…
Smarter deployments in Tinybird: faster schema changes for the most common operations (opens on the source site)
Tinybird ·
Most schema changes don't need a full table rebuild. We added ALTER TABLE support to Tinybird deployments so simple changes deploy in seconds, not minutes.
Upcoming changes to SoundCloud Access Tokens (opens on the source site)
tl;dr: If your app doesn’t store SoundCloud access tokens outside of the context of a user’s client (i.e. a database) the following should…
Making Changes in a Distributed System (opens on the source site)
You have a change to make in a distributed system. How many pull requests will it take to make a change? An Easily-distributed App A distributed system has two or more independent deployables. In this most common of scenarios, we have a frontend (FE) client and a backend (BE) server. It's just so easy to start. We push this architecture all the time. The two apps are not independent, however. They are inter-dependent at runtime. The FE and BE work in coordination to do something. Let's say they want to set a date on an object. There's a contract between the two so that they can talk together.…
An update on our API: Changes to access for inactive apps (opens on the source site)
We’re working on improving our API offering. In order to do that, a few changes are coming: We need to revoke access for some of you with…
A Deeper Dive Into the Fast-Lexer Changes (opens on the source site)
Red ·
What made the fast-lexer branch a priority? Several things. It started when @dockimbel looked into ticket #3606, which was impossible to fix currently, and we didn't want to give up on the auto-syncing between /text and /data facets. So he had to consider bigger options, including how to make the lexer instrumentable. It was not easy, because the current lexer is not re-entrant, so having the lexer emit events to a callback function could have caused serious problems. Digging through all Red's repos showed that the current lexer code was duplicated twice, beyond the basic lexing needed by…
A Deeper Dive Into the Fast-Lexer Changes (opens on the source site)
Red ·
What made the fast-lexer branch a priority? Several things. It started when @dockimbel looked into ticket #3606, which was impossible to fix currently, and we didn't want to give up on the auto-syncing between /text and /data facets. So he had to consider bigger options, including how to make the lexer instrumentable. It was not easy, because the current lexer is not re-entrant, so having the lexer emit events to a callback function could have caused serious problems. Digging through all Red's repos showed that the current lexer code was duplicated twice, beyond the basic lexing needed by…
Related topics
This page is generated automatically from the engineering blogs we follow. Every post links to its source, where it was published. See all sources.