home.social

#engineeringculture — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #engineeringculture, aggregated by home.social.

  1. The Engineering Leadership Crisis Nobody Talks About 🚨 #EngineeringLeadership #SoftwareEngineering #PlatformEngineering #TechLeadership #Microservices #SRE

    Modern engineering teams are collapsing under platform complexity, AI chaos, organizational scaling failures, and unreliable architectures. This deep technical leadership guide explains how elite engineering leaders manage platform rewrites, reliability crises, organizational chaos, and large-scale modernization without destroying delivery velocity. #SoftwareArchitecture #EngineeringManagement #DevOps #CloudComputing #Leadership

    atozofsoftwareengineering.blog

  2. The Engineering Leadership Crisis Nobody Talks About 🚨 #EngineeringLeadership #SoftwareEngineering #PlatformEngineering #TechLeadership #Microservices #SRE

    Modern engineering teams are collapsing under platform complexity, AI chaos, organizational scaling failures, and unreliable architectures. This deep technical leadership guide explains how elite engineering leaders manage platform rewrites, reliability crises, organizational chaos, and large-scale modernization without destroying delivery velocity. #SoftwareArchitecture #EngineeringManagement #DevOps #CloudComputing #Leadership

    atozofsoftwareengineering.blog

  3. How do we bring the joy back to #SoftwareDevelopment in the #AIEra?

    In this #InfoQ #podcast, Michael Parker explores “The AI Joy Gap” - why some developers are thriving while others are burning out.

    He dives into:
    ➡️ The “Factory Architect”: orchestrating AI agents instead of writing code directly
    ➡️ Hype vs. Reality: the cultural divide between AI optimism and the reality of wrestling with legacy codebases

    🎧 Listen now: bit.ly/4dAopXL

    📄 #transcript included

    #SoftwareDevelopment #AIagents #EngineeringCulture

  4. How do we bring the joy back to in the ?

    In this , Michael Parker explores “The AI Joy Gap” - why some developers are thriving while others are burning out.

    He dives into:
    ➡️ The “Factory Architect”: orchestrating AI agents instead of writing code directly
    ➡️ Hype vs. Reality: the cultural divide between AI optimism and the reality of wrestling with legacy codebases

    🎧 Listen now: bit.ly/4dAopXL

    📄 included

  5. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  6. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  7. 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

  8. 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

  9. 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

  10. In the pursuit of High-Performing Engineering Teams, we often focus on code commits & metrics.

    But what if the most important signals live in the relationships between teammates?

    In this #InfoQ talk, Lizzie Matusov explores how trust and psychological safety are critical indicators of team success.

    🎥 Watch the video 👉 bit.ly/4iE0Vlk

    📄 #transcript included

    #TeamWork #PsychologicalSafety #EngineeringCulture

  11. In the pursuit of High-Performing Engineering Teams, we often focus on code commits & metrics.

    But what if the most important signals live in the relationships between teammates?

    In this talk, Lizzie Matusov explores how trust and psychological safety are critical indicators of team success.

    🎥 Watch the video 👉 bit.ly/4iE0Vlk

    📄 included

  12. Every generation believes it finally solved complexity.
    Every previous generation already tried.

    What changes is not the problem space, but the tools we use to argue about it.
    And the names we give to old ideas when we rediscover them.

    Progress is real.
    Amnesia is just faster.

    #SoftwareHistory #TechPerspective #SystemsThinking #EngineeringCulture #ByernNotes

  13. worstofbreed.net received two excellent additions to the archive recently. Thanks to Daniel and @stealthmusic for documenting the madness.

    Both submissions have one in common: Excessive Granularity. We are observing teams drowning in repositories, pipelines, and YAML configurations, all in the name of "decoupling."

    worstofbreed.net/patterns/nano
    worstofbreed.net/radar/2026/#o

    #devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed

  14. worstofbreed.net received two excellent additions to the archive recently. Thanks to Daniel and @stealthmusic for documenting the madness.

    Both submissions have one in common: Excessive Granularity. We are observing teams drowning in repositories, pipelines, and YAML configurations, all in the name of "decoupling."

    worstofbreed.net/patterns/nano
    worstofbreed.net/radar/2026/#o

    #devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed

  15. Code reviews are less about correctness and more about shared understanding.

    The best ones improve code.
    The great ones align mental models, spread context, and prevent future mistakes.

    Bugs are temporary.
    Misunderstandings scale.

    #SoftwareEngineering #TeamWork #CodeReview #EngineeringCulture #ByernNotes

  16. Most “technical debt” is not technical.
    It’s organizational memory that never got written down and slowly turned into folklore.

    Decisions made under pressure become invisible assumptions.
    Assumptions turn into constraints.
    Constraints turn into bugs.

    Refactoring code is hard.
    Refactoring shared understanding is harder.

    #SoftwareEngineering #TechDebt #EngineeringCulture #SystemsDesign #ByernNotes

  17. 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.

    👉 authorial.org/byern/technical-

    #SoftwareEngineering #TechnicalDebt #Maintainability #EngineeringCulture #SoftwareArchitecture #Documentation #ADRs #KnowledgeManagement #ByernNotes

  18. 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

  19. 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

  20. I’ve worked on systems newer than today’s trends and older than some of today’s developers.
    The ones that survived were rarely the most elegant, fashionable, or exciting.

    They were understandable.
    They respected constraints.
    They changed slowly and deliberately.

    Most engineering problems are not solved by adding more layers.
    They are solved by deciding which ones not to add.

    #SoftwareEngineering #SystemsThinking #TechExperience #Maintainability #EngineeringCulture #SoftwareDesign #LongTermThinking #ByernNotes

  21. A reflection on why processes and policies can’t replace human behavior — and how true engineering culture must be grown, not enforced. hackernoon.com/the-policy-cult #engineeringculture

  22. A reflection on why processes and policies can’t replace human behavior — and how true engineering culture must be grown, not enforced. hackernoon.com/the-policy-cult #engineeringculture

  23. AWS’s outage exposed something deeper than DNS.
    With over 27,000 layoffs since 2022 - many of them senior engineers - Amazon’s cloud is showing signs of lost resilience.
    Institutional knowledge isn’t something you can hire back overnight.
    💬 What’s your view - are layoffs now a cybersecurity risk factor?
    🔁 Boost this & follow @technadu for more infosec reporting that cuts through noise.

    #AWS #Amazon #TechLayoffs #CloudSecurity #IncidentResponse #OutageAnalysis #InfoSec #CyberResilience #CloudComputing #EngineeringCulture

  24. Autonomy with accountability is the engine for scalable engineering. Marcos Arribas argues ICs own the product with feature flags: empower teams, guardrails, lead by example. Dive into the InfoQ chat: infoq.com/podcasts/engineering #EngineeringCulture

  25. How do you scale #EngineeringCulture as your org grows?

    In this #InfoQ #podcast, Marcos Arribas shares his insights on key strategies for growth, including:
    • Autonomous teams & ownership mentality
    • Progressive feature rollouts with flags
    • Small pull requests
    • Strategic AI adoption
    • Hiring junior engineers for long-term growth

    🎧 Listen now → bit.ly/4nZlDPL

    #EngineeringLeadership #Teamwork #Culture #Productivity

  26. How do you scale as your org grows?

    In this , Marcos Arribas shares his insights on key strategies for growth, including:
    • Autonomous teams & ownership mentality
    • Progressive feature rollouts with flags
    • Small pull requests
    • Strategic AI adoption
    • Hiring junior engineers for long-term growth

    🎧 Listen now → bit.ly/4nZlDPL

  27. Ready to level up your #EngineeringCulture? This #InfoQ #podcast is for you!

    Greg Foster discusses the hottest topics in tech:
    ➡️ The evolution & purpose of #CodeReviews
    ➡️ Building teams with kindness, expertise & urgency
    ➡️ How #AI tools are reshaping software development

    🎧 Listen now (with transcript): bit.ly/47yhLQu

    #SoftwareDevelopment

  28. Ready to level up your ? This is for you!

    Greg Foster discusses the hottest topics in tech:
    ➡️ The evolution & purpose of
    ➡️ Building teams with kindness, expertise & urgency
    ➡️ How tools are reshaping software development

    🎧 Listen now (with transcript): bit.ly/47yhLQu

  29. Want to build a stronger #EngineeringCulture?

    ✅ Lead by example
    ✅ Embrace "glue work"
    ✅ Take full ownership
    ✅ Be self-aware about your career path

    🎧 Dive deeper on the #InfoQ #podcast with Thiago Ghisi for more insights: bit.ly/4fJ7GCp

    📄 #transcript included

    #TechCareer #Leadership

  30. Want to build a stronger ?

    ✅ Lead by example
    ✅ Embrace "glue work"
    ✅ Take full ownership
    ✅ Be self-aware about your career path

    🎧 Dive deeper on the with Thiago Ghisi for more insights: bit.ly/4fJ7GCp

    📄 included

  31. 🤔 Ah, the groundbreaking revelation that part-time work is now called "fractional," because simple terms aren't cool enough for engineers. 🛠️ Let's sprinkle some corporate jargon and make it sound revolutionary, because who wouldn't want to feel like a fraction of themselves at work? 📉
    fractionaljobs.io #fractionalwork #corporatejargon #engineeringculture #workplacehumor #jargonoverload #HackerNews #ngated

  32. 🤔 Ah, the groundbreaking revelation that part-time work is now called "fractional," because simple terms aren't cool enough for engineers. 🛠️ Let's sprinkle some corporate jargon and make it sound revolutionary, because who wouldn't want to feel like a fraction of themselves at work? 📉
    fractionaljobs.io #fractionalwork #corporatejargon #engineeringculture #workplacehumor #jargonoverload #HackerNews #ngated

  33. Ever wondered how to tackle a massive test migration without losing your mind?

    Sergii Gorbachov, Staff Engineer at Slack, reveals how #Slack migrated an incredible 20,000 tests in just 10 months! He shares their unique approach, combining AI with traditional coding methods.

    💡 The big lesson? #AI isn't a magic fix. Human oversight and conventional tools were essential to make it work.

    📺 Watch the #InfoQ #videopodcast on YouTube: youtu.be/Mm-fHvuj_00

    #SoftwareTesting #Migration #EngineeringCulture

  34. Ever wondered how to tackle a massive test migration without losing your mind?

    Sergii Gorbachov, Staff Engineer at Slack, reveals how migrated an incredible 20,000 tests in just 10 months! He shares their unique approach, combining AI with traditional coding methods.

    💡 The big lesson? isn't a magic fix. Human oversight and conventional tools were essential to make it work.

    📺 Watch the on YouTube: youtu.be/Mm-fHvuj_00

  35. A Team / orchestra isn't great because everyone plays the same instrument.
    It's great because each musician plays their part well - with room to rehearse.

    Forcing harmony through buzzwords is like conducting with a broomstick.
    The violinist doesn't need to learn drums just because your last band did. Instruments don't play without musicians.
    Good conductors listen, adapt, and don't drown the music in noise.
    Otherwise, congrats, you’re supervising noise with potential.

    #Leadership #Teamwork #EngineeringCulture #OrchestraLogic #WorkplaceWisdom #BurnoutPrevention #AgileFail #BuzzwordBingo #GoodManagement #Programming #coding