|
|
|
|
|
|
by readlikeasloth
1063 days ago
|
|
|
... but then you have two competing organizations: OLD versus NEW. This is how it plays out: NEW starts as your shiny, agile, start-up-ish org with all the young people with the latest ideas. A company nearby got rid of all their freelancers? Great, let´s hire all of them. Think big. Great meetings and people seem to really make progress happen. We´re getting rid of all the REST APIs and introduce Apache Kafka as a message bus for the company. Only then progress stalls and OLD slowly begins to crawl back in. Legal department audits the agile process and unfortunately German laws are quite tough on bogus self-employment. All the freelancers have to go and NEW loses all their expertise. Other employees follow as this whole thing does not pay that great and looks more and more like any other 9/5 job.
Fast forward, 5 years later: the startup spirit is long gone. Corporate culture at NEW mirrors OLD. And not only culture wise. The NEW, "-tech" company is not seen as an independent company any more but supposed to be merged with the parent company. Because why have two of the same, right? Meanwhile OLD made some progress and introduced some reform projects. So developers do not have to fill out a printed paper application to get new servers any more. Only now you have two Kafka clusters with completely different setups as OLD also started their one one at some point. My learning here: new is not new if the culture stays the same. Also: never underestimate the power of old. People always talk about the new, shiny stuff. But old was there first. And is much more resilient than it seems. |
|
|