this post was submitted on 08 Dec 2024
5 points (69.2% liked)
Economy
501 readers
68 users here now
Lemmy Community for economy, business, politics, stocks, bonds, product releases, IPOs, advice, news, investment, videos, predictions, government, money, politics, debate, current trends and more.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When it comes to project work, it's the quality of work that matters, not the time spent. If someone produces good-quality work, it doesn't matter how they manage their time.
Also, when developers have lots of cross-team and cross-skillset coordination that needs to happen, you can spend the majority meeting, documenting, and reviewing.
Case in point; my Cloud team spends a significant chunk of time coordinating between backend and frontend, Ops, Firmware/Hardware team and DevOps.
Product Owner wants a feature, specs how the feature should look in the frontend, and what the device needs to do when used. Backend has to spec the cloud logic and API glue between them. A feature might need support from DevOps if infrastructure needs to be updated, and Ops needs to know how the feature works to support customers.
It's a whole lot of talk and documentation so that the amount of time we spend coding is as little as possible. That's a good thing. If you're spending the majority of your time writing code, you're probably doing something wrong.
10000000000000%
Employers should be psyched, not critical, when the time spent in executing is minimal.
I love starting a project that involves multiple groups and none of the other groups are even ready to start. It's fucking great.