DEV Community

Discussion on: Fight for the Architecture

Collapse
 
eljayadobe profile image
Eljay-Adobe

I'm always surprised at the longevity of culture. What you establish today may still be close to the corporate DNA of the company 50 years from now. You are sowing the seeds of the future. (I'm a bit envious!)

And from Uncle Bob's Clean Code book... the only way to go fast is to go clean. ;-)

One company I used to work at had a change of executive leadership. One of the first things the new leadership did was to charter a new course and instill some dramatic changes to the existing culture.

The ship is turning... ever... so... slowly. After 4 years, my friends that still work there say there has been very little actual change in 4 years. There has been some, but at the current rate of change it may be decades before the new executives' outlined vision is fully realized. Decades.

Change is hard. Organizational inertia is hard to tackle. Six Boxes looks into the sociology & psychology of trying to change a culture. Corporate antibodies, organ rejection (i.e., ignoring executive edicts), and backsliding to the comfort zone of the old ways all act as anchors holding back change.

Thread Thread
 
yellowbrickcode profile image
Sarah Williams

I feel very lucky to be given the opportunity and the trust to lead the culture for the development team :) It's my chance to put into practice all the things I've wanted to see in my previous companies I've worked in.

I've worked at places previously that have been trying to change their culture and seen the same problems you've described. It can take a long time, and in some cases it may never reach their envisioned finishing point. It's still nice to see companies at least acknowledging changes to their culture are required and trying to change it though.