You must log in or # to comment.
If you’re missing deadlines and getting customer complaints because of a new hire, that’s a failure in management, imo.
(Of course, that’s not saying management will take responsibility)
It’s nearly always a failure in management. In every company I’ve worked in, at some level failures come from bad leadership decisions.
Lack of communication, unrealistic deadlines, bad processes, no guardrails, no redundancy, poor/absent/too-harsh feedback, micromanaging, lack of observability, inaccessible resources, poor morale, etc. All management’s responsibility.
heh… every management failure you mentioned was a problem at my last job. impressive.
Devs never miss deadlines or fuck up. Never.
Devs missing deadline because they fucked around, or under estimated the work required and didn’t budget themselves enough time is more there fault (assuming the reason they under estimated wasn’t lack of information from management). Devs missing deadlines because someone tells them Tuesday that they need to drop everything and pick up a 5 pointer and have it done by Thursday, is management’s fault. The “unrealistic” part of the “unrealistic deadline” was the key word there.
Here is a real life example for you. Last year we had a few tasks for migrating our logs and dashboarding from Datadog to Dynatrace. We had just gotten our logs routing to Dynatrace on Wednesday, and were going to start work on migrating our dashboards (or actually rebuilding as there was no way to directly migrate them) the following sprint.
Then on Friday, I get an angry call from a manager of some other team that had some responsibility over the Datadogs licensing asking why we still have logs routing to Datadogs. She says that the license is being hard shut down on Monday and we need to be migrated already. So I had to drop everything. I had to export everything we had in Datadogs, and start manually rebuilding in Dynatrace (which uses a poorly documented proprietary query language I’d never used before), prioritizing the most important stuff for our support team before the weekend lest they fly blind starting Monday morning.
I only found out on Monday that this manager didnt know what they hell she was talking about, that we weren’t on the license being ended, and we had another month to do the migration. I was treated like a fucking champion by my own manager, who had been out of office on Friday, for getting done as much as I had in a single day, but there was no reason for it. She was misinformed from bad communication. And even if she had been correct, her lack of observation on the matter earlier and only informing us about the issue at the last minute was inexcusable. So was her anger over the situation at our team, who doesn’t fucking work for her, btw (not even sure which team she’s over), for not falling in line with a deadline we didn’t know about, or as it turned out a deadline we didn’t even have… bad management.
That sort of things happens a lot, but it’s also when you inform your manager. They may say to go ahead and adjust the schedule or they’re in a better position to politely tell the other manager that their failure to communicate this earlier is their problem and it’ll take as long as it takes.
Either way, you’re covered and do whichever work is appropriate.
She and my tech lead were out of office. I probably could have got in contact with them but I was new to the team, assumed the angry manager was right, that the work was urgent, and didn’t want to rock the boat. So I just did it. Today I’m far more aware of how full of shit some of the other team leaders are.
Most devs absolutely suck at estimating the time involved in a task. If management is setting deadlines by asking “how many hours will this task take” then missing a deadline is on management.
Is senior’s job to multiply junior’s estimate by 3 before telling management.
That is, until Sr. Dev is forced to babysit AI producing PR slop all day while Jr. Dev is looking for a new job.
Wrong
We fire the Sr Dev and get the cheaper Jr Dev to oversee the AI
That would be surprising. Usually, the long-timer who’s built up personal friendships with management is the last to go. Sometimes even if they suck.
Although, maybe in giant corporations with a lot of levels above you that would be less true.
Maybe. Maybe Sr Dev uses their connections to help Jr Dev look for a better job (assuming they like Jr Dev, maybe they look together) and one day Jr Dev helps them back. You never know.
But according to LinkedIn we’re all too crazy about AI to care about Jr Dev if we can have fun with AI. We’re all having a ton of fun using AI, right?
yes. tons. of. fon. 👏.👏.
What would be your favorite most fun part about AI? Mine is constant sorrow, face palming and existential crisis ever since management heard of it.
mine is the bucket of thumbs i gotta carry around if i wanna not look suspicious on camera
I was fine with mentoring junior developers until my manager decided pair programming was the way to go. I’m happy to help and teach, but like fuck am I going to sit at the same goddamn computer with some maroon all day. Can’t even power-nap properly.
pair programming can be really cool. if you have a complex problem, are roughly on the same level as the pair, are both motivated to do it.
that is a huge if. also the reason why it should never be mandated. suggested at most.
The entire reason we developed git was so nobody would ever have to pair program again.
Does he also request you write the code on paper first?
Lol I haven’t coded on paper first since I started programming … in the '70s on my friend’s Commodore-20.
Full agree. Pair programming makes me unproductive and it’s always just feels like one person doing it and the other person in the back saying “uh huh, yeah”. Our place used it as a learning opportunity but the problem is the person I pair with haven’t ever worked on my project and have no clue what’s going on when I’m month deep into a feature branch.
Pair programing with a mentor shouldn’t be a day to day thing. Like why waste the time and put so much pressure on the trainee like that anyways?
Honestly pair programming I feel works better with more similar abilities than far off. Also give em a task to let them struggle a bit in the beginning of the sprint.
Middle management is also there to communicate both ways in order to manage expectations. Especially when the senior dev is busy as well. And ideally the first few weeks to months after onboarding are there for junior devs to train and to get comfortable with the new environment (programmatically and socially). I get a lot of anti-work vibes from Lemmy communities, and while I get that capitalism is bad and big corps are optimizing profits over the employees’ well being, I also think that work doesn’t necessarily have to suck. I mean, it’s pretty neat when someone’s good at a thing and gets paid for doing something they somewhat like and are good at 70% of the time.
If times are rough and you have to take what you can get, that’s obviously shit, though…
Apart from perhaps parenting, work is supposed to be the best, most fulfilling thing in life. The root crime of capitalism is alienation, the source from which every other of its more serious crimes flow.
That is the most privileged thing I have read in a long time.
As you climb the layer cake, be a shit umbrella not a shit funnel.
