Sometimes PMs want to change the flow of way things working. They often say it's a small change and will not take much time. They see things on high level, but they don't see what are the logics behind need to change and what are DB migration required and sometimes it is not possible to change because many things dependent on it.
You should always challenge their assumptions from a dev perspective. If a pm says it's a small change, ask them how are they estimating it's a small chance? What are the factors they are considering? Then show your pov as to what all steps the tasks might take and the estimated time and effort for each task. Bake in the effort required for testing and debugging. When you come with such a view, it's hard for them to counter without logic.
+1
Ngl, most times, PMs don't want things to be hard on you as well haha :p
As @ScarfaceX says, if you (or any other function) bring some logic and data into why our method/thinking is wrong, I'm sure any good PM would be more than happy to change their mind (also depending on situation).
Small change*
Whenever you a call PM fraud here, they come & put justifications like you don't know business, products built by Engineers are shyt, only PMs can build good products, engineers don't prioritize business needs bla bla.
A data scientist/...
Would you report to a pm in a software company if the pm has half the amount or lesser work experience than you, none in your field but is a pm and pm's must be mini ceo's!
It’s clear that companies won’t need engineers 10 years from now.
They’ll just need people who know what to make. Who to sell to. How to sell to. At what price.
This will be the great commoditization of Software development
Ta...
This is an L take for someone who works at Google It is supremely obvious that SWEs are about to enter the golden er...
As a PM I would say it is to delivery high quality product in less time. 🕰️
