Four scales of #refactoring, defined by how difficult it is to disseminate the change beyond an individual developer's workspace, and therefore whether you need to align on a refactoring *strategy*.

Alt...

Single commit: - Affects a single codebase and built artefact. - Applied by one atomic commit. Multiple commits: - Creates wide-spread change in a single codebase and built artefact. - Use Expand/Contract to minimise disruption to other team members. Multiple deployments: - Cannot change all affected code in a single commit without breaking the system. - Requires multiple deployments with Expand/Contract to avoid downtime. - Delivery rate affects internal quality Multiple releases: - Requires Expand/Contract across multiple organisations to avoid breaking clients - Must meet contractual obligations with respect to API stability and evolution

Expand/Contract: a #refactoring strategy to avoid disrupting work in progress by other team members, or to avoid breaking clients during zero-downtime deployments.

Alt...

Expand/Contract illustrated by an old black-and-white photograph of accordion players. The Expand/Contract refactoring strategy is: 1. Add new features 2. Migrate code to use the new features 3. Remove old features when is safe to do so

To refactor a system from an object-oriented design to a functional design, we adopt a strategy of moving actions to the edge of the system, leaving the application domain model as immutable data and pure calculations.

We are using the terminology of "data", "calculations", and "actions" from the book "Grokking Simplicity" by Eric Normand.

In our workshop we work through different refactoring techniques to move actions to the edge of the system.

#refactoring #architecture

Alt...

Nested hexagons representing the hexagonal architecture, with an arrow labelled "actions" pointing from the center to the edge. The core hexagon representing the application domain model is labeled "Calculations & Data".

Duncan and I will be at #SoCraTes UK on June 18th and will use some of these practices to take control of LLM-generated code. LLMs default to generating code that is monolithic, procedural, and makes wide use of mutable state. #Refactoring is a good way to give the LLM patterns to follow. Separating actions from data & calculations, composing calculations, and proving consistency by type checking, are all good strategies to keep generated code comprehensible by humans.

https://socratesuk.org/training_day.html

A Short Guide to Naming by Tim Ottinger is free with a Leanpub Reader membership! Or you can buy it for $6.50! https://leanpub.com/naming_shortguide #computer_programming #python #javascript #java #web_development #refactoring

replacements.fyi, by @43081j.com (@e18e.dev):

https://replacements.fyi/?ref=frontenddogma.com

#websites #dependencies #refactoring #migrating #maintenance #javascript

A Short Guide to Naming by Tim Ottinger is free with a Leanpub Reader membership! Or you can buy it for $6.50! https://leanpub.com/naming_shortguide #computer_programming #python #javascript #java #web_development #refactoring

Out With the JS, in With the HTML, by @jimniels:

https://blog.jim-nielsen.com/2026/out-with-js-in-with-html/

#javascript #html #refactoring

#urlaub läuft: heute am rechner- backups gemacht, aufgeräumt, Ticket mit Nummer 3xx abgeschlossen (aktuell ist fast 1900), API ganz tief drin in #sQLshell und #dWb grundlegend umgestaltet (großes #refactoring ) und trotzdem funktioniert noch alles! Plan für die nächsten änderungen genau wie die restlichen it Projekte aufgeschrieben, Einkaufsliste für morgen früh ist auch fertig, plan für den Garten ist fertig und dann war ich heute noch ein wenig #windowshopping betreiben...

A Short Guide to Naming: Understand how and why to better name modules, classes, functions, and variables. by Tim Ottinger is the featured book 📖 on Leanpub!

if you've read my chapter on naming in a famous software book (first or second edition) you may want to go a little deeper. Same author, same topic, all-new content!

Link: https://leanpub.com/naming_shortguide

#computer_programming #python #javascript #java #web_development #refactoring

A Short Guide to Naming by Tim Ottinger is free with a Leanpub Reader membership! Or you can buy it for $5.00! https://leanpub.com/naming_shortguide #computer_programming #python #javascript #java #web_development #refactoring

🤦‍♂️ Oh, joy! Another thrilling 12-minute treatise on code complexity that rivals a calculus textbook in zest. Apparently, if you throw enough fancy terms like Cyclomatic and Halstead at your #JavaScript spaghetti, it suddenly becomes gourmet 🤔👌. Who knew #psycholinguistics held the key to #refactoring nightmares? 🍝🔍
https://philodev.one/posts/2026-04-code-complexity/ #codecomplexity #softwaredevelopment #programminghumor #HackerNews #ngated

That’s your clue: refactor first.

(Special case of the general KFB wisdom “First make the change easy, then make the easy change.”)

#Refactoring #ExtremeProgramming #XPLives