Technology

60212 readers

1980 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

448

Tech worker movements grow as threats of RTO, AI loom (arstechnica.com)

submitted 5 days ago by [email protected] to c/technology

91 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] CeeBee_Eh 3 points 3 days ago* (last edited 3 days ago) (1 children)

Then half of your job is dealing with a shitty company and not being a developer.

Partly correct, but yes.

Half of your job is being wasted on overhead you can’t manage.

Who said I can't manage it?

How else to describe it than you are half the dev you could be while you blame everyone else. Shit as a director I’m not mixing words.

Director? That actually tracks. Believe it or not, but a good 30% to 40% of a dev's work is not writing code. You can't just start screwing 2x4s together and expect a house. There needs to be coordination and collaboration between the devs; and paradoxically, the more devs you have the more time is spent on that collaboration and coordination part. It's called The Mythical Man Month. Something managers and directors haven't been able to get into their heads since the 70s.

If you can’t break the problem down part of is on the team but a lot of it is on you.

Break what problem down? What are you on about?

If you want to architect a solution you have to be able to explain it.

Ya, that's absolutely right. And I've yet to meet a PM that can properly explain what they're looking for. They explain result A, they get result A, then suddenly they actually meant result §∆. Happens every time.

It’s pretty bad having to explain this to coddled engineers learning how the other half of the company works.

I know full well how the other half works. Not a lot of complexity there. 90+% of what's said in meetings could be an email. I bet you're one of those directors that insists the devs have daily check-ins (absolute waste of time) and even have some of the other managers and "stakeholders" join to "ask questions", when anyone who isn't a dev has zero right and business to be there. Those stand-ups are not for you and you're just in the way.

Talking as if everyone else doesn’t get it

They don't. It's that simple.

why be an asshole about it?

Did you really just spit in the face of an entire group and then cry about someone being mean when they called you out? If you're a director, holy crap! I pity and fear for the people who work with you.

Why do I get more bs from coders than I do contractors working on my roof?

I have a theory...

My grandfather worked on the Apollo missions so why is C# black fucking magic and suddenly you’re Gandalf?

Your grandfather sounds like he was a smart guy.

It’s not magic. It’s code

To me it's code and logic. To you it's magic.

[–] Beetschnapps 1 points 2 days ago

Yea the delta is important. And the mythical man month also counts ramp up time and not people just being generally incompetent.

Been through lots of engineers that can’t make it past ramp up, where everything is unpossible. Had many pms that couldn’t speak past the problem to save their lives so I feel that. But let’s be clear if there is a way forward don’t obscure the value. Don’t talk down. I work with post docs, principal engineers etc and they seem to be able to break down the problem, meanwhile lower level techs keep up with this shit.