this post was submitted on 08 Dec 2024
5 points (69.2% liked)

Economy

501 readers
57 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
top 8 comments
sorted by: hot top controversial new old
[–] procrastitron 16 points 1 week ago (1 children)

The rest of your time will be spent in meetings and responding to emails.

[–] youstolemyname 3 points 1 week ago

Getting stuck in a conversation with your coworker who doesn't know when to shut up

[–] FlashMobOfOne 11 points 1 week ago (1 children)

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.

[–] [email protected] 6 points 1 week ago (2 children)

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.

[–] FlashMobOfOne 6 points 1 week ago

It’s a whole lot of talk and documentation so that the amount of time we spend coding is as little as possible.

10000000000000%

Employers should be psyched, not critical, when the time spent in executing is minimal.

[–] Alexstarfire 1 points 1 week ago

I love starting a project that involves multiple groups and none of the other groups are even ready to start. It's fucking great.

[–] [email protected] 6 points 1 week ago

Sigh.

It's the old "knowing which button to push".

I've spent days having discussions about a change that I understood incredibly well, and "just knew" wouldn't cause issues... And fortunately we discovered through all these discussion, an edge case where the change would've caused a major outage.

The reason business has extensive meetings and discussions is to uncover this stuff.

The actual change is nothing more than clicking a button. But clicking the right one, at the right time.

[–] Oisteink 3 points 1 week ago

Must be universal truth as it comes from trustworthy Amazon