71–80 of 202 posts
Earlier quoted context omitted.
My hotter take: All 3 of the engineer, PM and designer will all assume the other 2 are optional, in reality all 3 and the entire company they work for will be optional in most cases.
Good PMs are not optional. Most PMs are.
Companies without any product managers, much less good ones, are putting out profitable products all the time.
My hot take: the dedicated PM role is becoming optional. Engineers already understand feasibility and tradeoffs, and they often end up informing the PM anyway, which usually comes at the cost of meetings and slow decisions. With clear quarterly goals, engineering and design can own product together. They would shape scope, ship in increments, measure, and iterate. So the "product" function still exists, but its not a…
So… I can do it all. Product manage, code, lead a team, even be my own designer in a pinch. But that’s far too much work and context switching for one person. Someone will try, but the reason you tend to build teams of specialists is to let people focus even when they can do lots of different things.
Our job is done for. We will be shown the door, and everyone will rejoice. Everyone will live in a happy world where you'll doddle a house and Claude will build you a next generation SaaS that makes you millions. Managers will do the job of engineers, by just telling LLMs to make an app or to make money or something. C-suites will have agents doing the jobs of managers, and CEOs will run entire companies with a Claud…
I got laid off at a job where this applied, then at another company got rejected because they cancelled the position altogether to use Agentic Coding by Microsoft instead. Then I joined a small consultancy that just lets me build however I want. There's no reviews, no sprint reviews, no evaluation. They trust that you work on what is important. While this is a very messy and unmaintained workflow, it is a lot nicer a…
Scrum is so woefully misunderstood.
It makes sense for small teams (yes, those 4-5 devs), if — and that's a big if — they work together on a single product. It is intended for developers to coordinate with each other, and also provides feedback loops for reality checks and for improvement of collaboration.
If those 4-5 developers work independently from one another, don't have to coordinate, don't need business to tell them what, out of various options, is the most important thing to work on right now, and don't need feedback from users to correct them along the way, then of course they don't need scrum.
Our job is done for. We will be shown the door, and everyone will rejoice. Everyone will live in a happy world where you'll doddle a house and Claude will build you a next generation SaaS that makes you millions. Managers will do the job of engineers, by just telling LLMs to make an app or to make money or something. C-suites will have agents doing the jobs of managers, and CEOs will run entire companies with a Claud…
can't tell if you are serious or not.
> It is truly the next thing, and the future, probably happening in the next 2 years, or in 2 years in 2 years.
Meta, and other large companies have been encouraging PMs to code, while I've seen many negative responses from engineers having to code review, debug, deal with production issues, etc. stemming from crappy code they don't understand. Metrics and KPIs are being gamed into stupid incentives like lines of code, commits, and tickets closed. Leadership claims they are aware of Goodhart's Law, but their actions show other…
An easy correction is to only merge PRs from folks who are on the on call rota. Those not on rota can either join or have their PR receive heavy scrutiny
"Programmers are the ultimate detail managers. All the tiny little details that nobody else wants to deal with wind up in our laps." - Robert C. Martin Let's see if AI makes PMs care for details.
My hot take: the dedicated PM role is becoming optional. Engineers already understand feasibility and tradeoffs, and they often end up informing the PM anyway, which usually comes at the cost of meetings and slow decisions. With clear quarterly goals, engineering and design can own product together. They would shape scope, ship in increments, measure, and iterate. So the "product" function still exists, but its not a…
So… I can do it all. Product manage, code, lead a team, even be my own designer in a pinch. But that’s far too much work and context switching for one person. Someone will try, but the reason you tend to build teams of specialists is to let people focus even when they can do lots of different things.
Earlier quoted context omitted.
So… I can do it all. Product manage, code, lead a team, even be my own designer in a pinch. But that’s far too much work and context switching for one person. Someone will try, but the reason you tend to build teams of specialists is to let people focus even when they can do lots of different things.
Hey you forget sales and marketing. Just do that also.
Earlier quoted context omitted.
I got laid off at a job where this applied, then at another company got rejected because they cancelled the position altogether to use Agentic Coding by Microsoft instead. Then I joined a small consultancy that just lets me build however I want. There's no reviews, no sprint reviews, no evaluation. They trust that you work on what is important. While this is a very messy and unmaintained workflow, it is a lot nicer a…
> it is a lot nicer and I am honestly wondering if Scrum is even necessary when you're only with 4-5 devs. Scrum is so woefully misunderstood. It makes sense for small teams (yes, those 4-5 devs), if — and that's a big if — they work together on a single product. It is intended for developers to coordinate with each other, and also provides feedback loops for reality checks and for improvement of collaboration. If th…
I think it's awful when people follow it slavishly -- you chuck out anything that doesn't fit your team. And yeah, in the example you gave, it's a terrible fit lol
I have some stakeholders that do not know what they want and can't define it, so in desperation I dragged them thorough making fucking user stories -- user stories --and oh my god they loved it lol
They immediately started trying to apply it to everything too. I have regrets.