Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think in part it's the industry's attitude towards software engineering, and undervalueing technical work. Most companies do this by adding more responsibilities than just building the software and maintaining it as if that isn't hard enough. It's everything from managing the project to being repsonsible for releasing and communicating the changes. People have limited time to specialize and become experts in the systems they build and slicing products vertically so that each engineer has a tiny slice of the entire business is producing fragile systems across the industry.
 help



I don't agree. As a senior engineer I don't really want other people managing my projects or attempting to release and communicate my changes. I design a system (in collaboration with colleagues and stakeholders), I communicate how long it will take and why, and I'm responsible for putting it into production and making sure it works. All of this is just part of being a professional who takes responsibility for their work. Delegating any part of that to someone else would give away more agency in my work than I'd like.

I'm willing to concede that there may be other areas of software engineering where it makes more sense to have the narrow specialists you describe, but it hasn't been my experience. Also for junior staff it might make sense for their senior peers to project-manage them a little bit so that they're not too far outside their comfort zone.


I don't get why management is seen as some higher level job. It's actually lower level in my opinion. It's just a matter taking some notes and then telling others of the status. The problem is it's time consuming, time that could be spent ensuring there are no bugs and everything works perfectly.

In my experience what instead happens is that companies are ok with bugs so long as you communicate why it happened and how you are going to fix it. So the tradeoff is clear, spend a lot of time managing and let bugs happen so long as they are being managed properly. This is what I think causes fragile software at scale. People with high level technical knowledge should be hands on, and any bugs should be unacceptable.


I used to think like this, but I changed my mind after many years and seeing different companies and management. I now believe that management is what makes or breaks a company, and it's certainly not just a matter of taking notes and broadcasting status. Accepting some bugs is totally fine and normal when there are bigger priorities.

To the type of people who are higher-level managers and make decisions on organization, that's how it works. You have to start off at the bottom, schmooze and catch the sight of people above, so they move you up. It's just an entirely non-technical POV.

So you never had your manager suggest adding Bob and Mary to your project so it can be completed sooner?

I have, and I usually explain that you can’t get nine women together and have a baby in one month.

They usually do as they please, and assign extras or not, and ultimately learn in the long run.

This isn’t to say that extra staff on a project can’t be helpful. But more often than not, management miss-estimates how the extra staff will impact the project.


Long ago while I was the Pres of the local IEEE chapter, I was out to dinner with the section chief and her VP and the VP said engineers were the only professionals who handed over their hard work willingly for no guarantee of anything. His view was that the smart engineers learned how to exploit the company resources for their own research in patent seeking...other than that he was quite angry that engineers never unionized.

can you imagine if the IEEE had formed a union, way back in the 40's or so...???


To be fair I worked with engineers who used codebase as their own playground. You're interested in this methodology, language, pattern? Fuck anything else, fuck any standards that the team has, fuck other people that will have to cleqn after you and the outages you're causing - you just go hog wild, your friend approves PRs, nobody else understand what's going on because you decided to write something in brainfuck and then, after you leave I can see you give presentation about how brainfuck driven development is the next big thing and how your consultancy will solve every problem one might have

scenario you describe not far from the situation we are now in, except the brainfuck code is being written by general requests to one kind of coding LLM or another

I can see where the code so brilliantly crafted today, and unintelligible to it's inheritors, would result in the same kind of frustration...

...except no human to stare in the face and scream at


I’m a “working manager” in my company. I now have a contract through my company with one of our clients. On that contract I’m probably short 2.5 people (it’s just me right now). I’ve raised it on both sides.

The shits that I give wax and wane on a quarterly basis, but the average pattern is me being largely disengaged, disincentivized to well, and burnt out. I’ve basically told my company they can’t really count on me for anything.

Maybe they’re trying to get me to quit or waiting for the contract company to hire me direct.

Sorry, different type of “added responsibilities “


Managers are extremely important. If anything I'm advocating for more management. Instead companies have offloaded a lot of those responsibilities unto engineers. Management is a hard skill and could free up technical people to focus and produce high quality software. If it's really necessary that engineers also do some management, I think it can be a role people switch into per project instead of always being a kind of hybrid.

Hope you find some resolution on your side. It can be tough sometimes.


Agree. The problem is that managers tend to move their responsibility onto engineers. Should I need to understand why do you want to build X that does Y? No, I should get a spec where you describe the outcomes. Each to their domain - devs to technical, product to business. Instead I learn why the sprockets are of flubber color because it resonates with women aged 10-30

> and undervalueing technical work

The Seattle area is full of tech employees who are millionaires and some even up to 9 figures.


> some even up to 9 figures

I think you're conflating very different groups. Folks with 100+ million dollars to their name are going to be owners rather than "tech employees" and I'd guesstimate 100 of them before filtering for "tech".


Monetarily valued for sure, but it would be interesting to know what split of politics and actually applying their craft got them the millions.

SV is also not the whole industry so looking outside of that, I see exactly what OP is saying. Technical staff are usually required to split their time across numerous project management tasks that are mostly to support the project management team's communication of goals to the client up the ladder. I am not purporting to have a solution to the problem mind you, it's more complex than just "let em code man!"


I bet in general it is not because of their technical expertise as much as their management skills. Engineers are increasingly a hybrid role and you can't just spend your day solving technical problems (even though in most companies I've seen everything is constantly breaking and full of bugs).



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: