2 ms·
I think this is a bad take depending on the context, especially for small companies. First you’re painting developers with a rather broad brush. I know plenty o
by ianbutler 5y ago
I think this is a bad take depending on the context, especially for small companies. First you’re painting developers with a rather broad brush. I know plenty of developers who like to think about how features impact end users and like to interact with people in general to figure out how to build the right features that create that impact. Good developers are perfectly capable of interacting with broader teams to create something that really benefits users.
Similarly not all marketers are “trigger happy with features” a lot of marketers understand how feature work impacts developers and actually take time to figure out the most important features to build and market and don’t have short shelf life.
In my experience you’ve basically just described people bad at their jobs all around.
Following your advice would just be adding potentially unnecessary headcount and creating an unnecessary communication gap between two critical teams, again with a focus on small business or startups. I do think larger companies could do well with less compartmentalization as well though.