Live data from Hacker News

Ask HN: Are most corporate SWE jobs performative?

news.ycombinator.com

121–130 of 307 posts

Re: Ask HN: Are most corporate SWE jobs performative?

#121
post #111

The idea that 1:1s with devs adding very little value to the team is… pretty wild. If you think 1:1s don’t add value, your slice of the reality of what even modestly sized teams need to operate smoothly is so far from my experience I don’t think we’re likely to bridge the divide. But to make a good faith effort: what is the job you think line managers are supposed to be doing, if not listening to devs, going to meeti…

With most of my managers 1:1 have always been a way for them to catch up with what I’ve been working on, despite doing a standup every single day so that the team knows what each other is doing.

I have standup every day so my manager knows what I am doing so my 1:1s are:

- General sentiment about problems with the team and company that bother me but that I don’t have a solution to yet or decided how to bring it up with the team.

- Fun / interesting projects I unilaterally decided to dedicate my working hours towards that I never asked permission to work on. Sometimes it ends up being something cool that my manager wants to join in on or promote to a bigger effort.

- About our lives and what's going on.

Re: Ask HN: Are most corporate SWE jobs performative?

#123
You can get incredible value out of 1-on-1s with capable managers. Insight about where the organization and product is going that you would otherwise miss, you’ll get to rubber duck about your high-level problems with someone who understands them, and its your time to influence decision making. But it does require a capable and motivated manager and an organization that gives the manager actual agency

Re: Ask HN: Are most corporate SWE jobs performative?

#124

Sounds like you think there’s people that shouldn’t be needed? Are they on their way to a layoff or is the company happily holding on to them? If there are no layoffs in their future, they must be creating value you can’t yet see. Get closer to the work they do and maybe you’ll see it. Also: the “waste” might be dwarfed by scale. For example Twitter famously had Linux kernel devs on the payroll. Why would a tweet com…

> Sounds like you think there’s people that shouldn’t be needed? Are they on their way to a layoff or is the company happily holding on to them?

> If there are no layoffs in their future, they must be creating value you can’t yet see.

I've been involved in a few projects where the value appeared clear at the beginning, but by the end there was little value.

In one case the project failed due to incompetence and mismanagement: Basically, the project dragged on and on until it missed its market window. (What stinks is it was basically a port of a Visual Basic sales tool to a more modern v2.)

In another case I was hired into a machine learning project in a company where everyone spent a lot of time justifying their jobs. The project ultimately didn't "improve" over the non-machine-learning approach, and devolved into a "solution in search of a problem".

---

As far as why the company held onto the people involved? (I left after both projects.) That's harder to explain, but I like to think of an analogy to a king holding on to a standing army: It's there when you need it, and your soldiers aren't helping the rival kingdom.

A different way to say it: One of the downsides to working in a large company is that a lot of the people there are "warm butts on seats." The company could function without them. Many of the people you work with have competence issues. You're probably a "warm butt on a seat" too, and may have some competence issues. That's why I like working for smaller companies: they can't afford to be fat.

Re: Ask HN: Are most corporate SWE jobs performative?

#125

Earlier quoted context omitted.

on the flip side, try to get an open source maintainer to define what the criteria are for merging a pull request, or what a bug report needs in order to be fixed. they all say one thing and it is always another. it feels like pulling your hair out.

You forgot the gigachad gif.

"Doesn't merge PRs."

"Doesn't fix issues."

"1m downloads."

Re: Ask HN: Are most corporate SWE jobs performative?

#127
there is a lot to pull apart here

there is always an aspect of every job that is performative - even small companies. I like to call this perception management. a lot of any job is effectively communicating what you're doing. a lot of effective communication is also not just saying what you're doing, but also how you deliver the information. people are more likely to listen when you communicate things in a more positive tone, make the information concise in a bottom-line up-front style, use a deeper voice (told to me by my wife and women colleagues), and pace the information in a way that lets people ask follow up questions iff needed. no one should _have_ to do all this, but it does change people's perception of how competent you are. I've seen both sides of this coin - amazing engineers that get no promo because they can't communicate, and mediocre engineers that get promoted quickly due to their ability to communicate. I'd almost even argue that this is how should be - as you climb the corporate ladder, communication becomes a lot more important than technical skills and ability

