Thread regarding F5 Networks Inc. layoffs

F5 new ceo messed up with layoffs

I think the new CEO and his GMs are rethinking the layoffs now. Ever since he came in and started making changes he really messed up culture. I heard he’s too scared to do anymore layoffs because all the good people have left and issues from customers are starting to hurt their image. They deserve what they pay for.

by
| 2639 views | | 5 replies (last )
Post ID: @OP+110mWV6h

5 replies (most recent on top)

Boy were you wrong. Layoffs still happening.

by
|
Post ID: @Elns+110mWV6h

Couldn't have said it better than first reply.

Irony of all this is the theoretical goal of most of the consultant BS is to try to turn those slow / waterfall / bureaucratic companies into the kind of company F5 already was and used to be.

by
|
Post ID: @8ypa+110mWV6h

Here's the TLDR for that long response. This video describes the App Services GM's personality, approach, and results.

https://rumble.com/v86uql-truck-is-all-blow-and-no-show.html

by
|
Post ID: @7oqu+110mWV6h

The OP is totally on the money. He/she gets it.

by
|
Post ID: @7mbd+110mWV6h

Yes problem is when new CEO took over and staffed upper management with a bunch of outside consultants eager to make their mark / prove their inflated salary and ego, they didn't take the time to understand what they had inherited - they assumed F5 was fundamentally slow / bloated / waterfall company of lazy bureaucratic legacy developers and dead wood, not realizing that F5 had very high competence culture built from the bottom up by PD engineers, like a sort of Google vibe where nobody labelled things and everyone just did "the right thing" without the need for Agile or "Zones" other consultant garbage. That's ruined now. New CEO & co. are to blame. New F5 is full of cargo-cult-engineering and resume-driven-development on projects lasting just long enough for some VP to complete a level-up ("hurray, we containerized X!"... but customers do not give one s**t) then abandon the project or F5 (aka "pivot").

They probably could have just not laid anyone off and instead said "you need to work on this new project area", or "pivot the product to work with this", even if totally new tech for the dev, and it probably would have gone way better than layoffs + Agile consultants.

by
|
Post ID: @5rnx+110mWV6h

Post a reply

: