Live data from Hacker News

Doing nothing at work

seangoedecke.com

71–80 of 168 posts

Re: Doing nothing at work

#71
the bit about glue work is interesting, because in my time working for megacorps this has been an explicit part of the annual performance review (google called it "citizenship" which I think captured the essence of it - basically "what work did you do to make things better for the rest of the company").

on one hand it does seem a bit messed up - this was not in my "job description", so it was technically unpaid work that was nevertheless a formal part of my expectations. but on the other hand I really liked working in an environment where everyone spent some of their time and effort to improve things for everyone.

also making it an explicit requirement for everyone to do at least attempted to circumvent the more toxic culture of "I am a rockstar engineer and I'm busy doing important things, someone else can do the glue work". not to mention that "someone else" usually ended up being a woman, and that she was almost certainly getting paid less than said rockstar engineer.

the OP's implication is that the company should have formally hired someone to do all the glue work, but it is usually made up of enough diverse pieces that it would be practically impossible to hire a single person to do it - e.g. what sort of job title would cover "write documentation, interview software engineers, and organise a team off-site"? but those were all tasks that needed to be done and the citizenship requirement let the burden be distributed more fairly.

I think a better way to put it is not "don't do glue work" but "don't be the only chump doing unrewarded glue work", i.e. to push for a company culture where everyone is expected to do some of it and where it is formally recognised as work.

Re: Doing nothing at work

#72
post #38

> Second, preventing or mitigating an incident early (even by just knowing the right feature flag to turn off) can save huge amounts of money: both immediate lost revenue during the incident and future lost revenue from customers who would have pulled their business or refused to sign pending contracts. Not to be sarcastic but just to offer an observation: in a sufficiently large or bureaucratic organization, prevent…

I learned this early in a conservative org. Preventing things is risky. Just keep the solution ready for when things go wrong because then you'll get approval.

I've had this in my career also, I've had a solution that was deemed too risky to release by management but would have prevented an outage, but when an outage actually happened that was the first thing they wanted to try and it worked gloriously. I'm thinking that if it was released prior to the incident it would have not have had the same impact on my career.

Re: Doing nothing at work

#73

> Second, preventing or mitigating an incident early (even by just knowing the right feature flag to turn off) can save huge amounts of money: both immediate lost revenue during the incident and future lost revenue from customers who would have pulled their business or refused to sign pending contracts. Not to be sarcastic but just to offer an observation: in a sufficiently large or bureaucratic organization, prevent…

It’s about what people notice. In town governments I’ve heard of cutting popular programs that will provoke an outcry only to get credit for reinstating them, while possibly smuggling through other actions that are necessary but unpopular.

Re: Doing nothing at work

#74
post #64

> I also believe that being too helpful leaves you vulnerable to predators. Tech companies are full of people who want to extract uncompensated work from software engineers4. This is different from work that arrives via normal channels, and for which you’re compensated by promotions, bonuses (and just your normal salary). I’m talking about work that arrives via backchannels, from people who don’t have the ability or…

Eh, I think it depends on how engaged your supervisor is. One of the last people I want to work with is the “it’s not my job” guy. I want to work with people who see a problem and offer a solution, whether it’s in their job description or not. If you’re not being recognized for your work that’s a leadership problem. Stiff arming work feels like a way towards an ossified lumbering work culture.

Startup vs incumbent

Re: Doing nothing at work

#75

Earlier quoted context omitted.

Kent Beck (maybe in Good News Factory but also in talks) that his team would never commit to more than half what they think they can get done. This is a good way to sustainability. And that's the optimization and precedent to set; that we are here for the long term, delivering steadily at a sustainable pace. It's a long game, and over promising only runs down trust, which is your biggest means too getting the space w…

