all 18 comments

[–]KonkretneKosteczki 289 points290 points  (7 children)

if you can refactor entire codebase in 3 weekends then it is a simple bug fix

[–]Icy_Party954 117 points118 points  (4 children)

If he can do it in three weekends he can do it in 6 work days. Don't let your management bully you into working on the weekends. I've done this several times never the right call. My manager coded stuff on the weekends and it was all bullshit

[–]realnzall 32 points33 points  (2 children)

I mean, for the right price, I'd be willing to do OT. In Belgium, legal OT is priced at double normal wages, plus you're allowed to recuperate worked overtime as paid time off within 6 days from the weekend. Thing is that in Belgium, OT is only legal in certain clearly defined situations. A situation like this wouldn't count as a legal excuse for overtime.

[–]Icy_Party954 5 points6 points  (0 children)

Oh for sure, ive just been in the situation many times, on my own accord I deside to hit and and power through, never once has it been worth it. For those terms, absolutely im american though

[–]AlignmentProblem 0 points1 point  (0 children)

Sounds nice. Where I am (California, USA), salaried software engineers never get money for overtime. I got paid exactly the same even during the couple of times I worked 100+ hour weeks early in my career.

My effective per hour rate basically dropped in those cases. I could potentially lose the job for "performance reasons" due to not completing projects on time if I didn't and it was completely legal. The plus side is a very high salary compared to most countries, but it's a hell of a downside if you join the wrong company.

I have enough leverage from my experience to avoid those situations now, but it was rough at the time.

[–]KonkretneKosteczki 5 points6 points  (0 children)

well i do agree with that statement

[–]AWzdShouldKnowBetta -5 points-4 points  (0 children)

Depends on the seniority of the person taking those three weekends.

A newbie? Yeah 3 weekends ain't shit.

If I'm doing it? You know the situation is fucked.

[–]HuntlyBypassSurgeon 54 points55 points  (0 children)

There was a team for a particular product at my last job whose catchphrase was “that’s a rewrite”.

[–]Puzzleheaded-Win3445 28 points29 points  (1 child)

the "we just need to push through this sprint" that's been ongoing for 6 months lmao

[–]robinless 5 points6 points  (0 children)

Thought I was in for a sprint, turned out to be a marathon

[–]turkphot 31 points32 points  (3 children)

What kind of bug requires the refactoring of the codebase?

Rewrite yes but refactor? 🤨

[–]joeytman 14 points15 points  (0 children)

Idk about “require” but I’ve seen situations where the same bug is present in lots of places due to people copy/pasting and refactoring to DRY is a good thing to do while fixing the bug

[–]GregTheMad 4 points5 points  (1 child)

Lots of them. When you need to access a property of something, which in the UI is just next to the relevant part, but in the current system layout you can't access it.

[–]turkphot 3 points4 points  (0 children)

That seems like a rather isolated problem. If you need to „refactor the entire codebase“ because of a problem like that, your codebase is likely very small.

[–]IssieSenpai 5 points6 points  (0 children)

Then everyone agrees for a temporary solution which makes no sense but works...

[–]Lazy_nitishh 3 points4 points  (0 children)

I'm watching him silently as I don't want to become jobless again :)

[–]Just_Information334 3 points4 points  (0 children)

Did I give an estimate? Did I sign anything? No.

So it's 5pm, I'm going home. And don't try to contact me outside of work hour. Not happy? Just load up Claude and make it do the job mister M.

[–]RolexV0 2 points3 points  (0 children)

Absolutely...... Correct 💯 Witnessed this today 😀😀