4 ms·

I today agree, that devs being part of the creative process and not being drones leads to more happiness and has a lot of upside: they bring new ideas to the ta

I today agree, that devs being part of the creative process and not being drones leads to more happiness and has a lot of upside: they bring new ideas to the table, are more invested in the solution and feel owner ship -> quality of outcome is better. However, in my experience working on a big product with multiple teams, the main problems with devs getting creative is (a) the consistency of the user experience suffers badly (b) the overall architecture erodes as everybody builds particular solutions fitting their specific problem I am not sure what the best way is to reconcile Dev happiness and (a,b) in this context.

blablabla123 7y ago
About (a) and (b), in my first 2 jobs this was a non-issue since my boss always had the last word. I guess today's Agile/Scrum situation is a big improvement over that, where people work data driven and not by personal taste of one person. Anyway, one could solve it by maintaining a ratio of people with a lot of experience. (a) A Designer needs to be on the team that can do a Corporate Identitiy (CI) => this way it's possible that Engineers create their own Bootstrap (b) Either solve it top-down by having an engineer with enough architecture experience; or have architecture guidelines in place / develop them consensus-based At most places there are very concrete guidelines about codestyle, usually ensured by linters. One can also put more emphasis on architecture style