to your point about 1:1s: if you're not getting anything out of your 1:1s, that's a skill issue and is on you IMHO. even when I had bad managers, I was able to effectively communicate my needs, goals, updates, thoughts, as well as give feedback back; in doing so, I've been able to turn horrible manager-team dynamics into a positive experiences. and I'd always argue it came down to the fact that the people perceive you directly correlates with how serious they'll take your word

at the same time, I can empathize with the idea that some middle managers are just bodies that get in the way - everyone's had their fair share of that. but if you're actually good at your job and communicating , you should almost always be able to get around them when it's really necessary

EDIT: and this is coming from a person who is and will always want to stay as an IC engineer

Re: Ask HN: Are most corporate SWE jobs performative?

#129
post #111

The idea that 1:1s with devs adding very little value to the team is… pretty wild. If you think 1:1s don’t add value, your slice of the reality of what even modestly sized teams need to operate smoothly is so far from my experience I don’t think we’re likely to bridge the divide. But to make a good faith effort: what is the job you think line managers are supposed to be doing, if not listening to devs, going to meeti…

With most of my managers 1:1 have always been a way for them to catch up with what I’ve been working on, despite doing a standup every single day so that the team knows what each other is doing.

I used to be a believer in daily standup plus bi-weekly sprint planning, but lost faith with the (possibly cargo cult) methodology I was trying to follow. Adding 1:1 in with that would be far too frequent, and probably far too little real content in each meeting.

Did productivity actually change dispensing with those meetings? Probably not by much, it's hard to say empirically because task estimation was always a wildcard.

Qualitatively, I think a good balance is twice-weekly standup, bi-weekly long form. It adds some structure and regular communication, I think it helps people feel better and have a bit more relationship. But I supplement this with frequent invitations to talk about product ad-hoc, talk about tasking ad-hoc if you feel you're not productive, and schedule more pointed meetings with me whenever I'm free. Which is almost all the time, because I need to not be in meetings in order to get work done or spend time thinking.

Honestly, I don't begrudge anyone a job. If people want to do SWE as a performative role, I'll detect that fairly quickly and let it be, even people under me if I were to climb the org chart beyond the first rung. They actually do serve some benefits to the company and to society, as long as they are amicable and respond positively to requests. I'm eventually going to tune them out for serious/urgent development work, and no one can make any guarantees about protection from layoffs, period. C'est la vie.

If people are driven to achieve more, love engineering products, and enjoy working with technology, it's going to be obvious. We will end up working together to solve problems like gravity creates stable orbits. But I can't realistically only hire those people, or run even a medium size company with only the vital few on payroll. It's statistically unlikely, that's why a unicorn startup is a unicorn. Statistically most SWE roles exist outside of that... right? Like after IPO, in big companies where some amount of bureaucracy is just a fact of the size of the machine.

EDIT: twice weekly standup, although I guess bi-weekly can mean both every other week and twice a week?

Re: Ask HN: Are most corporate SWE jobs performative?

#130

Earlier quoted context omitted.

Usually people clam up and are not vocal during group meetings. I am not one of them but it's super common. 1-1s allow people to be more candid.

I am not against 1 on 1's, but making that a regularly scheduled thing as if that adds value is kind of what I am arguing against. If people don't feel comfortable voicing something unless it is in private to their manager, that suggests to me two things - the manager/leadership is not fostering a collaborative environment, or the person needs to work on that (with the assistance/support of their manager), which I se…

You are working against human nature if you think most people are not going to feel more comfortable talking about private matters in a 1:1 vs a public environment.

You're also an asshole manager if you're giving any sort of negative feedback on a person in a public setting.

You could always just schedule a meeting when someone needs a course correction, but then your employees who are clever little humans, will quickly figure out that any ad hoc meeting is going to be a problem for them and then have anxiety about those, even if its going to be a positive meeting for once.

Have you never heard people joke that their boss asked them for a quick chat and they thought they were getting laid off?

Post reply on HN