Discussion
Loading...

Post

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Hrefna (DHC)
Hrefna (DHC)
@hrefna@hachyderm.io  路  activity timestamp 5 hours ago

RE: https://mastodon.social/@nixCraft/116087634363842093

This is a great take.

Anecdote time.

I worked at a company where the engineering team was a mess. An absolute mess. The company as a whole consistently found that the engineering team would just fail to deliver anything. Releases took literally months and required massive investment, they were error prone, and features would get rolled back.

Over time we fixed it. We got it down to a 6 week release cycle that still had a lot of manual steps, but was no longer being compiled on Ye Random Senior Engineer's laptop. There was unit testing and integration testing. Engineering ran on a kanban-like system and features could be delivered at all and, while they still sometimes took a while still (six week release cycles are still painful), they very very rarely would ever see a rollback.

There was still a lot of room for improvement, but we were improving.

Then something happened.

Engineering no longer was the bottleneck.

Why? Because the company was completely unwilling to let go of customers or features and the squirrels in upper management couldn't stay focused for even a single month, let alone for the three months a full feature release would take.

Engineering, even with all of its flaws, had become increasingly reliable, but the rest of the org still held the company back.

Even when we were at our worst our bottleneck was _never_ the actual generation of code. That was always straightforward. The bottleneck was all of the _other_ stuff that went into it. Resources being undersized or hard to bring up, production toil pulling away senior engineers (in particular), customers whose idea of a modern browser was IE6 and who refused to test releases early, etc.

The company persisted in a delusion that the problem was "if we could just write code faster." That was the motto of upper management.

But the problems were never how quickly the code got generated. The problems were deeply systemic. Most ideas were terrible and even when they weren't terrible we couldn't focus on them, and engineers were constantly stressed by shifting directions, "productiontyped" code that might as well have been hallucinated given its lack of quality controls, and fundamental lack of discipline.

AI wouldn't have changed anything.

nixCraft 馃惂
nixCraft 馃惂
@nixCraft@mastodon.social  路  activity timestamp 9 hours ago

Lmao.

  • Copy link
  • Flag this post
  • Block
Ben Pate 馃馃徎
Ben Pate 馃馃徎
@benpate@mastodon.social  路  activity timestamp 4 hours ago

@hrefna @nixCraft

<blink sarcasm="true">I think you omitted the end of your story, where execs in the C-suite took a deep inward look, accepted accountability, and made the organizational changes necessary to focus on their singular strategic vision.</blink>

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About 路 Code of conduct 路 Privacy 路 Users 路 Instances
Bonfire social 路 1.0.2-alpha.29 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct