#maintainability — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #maintainability, aggregated by home.social.
-
Write Code That’s Easy to Delete: The Art of Impermanent Software, by (not on Mastodon or Bluesky):
https://dev.to/adamthedeveloper/write-code-thats-easy-to-delete-the-art-of-impermanent-software-19l1
-
Code Maintainability: What Is It and Why It’s Important, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/05/code-maintainability-what-is-it-and-why-is-it-important/
-
Code Maintainability: What Is It and Why It’s Important, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/05/code-maintainability-what-is-it-and-why-is-it-important/
-
Code Maintainability: What Is It and Why It’s Important, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/05/code-maintainability-what-is-it-and-why-is-it-important/
-
Code Maintainability: What Is It and Why It’s Important, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/05/code-maintainability-what-is-it-and-why-is-it-important/
-
Code Maintainability: What Is It and Why It’s Important, by @jetbrains.com:
https://blog.jetbrains.com/qodana/2026/05/code-maintainability-what-is-it-and-why-is-it-important/
-
I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.
https://dev.to/drhyde/god-is-my-copilot-copilot-is-my-new-god-5h6i
-
I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.
https://dev.to/drhyde/god-is-my-copilot-copilot-is-my-new-god-5h6i
-
I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.
https://dev.to/drhyde/god-is-my-copilot-copilot-is-my-new-god-5h6i
-
I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.
https://dev.to/drhyde/god-is-my-copilot-copilot-is-my-new-god-5h6i
-
I've been playing with #Github #Copilot as more than just fancy tab-completion in my editor. This will annoy many people. I agree with most of them on most things. I agree that people responsible for the production of code should think carefully about the code. They should value #readability, #maintainability, #testability etc. I agree that some ways of using #AI for coding are just terrible practice. I just don't think that all AI use is inherently evil.
https://dev.to/drhyde/god-is-my-copilot-copilot-is-my-new-god-5h6i
-
Want fewer rewrites and faster test reviews? Learn how SOLID guides beginners toward clean #PageObjectModel in #Java—with concrete refactoring examples.
Read Savi Grover’s article: https://javapro.io/2026/01/06/learning-java-automation-the-solid-way-a-beginners-guide-to-learn-page-object-model-with-java-solid-principles/
#Java #AutomationTesting #Maintainability #JAVAPRO #CleanCode
-
Want fewer rewrites and faster test reviews? Learn how SOLID guides beginners toward clean #PageObjectModel in #Java—with concrete refactoring examples.
Read Savi Grover’s article: https://javapro.io/2026/01/06/learning-java-automation-the-solid-way-a-beginners-guide-to-learn-page-object-model-with-java-solid-principles/
#Java #AutomationTesting #Maintainability #JAVAPRO #CleanCode
-
I am really torn between letting #AI tackle tasks that I just don't have the time for, or doing it on my own and push through.
Throwing AI on issues may solve a problem, but introduces holes in your #knowledge about and #maintainability of the #code.I can't be the only one. 🫠
-
#Development #Guides
The CSS ‘z-index’ value · “Stop racing for the highest number.” https://ilo.im/16b8yj_____
#Predictability #Maintainability #Stacking #Layers #Tokens #Tooltips #WebDev #Frontend #CSS #JavaScript -
#Development #Guides
The CSS ‘z-index’ value · “Stop racing for the highest number.” https://ilo.im/16b8yj_____
#Predictability #Maintainability #Stacking #Layers #Tokens #Tooltips #WebDev #Frontend #CSS #JavaScript -
#Development #Guides
The CSS ‘z-index’ value · “Stop racing for the highest number.” https://ilo.im/16b8yj_____
#Predictability #Maintainability #Stacking #Layers #Tokens #Tooltips #WebDev #Frontend #CSS #JavaScript -
#Development #Guides
The CSS ‘z-index’ value · “Stop racing for the highest number.” https://ilo.im/16b8yj_____
#Predictability #Maintainability #Stacking #Layers #Tokens #Tooltips #WebDev #Frontend #CSS #JavaScript -
When I talk to people about web quality, they always mention measures based on code #readability and #maintainability. Rarely or never do they mention #performance, #accessibility, or #userExperience.
Performance _is_ accessibility. I think there is so much opportunity for me and my colleagues to raise the bar at the #RaspberryPiFoundation to improve access to kids and educators around the world.
Mike Hall at #SotB26.
-
Why do UI tests slow teams down instead of speeding them up? Savi Grover shows how better Java design (SOLID + POM) turns automation into an asset again.
Worth sharing with your team: https://javapro.io/2026/01/06/learning-java-automation-the-solid-way-a-beginners-guide-to-learn-page-object-model-with-java-solid-principles/
-
Why do UI tests slow teams down instead of speeding them up? Savi Grover shows how better Java design (SOLID + POM) turns automation into an asset again.
Worth sharing with your team: https://javapro.io/2026/01/06/learning-java-automation-the-solid-way-a-beginners-guide-to-learn-page-object-model-with-java-solid-principles/
-
Software engineering is the art of turning "just a small change" into a three-part migration plan, a rollback strategy, and a meeting.
Not because engineers are dramatic, but because reality has:
- hidden dependencies,
- old clients,
- and data that refuses to be reshaped politely.If the change feels small, that is often a sign you have not found the sharp edges yet.
#SoftwareEngineering #EngineeringHumor #TechReality #Maintainability #ChangeManagement #SystemsThinking #ByernNotes
-
Software engineering is the art of turning "just a small change" into a three-part migration plan, a rollback strategy, and a meeting.
Not because engineers are dramatic, but because reality has:
- hidden dependencies,
- old clients,
- and data that refuses to be reshaped politely.If the change feels small, that is often a sign you have not found the sharp edges yet.
#SoftwareEngineering #EngineeringHumor #TechReality #Maintainability #ChangeManagement #SystemsThinking #ByernNotes
-
Software engineering is the art of turning "just a small change" into a three-part migration plan, a rollback strategy, and a meeting.
Not because engineers are dramatic, but because reality has:
- hidden dependencies,
- old clients,
- and data that refuses to be reshaped politely.If the change feels small, that is often a sign you have not found the sharp edges yet.
#SoftwareEngineering #EngineeringHumor #TechReality #Maintainability #ChangeManagement #SystemsThinking #ByernNotes
-
I trust systems that can be explained without adjectives.
If it needs "robust", "scalable", "enterprise-grade", and "AI-powered" to sound plausible, it is probably doing too much. If it can be explained in verbs and nouns, it is probably closer to truth.
Design is not how convincing the story is.
It is how predictable the behavior is.#SoftwareEngineering #SystemsDesign #SoftwareArchitecture #Clarity #Maintainability #EngineeringBasics #ByernNotes
-
I trust systems that can be explained without adjectives.
If it needs "robust", "scalable", "enterprise-grade", and "AI-powered" to sound plausible, it is probably doing too much. If it can be explained in verbs and nouns, it is probably closer to truth.
Design is not how convincing the story is.
It is how predictable the behavior is.#SoftwareEngineering #SystemsDesign #SoftwareArchitecture #Clarity #Maintainability #EngineeringBasics #ByernNotes
-
I trust systems that can be explained without adjectives.
If it needs "robust", "scalable", "enterprise-grade", and "AI-powered" to sound plausible, it is probably doing too much. If it can be explained in verbs and nouns, it is probably closer to truth.
Design is not how convincing the story is.
It is how predictable the behavior is.#SoftwareEngineering #SystemsDesign #SoftwareArchitecture #Clarity #Maintainability #EngineeringBasics #ByernNotes
-
Most migrations fail socially before they fail technically.
Not because people are unwilling, but because the system has hidden contracts: spreadsheets, habits, undocumented workflows, “temporary” scripts that became critical infrastructure.
The code is only the visible part.
The hard part is preserving intent while changing mechanics.#SoftwareEngineering #Migration #EngineeringCulture #SystemsThinking #Maintainability #TechLeadership #ByernNotes
-
There is a quiet kind of technical excellence that looks like “nothing happened.”
No incident. No fire drill. No heroic debugging session.
Just clear boundaries, boring interfaces, and a refusal to let the system become clever in the wrong places.Heroics feel productive.
Routine is what scales.#SoftwareEngineering #Maintainability #Simplicity #SystemsDesign #EngineeringCulture #TechReality #ByernNotes
-
There is a quiet kind of technical excellence that looks like “nothing happened.”
No incident. No fire drill. No heroic debugging session.
Just clear boundaries, boring interfaces, and a refusal to let the system become clever in the wrong places.Heroics feel productive.
Routine is what scales.#SoftwareEngineering #Maintainability #Simplicity #SystemsDesign #EngineeringCulture #TechReality #ByernNotes
-
There is a quiet kind of technical excellence that looks like “nothing happened.”
No incident. No fire drill. No heroic debugging session.
Just clear boundaries, boring interfaces, and a refusal to let the system become clever in the wrong places.Heroics feel productive.
Routine is what scales.#SoftwareEngineering #Maintainability #Simplicity #SystemsDesign #EngineeringCulture #TechReality #ByernNotes
-
7 Ways to Manage Large-Scale Taxonomies:
An experience-based, practical guide to controlling hundreds or thousands of tags.
-
Research on the usage of #AI code assistants and the #maintainability of a system.
https://arxiv.org/pdf/2507.00788
Have yet to read the paper in detail but the summary in this video is already quite interesting: https://www.youtube.com/watch?v=b9EbCb5A408
-
#Development #Approaches
A web component super power · Done right, inheritance shines in design systems https://ilo.im/169d48_____
#Inheritance #OOP #Reusability #Maintainability #JavaScript #WebComponents #DesignSystems #WebDesign #WebDev #Frontend -
StyleX vs. Tailwind: Meta’s Take on CSS-in-JS Maintainability, by @ricmac (@TheNewStack):
https://thenewstack.io/stylex-vs-tailwind-metas-take-on-css-in-js-maintainability/
#tailwind #comparisons #cssinjs #maintainability #css #javascript
-
StyleX vs. Tailwind: Meta’s Take on CSS-in-JS Maintainability, by @ricmac (@TheNewStack):
https://thenewstack.io/stylex-vs-tailwind-metas-take-on-css-in-js-maintainability/
#tailwind #comparisons #cssinjs #maintainability #css #javascript
-
StyleX vs. Tailwind: Meta’s Take on CSS-in-JS Maintainability, by @ricmac (@TheNewStack):
https://thenewstack.io/stylex-vs-tailwind-metas-take-on-css-in-js-maintainability/
#tailwind #comparisons #cssinjs #maintainability #css #javascript
-
StyleX vs. Tailwind: Meta’s Take on CSS-in-JS Maintainability, by @ricmac (@TheNewStack):
https://thenewstack.io/stylex-vs-tailwind-metas-take-on-css-in-js-maintainability/
#tailwind #comparisons #cssinjs #maintainability #css #javascript
-
StyleX vs. Tailwind: Meta’s Take on CSS-in-JS Maintainability, by @ricmac (@TheNewStack):
https://thenewstack.io/stylex-vs-tailwind-metas-take-on-css-in-js-maintainability/
#tailwind #comparisons #cssinjs #maintainability #css #javascript
-
Nobody Knows How Large Software Products Work, by @seangoedecke.bsky.social:
https://www.seangoedecke.com/nobody-knows-how-software-products-work/
-
The Nine Levels of JavaScript Dependency Hell, by @andrewnez:
https://nesbitt.io/2026/01/05/the-nine-levels-of-javascript-dependency-hell.html
-
New article is live on my WriteFreely:
“Technical debt isn’t just code, it’s lost context.”Most teams can point at code debt: missing tests, messy modules, shortcuts taken under pressure. The harder (and often more expensive) debt is the part you cannot point to: the *why* that evaporated. The moment a reasonable decision becomes an undocumented assumption, then a “hard requirement,” and finally a constraint that nobody dares to touch.
The article is built around a pattern I keep seeing in real systems: **Decision → Assumption → Constraint → Incident (or slow bleed)**, plus the symptoms that show up in delivery, operations, and team dynamics when context turns into folklore.
I also propose a few lightweight countermeasures that do not require a documentation bureaucracy: mini-ADRs that take ten minutes, PR prompts that force future-facing context into the open, a simple “folklore detection” checklist, and a realistic 30-day adoption plan for normal teams.
If you’ve ever inherited a system where “don’t touch that, it caused an incident last time” was considered documentation, this one is for you.
👉 https://authorial.org/byern/technical-debt-isnt-just-code-its-lost-context
#SoftwareEngineering #TechnicalDebt #Maintainability #EngineeringCulture #SoftwareArchitecture #Documentation #ADRs #KnowledgeManagement #ByernNotes
-
New article is live on my WriteFreely:
“Technical debt isn’t just code, it’s lost context.”Most teams can point at code debt: missing tests, messy modules, shortcuts taken under pressure. The harder (and often more expensive) debt is the part you cannot point to: the *why* that evaporated. The moment a reasonable decision becomes an undocumented assumption, then a “hard requirement,” and finally a constraint that nobody dares to touch.
The article is built around a pattern I keep seeing in real systems: **Decision → Assumption → Constraint → Incident (or slow bleed)**, plus the symptoms that show up in delivery, operations, and team dynamics when context turns into folklore.
I also propose a few lightweight countermeasures that do not require a documentation bureaucracy: mini-ADRs that take ten minutes, PR prompts that force future-facing context into the open, a simple “folklore detection” checklist, and a realistic 30-day adoption plan for normal teams.
If you’ve ever inherited a system where “don’t touch that, it caused an incident last time” was considered documentation, this one is for you.
👉 https://authorial.org/byern/technical-debt-isnt-just-code-its-lost-context
#SoftwareEngineering #TechnicalDebt #Maintainability #EngineeringCulture #SoftwareArchitecture #Documentation #ADRs #KnowledgeManagement #ByernNotes
-
New article is live on my WriteFreely:
“Technical debt isn’t just code, it’s lost context.”Most teams can point at code debt: missing tests, messy modules, shortcuts taken under pressure. The harder (and often more expensive) debt is the part you cannot point to: the *why* that evaporated. The moment a reasonable decision becomes an undocumented assumption, then a “hard requirement,” and finally a constraint that nobody dares to touch.
The article is built around a pattern I keep seeing in real systems: **Decision → Assumption → Constraint → Incident (or slow bleed)**, plus the symptoms that show up in delivery, operations, and team dynamics when context turns into folklore.
I also propose a few lightweight countermeasures that do not require a documentation bureaucracy: mini-ADRs that take ten minutes, PR prompts that force future-facing context into the open, a simple “folklore detection” checklist, and a realistic 30-day adoption plan for normal teams.
If you’ve ever inherited a system where “don’t touch that, it caused an incident last time” was considered documentation, this one is for you.
👉 https://authorial.org/byern/technical-debt-isnt-just-code-its-lost-context
#SoftwareEngineering #TechnicalDebt #Maintainability #EngineeringCulture #SoftwareArchitecture #Documentation #ADRs #KnowledgeManagement #ByernNotes
-
The systems that last are rarely the smartest ones in the room.
They are not the most elegant, fashionable, or exciting.They survive because people can still understand them at 3 AM, five years later, with incomplete context, stale documentation, and a failing debugger.
They respect constraints.
They change slowly and deliberately.Elegance helps.
Clarity survives.#SoftwareEngineering #SystemsThinking #Maintainability #TechExperience #EngineeringCulture #ByernNotes
