3 ms·
It's not really about the time it takes for me, it's the division of work into tiny boring pieces, such that they often feel like they're taking as long to disc
by OJFord 4y ago
It's not really about the time it takes for me, it's the division of work into tiny boring pieces, such that they often feel like they're taking as long to discuss & 'estimate complexity' (don't get me started - we don't have 'capacity' for a certain 'amount of complexity' within a.. two week period, so stop pretending it's not a time estimate - anyway..) as they would to do.
I'm reminded slightly of an article submitted here recently - https://martinfowler.com/articles/bottlenecks-of-scaleups/03-product-v-engineering.html https://martinfowler.com/articles/bottlenecks-of-scaleups/03... (though they're not really discussing motivation as such) - it's the detachment of engineering from product, I suppose. Little 'ownership' of or time to spend on thinking about the product experience, just 'do this', 'add that'. If I compare to people I know in other professions - accounting, doctors, tax - they all work more directly with a client or case, manage their own work. Of course they have managers too, but that relationship is more like 'I need some help with this problem that has arisen, let me now brief you on what I've been doing because otherwise you have no context' or longer-term performance etc. - not 'what tiny thing(s) did you do yesterday and which tiny thing(s) will you do today' every bloody morning.
- robertlagrant 4y ago> 's the division of work into tiny boring pieces This is only useful if you want to ship changes iteratively. If you're working a on a big blob of a thing that can have waterfall-style estimation and delivery then you'll avoid all that. > it's the detachment of engineering from product, I suppose This is more likely the cause. The emergence of product as a ruling class over engineering is a problem. Product is a useful concept, but I think we've all assumed only a person with a Product job title can be a product owner in a team, when I think Product adds much more value as a slightly more distant integration point for engineering, marketing, sales, customer support, legal, etc.
- Viliam1234 4y ago> If you're working a on a big blob of a thing that can have waterfall-style estimation and delivery then you'll avoid all that. It seems that among the cool kids, "waterfall" is considered a bad thing that everyone should avoid. I admit I miss the days when I could have spent weeks working on a project without being interrupted by daily "agile" meetings.
- robertlagrant 4y ago> I admit I miss the days when I could have spent weeks working on a project without being interrupted by daily "agile" meetings. I think if there's no team you need to talk to very often and you're working in a pretty static environment then you should be fine. It's just that a lot of those nice problems are harder to come by these days.