this post was submitted on 15 Oct 2024
311 points (99.7% liked)

Programming

17416 readers
71 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 18 points 4 weeks ago (1 children)

The bloody managers are the biggest problem. Most don't understand code much less the process of making a software product. They force you into idiotic meetings where they want to change how things work because they "don't have visibility into the process" which just translated to "I don't understand what you're doing".

Also trying to force people who love machines but people less so into leading people is a recipe for unhappiness.

But at least the bozos at the top get to make the decisions and the cheddar for being ignorant and not listening.

Anti Commercial-AI license

[–] [email protected] 4 points 4 weeks ago* (last edited 4 weeks ago)

The bloody managers are the biggest problem. Most don’t understand code much less the process of making a software product.

So, I've had my eye on management and started doing some management training. The job of management really isn't to do the work itself (or even to understand the work). That's the job of specialists and technical leads. The job of management is to oversee the workforce (hiring, organizing teams, dictating process, allocating project time, planning mid and long term department goals, etc) not to actually get your hands into the work itself.

It's certainly helpful to understand coding broadly speaking. But I'm in an office where we're supporting dozens of apps written and interfaced with at least as many languages. Nevermind all the schemas within those languages. There's no way a manager could actually do my job without months (if not years) of experience in the project itself.

At the same time, the managers should understand the process of coding, particularly if they're at the lower tier and overseeing an actual release cycle. What causes me to pull my hair out is managers who think hand-deploying .dlls and fixing user errors with SQL scripts is normal developer behavior and not desperate shit you do when your normal workflows have failed.

Being in a perpetual state of damage control and thinking that this is normal because you inherited from the last manager is the nightmare.

But at least the bozos at the top get to make the decisions and the cheddar for being ignorant and not listening.

Identifying and integrating new technologies is normal and good managerial behavior.

Getting fleeced by another round of over-hyped fly-by-night con artists time after time after time is not as much.

But AI seems to thread the needle. Its sophisticated and helpful enough to seem useful on superficial analysis. You only really start realizing you've been hoodwinked after you try and integrate it.

Setting aside the absurd executive level pay (every fucking corporate enterprise is just an MLM that's managed to stay cash positive) it does feel like the problem with AI is that each business is forced to learn the lesson the hard way because no business journal or news channel wants to admit that its all shit.

[–] [email protected] 6 points 4 weeks ago

Reinforcing my headcanon that everyone is.

[–] [email protected] 40 points 4 weeks ago (4 children)

Maybe it is just my experience, but in the last decade, employers stopped trying to recruit and retain top developers.

I have been a full time software engineer for more than a decade. In the 2010s, the mindset at tech giants seemed to be that they had to hire the best developers and do everything they could to keep them. The easiest way to do both was to be the best employer around. For example, Google had 20% time, many companies offered paid sabbaticals after so many years, and every office had catering once a week (if not a free cafeteria). That way, employees would be telling all of their friends how great it is to work for you and if they decide to look for other work, they would have to give up their cushy benefits.

Then, a few years before the pandemic, my employer switched to a different health insurance company and got the expected wave of complaints (the price of this drug went up, my doctor is not covered). HR responded with "our benefits package is above industry averages". That is a refrain I have been hearing since, even after switching employers. The company is not trying to be the best employer that everyone wants to work at, they just want to be above average. They are saying "go ahead and look for another employer, but they are probably going to be just as bad".

Obviously, this is just my view, so it is very possible that I have just been unlucky with my employers.

[–] [email protected] 2 points 4 weeks ago

This is the first rule of sales. It is not important or necessary to be the best. It is only necesaary to be slightly less shitty than your nearest competitor.

[–] [email protected] 2 points 4 weeks ago

Man not all are even trying to beat the average!

[–] [email protected] 14 points 4 weeks ago (1 children)

I've kinda checked out of the private sector for this reason. I've been having a great time working for a government job. Great benefits, union, etc... pay is about 80 percent of what others make but it's more than enough to get by.

[–] [email protected] 5 points 4 weeks ago (1 children)

Man, I'd be happy with 80% of what I get for less stress and more security. What kind of government job specifically?

[–] [email protected] 4 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

What kind of government job specifically?

Most of them. Certainly the ones that have unionized. If you know someone in the inside, they probably know if there's a union.

You'll see more unions in government work because while private organizations breaking up unions is ethically questionable; governments breaking up unions is just openly totalitarian.

If I can't negotiate with a private employer, I might be a wage slave, but I can ask the government for help.

If I can't negotiate with my government job, it's not actually a job, I'm just a slave.

[–] [email protected] 1 points 3 weeks ago* (last edited 3 weeks ago)

I meant more specifically in OP's case, but also which pay that much. When I looked locally (major city) all the G jobs were under 100k. Usually well under.

[–] [email protected] 14 points 4 weeks ago

In the 2010s, the mindset at tech giants seemed to be that they had to hire the best developers and do everything they could to keep them.

Not really. The mindset was actually to hire skilled developers just to dry up the market, so that their competitors would not have skilled labour to develop their own competing products and services.

Then the economy started to take a turn for the worse, and these same companies noted that not only they could not afford blocking their competitors from hiring people but also neither did their competitors. Twice the reasons to shed headcount.

It was not a coincidence that we saw all FANGs shed people at around the same time.

[–] [email protected] 3 points 1 month ago

Yay, horror story time!

load more comments
view more: next ›