Yep, if you want to run a sustainable business you don't look to fire on all cylinders all the time, but that's the rub, almost no owners are looking to run a sustainable business anymore. Most people either want hypergrowth idiocy or to be bought by the people doing hypergrowth idiocy. Setting consistent expectations means you can plan, you can actually reasonably budget, you can have predictability in your business…

AI has made this way worse - now the thinking is "well, the agent is doing all the work, why can't the engineers make sure it is running on all cylinders all the time, churning out useful code"

Re: Doing nothing at work

#76
post #64

> I also believe that being too helpful leaves you vulnerable to predators. Tech companies are full of people who want to extract uncompensated work from software engineers4. This is different from work that arrives via normal channels, and for which you’re compensated by promotions, bonuses (and just your normal salary). I’m talking about work that arrives via backchannels, from people who don’t have the ability or…

Eh, I think it depends on how engaged your supervisor is. One of the last people I want to work with is the “it’s not my job” guy. I want to work with people who see a problem and offer a solution, whether it’s in their job description or not. If you’re not being recognized for your work that’s a leadership problem. Stiff arming work feels like a way towards an ossified lumbering work culture.

unless you're contracted (fixed bid) working on jobs then you're getting paid hourly, salary, whatever... boss tells you to stand around and shoot the shit, thats what you do. I dont know why people think 'not my job' is a relevant answer... the job is what they tell you to do...

Re: Doing nothing at work

#77

Earlier quoted context omitted.

Don’t you? You can always say no verbally or with non-delivery. Are you working under a continuous and immediate threat of dismissal?

> Are you working under a continuous and immediate threat of dismissal? Definitely! It's been that way everywhere I've ever worked. Unless you are churning out code at maximum speed then it's only a matter of time before you get fired.

[deleted]

Re: Doing nothing at work

#78
post #64

Earlier quoted context omitted.

Eh, I think it depends on how engaged your supervisor is. One of the last people I want to work with is the “it’s not my job” guy. I want to work with people who see a problem and offer a solution, whether it’s in their job description or not. If you’re not being recognized for your work that’s a leadership problem. Stiff arming work feels like a way towards an ossified lumbering work culture.

unless you're contracted (fixed bid) working on jobs then you're getting paid hourly, salary, whatever... boss tells you to stand around and shoot the shit, thats what you do. I dont know why people think 'not my job' is a relevant answer... the job is what they tell you to do...

I do agree with you, and most jobs have a "and other duties as assigned" for that reason.

But I'll equivocate by saying there are exceptions. If you work a union gig (technically a contract), you have to be careful to stay in your lane unless you want a grievance filed. If you are a licensed engineer and your boss tells you to design/stamp something outside your domain of competence, you have a duty to say no. But that kind of stuff is the exception.

Re: Doing nothing at work

#79

> Second, preventing or mitigating an incident early (even by just knowing the right feature flag to turn off) can save huge amounts of money: both immediate lost revenue during the incident and future lost revenue from customers who would have pulled their business or refused to sign pending contracts. Not to be sarcastic but just to offer an observation: in a sufficiently large or bureaucratic organization, prevent…

Many carears are made and bonuses paidout with heroesim trick.

Re: Doing nothing at work

#80
post #64

> I also believe that being too helpful leaves you vulnerable to predators. Tech companies are full of people who want to extract uncompensated work from software engineers4. This is different from work that arrives via normal channels, and for which you’re compensated by promotions, bonuses (and just your normal salary). I’m talking about work that arrives via backchannels, from people who don’t have the ability or…

Eh, I think it depends on how engaged your supervisor is. One of the last people I want to work with is the “it’s not my job” guy. I want to work with people who see a problem and offer a solution, whether it’s in their job description or not. If you’re not being recognized for your work that’s a leadership problem. Stiff arming work feels like a way towards an ossified lumbering work culture.

My pushback isn’t the credit part it is when they try to spring things on you directly instead of going through normal channels. A lack of planning on someone’s part is not automatically an emergency on my part. I see this far more often than credit stealing
Post reply on HN