#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/
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
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
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
Most “architecture” conversations start with boxes and arrows.
The systems that survive start with invariants.
What must never happen? What must always be true? What can be eventually true?
If you cannot answer those without drawing a diagram, the diagram is premature.
I’ve seen beautiful designs fail because nobody wrote down the invariants.
And I’ve seen ugly systems run for a decade because someone did.
#SoftwareEngineering #SoftwareDesign #Maintainability #Architecture #ByernNotes