|
|
|
|
|
by pinewurst
913 days ago
|
|
Speaking as a recently retired PM who knew my business cold, my biggest challenge was designers and developers who prioritized resume enhancement over even the semblance of business/customer success. Not wanting to implement critical functionality because it was “too hard” vs hard selling me on how Rust would change my life (like Scientology) if I’d support a total rewrite. |
|
It’s this mentality which is the problem — that only PMs are thinking about customer/biz success and so they must prioritize and figure out what everyone should work on and when it should be done.
Let’s do a rewrite in Rust. What does this engineer know that we don’t? Why would they say something so incredulous. What if they are thinking about the customer and biz but from a different angle.
Builders - people writing code and designing the actual functionality and experiences somehow became strictly “resources”. The thing that made tech great and allowed for so many companies to flourish was the tech/geek/nerd/hacker spirit that let those who write code decide what to do and how to do it.
Now, we’ve McKinsey’d the whole thing into boring processes that make work for people who don’t design or code. Jira, Google Docs, Slack, etc etc etc