I am pretty sure there as boatloads of developers that want to do good and even know what needs to be done just as in every single company I have ever worked with.
And devs are in the perfect position to take on this responsibility. They usually have sufficient domain knowledge and know what it takes to build stuff in this context.
Communication and knowledge should be considered part of the product. You often times still need these kinds of developers to deliver even this aspect. Basically someone who groks the project so thoroughly that they can synthesize disparate pieces of information into something holistic and absorbable.
I read the entire article, twice. Nonetheless, the confusion that set in initially never disappeared. What is the takeaway here? What is specifically advisable in order to facilitate developer happiness? I get that it’s important to invest in tools and training - no mystery there. But something more concrete was expected. What did I miss?
reply