#engineeringculture — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #engineeringculture, aggregated by home.social.
-
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 -
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 -
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 -
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 -
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 -
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: https://bit.ly/4dAopXL
📄 #transcript included
-
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: https://bit.ly/4dAopXL
📄 #transcript included
-
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: https://bit.ly/4dAopXL
📄 #transcript included
-
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: https://bit.ly/4dAopXL
📄 #transcript included
-
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: https://bit.ly/4dAopXL
📄 #transcript included
-
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 […]https://codeaholicguy.com/2026/05/13/the-new-10x-engineer-with-ai/
-
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 […]https://codeaholicguy.com/2026/05/13/the-new-10x-engineer-with-ai/
-
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 […]https://codeaholicguy.com/2026/05/13/the-new-10x-engineer-with-ai/
-
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 […]https://codeaholicguy.com/2026/05/13/the-new-10x-engineer-with-ai/
-
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 […]https://codeaholicguy.com/2026/05/13/the-new-10x-engineer-with-ai/
-
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
-
Strong leaders rarely fail due to skill gaps. They fail when belief stays unclear. Curious to hear which principle guides your toughest decisions. #TechLeadership #LeadershipPhilosophy #ExecutiveLeadership #DigitalLeadership #EngineeringCulture #TrustInTech #HighPerformance #ResponsibleTech #LeadershipDesign
https://www.linkedin.com/pulse/quiet-power-clear-leadership-philosophy-technology-mohindroo--ra8ec -
Strong leaders rarely fail due to skill gaps. They fail when belief stays unclear. Curious to hear which principle guides your toughest decisions. #TechLeadership #LeadershipPhilosophy #ExecutiveLeadership #DigitalLeadership #EngineeringCulture #TrustInTech #HighPerformance #ResponsibleTech #LeadershipDesign
https://www.linkedin.com/pulse/quiet-power-clear-leadership-philosophy-technology-mohindroo--ra8ec -
Strong leaders rarely fail due to skill gaps. They fail when belief stays unclear. Curious to hear which principle guides your toughest decisions. #TechLeadership #LeadershipPhilosophy #ExecutiveLeadership #DigitalLeadership #EngineeringCulture #TrustInTech #HighPerformance #ResponsibleTech #LeadershipDesign
https://www.linkedin.com/pulse/quiet-power-clear-leadership-philosophy-technology-mohindroo--ra8ec -
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 👉 https://bit.ly/4iE0Vlk
📄 #transcript included
-
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."
https://worstofbreed.net/patterns/nano-service-swarm/
https://worstofbreed.net/radar/2026/#one-to-twenty#devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed
-
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."
https://worstofbreed.net/patterns/nano-service-swarm/
https://worstofbreed.net/radar/2026/#one-to-twenty#devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed
-
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."
https://worstofbreed.net/patterns/nano-service-swarm/
https://worstofbreed.net/radar/2026/#one-to-twenty#devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed
-
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."
https://worstofbreed.net/patterns/nano-service-swarm/
https://worstofbreed.net/radar/2026/#one-to-twenty#devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed
-
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."
https://worstofbreed.net/patterns/nano-service-swarm/
https://worstofbreed.net/radar/2026/#one-to-twenty#devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed
-
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
-
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
-
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
-
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
-
Great read! DevEx is now a core pillar of digital transformation. Leaders who build strong developer environments will shape faster, safer, AI-ready enterprises. What part of DevEx matters most in your org? #DeveloperExperience #DigitalTransformationLeadership #EmergingTechnologyStrategy #CIOPriorities #EngineeringCulture #ITOperatingModelEvolution #PlatformEngineering #FutureOfWorkInTech
https://www.linkedin.com/pulse/developer-experience-devex-why-its-top-priority-sanjay-k-mohindroo--snkfc -
A reflection on why processes and policies can’t replace human behavior — and how true engineering culture must be grown, not enforced. https://hackernoon.com/the-policy-culture #engineeringculture
-
What I’ve been reading (and watching) this week ending 26 October 2025 https://medium.com/@jchyip/what-ive-been-reading-and-watching-this-week-ending-26-october-2025-bfb5e7e716f8 #OKR #TechnicalDebt #AI #EngineeringCulture #ClimateChange #Lean #Economics
-
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: https://www.infoq.com/podcasts/engineering-culture-autonomy-ownership/ #EngineeringCulture
-
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 → https://bit.ly/4nZlDPL
-
Trust builds teams. Ownership drives speed. What’s one tactic you’ll try? #HighPerformanceTeams #TechLeadership #EngineeringCulture #AgileLeadership #BuildToLast #TeamAutonomy #PsychologicalSafety #DeveloperExperience #FeedbackCulture #NetflixCulture #TeamWins #SanjayKMohindroo
https://medium.com/@sanjay.mohindroo66/building-high-performance-technology-teams-6d327131c21a -
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): https://bit.ly/47yhLQu
-
This practical approach addresses specific mission risks, contrasting with projects like JIZAI ARMS from biomimetics labs. See JIZAI ARMS in action: https://www.youtube.com/watch?v=ywrK1yTYRIA. Here, the difference in engineering culture is evident: NASA & MIT prioritize risk minimization, valuing a reliable crutch over a beautiful manipulator tail. #EngineeringCulture #RiskMinimization #JIZAIARMS #Biomimetics #NASA #MIT
-
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: https://bit.ly/4fJ7GCp
📄 #transcript included
-
🤔 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? 📉
https://www.fractionaljobs.io #fractionalwork #corporatejargon #engineeringculture #workplacehumor #jargonoverload #HackerNews #ngated
