this post was submitted on 25 Feb 2024
959 points (98.1% liked)

Programmer Humor

32479 readers
471 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] SolarMech 79 points 8 months ago (5 children)

If a TODO passes code review, more than one person fucked up.

[–] OsrsNeedsF2P@lemmy.ml 31 points 8 months ago (2 children)

At my first job after university, we did releases every Friday evening. From 3-5pm, all you would see in the Slack channel was a flurry of everyone committing straight to master (with a bunch of merge conflict commits between). Oh and then we'd release. Fun times.

[–] ShadowCatEXE@lemmy.world 16 points 8 months ago

A free for all, late Friday deployment is baffling… We’ve got a strict window of Tuesday-Thursday for releases (unless it’s a critical issue), and a 2-3 day merge freeze to help mitigate unexpected changes.

We’ve got a relatively small team with LOTS of moving parts, so minimizing deployment issues is always top of mind.

[–] SchizoDenji@lemm.ee 8 points 8 months ago (1 children)

I literally know multi billion dollar B2C startups doing the same. It's got so toxic that the management regularly fires people and to fill their spots, they offer obscene amounts of money just for starter positions.

[–] hypertext5689@lemmy.dbzer0.com 4 points 8 months ago

Where's this? I feel like I can milk the company for a little while lol.

[–] winky9827b@lemmy.world 22 points 8 months ago (1 children)

Eh, then you just get those idiots who avoid using TODO: because it makes the code review "harder".

// This is a broken example.
// Note: remove X before doing Y
[–] targetx@programming.dev 10 points 8 months ago

That's no longer a technical process issue but more of a teamcoach/HR kind of issue then. You should be able to assume good intentions from colleagues, imho.

[–] Patches@sh.itjust.works 6 points 8 months ago

You guys do code reviews?

[–] ozymandias117@lemmy.world 4 points 8 months ago

I mean, just look at how many patches in Android are marked DO NOT MERGE, DO NOT MERGE ANYWHERE, etc, but are in mainline

[–] intensely_human@lemm.ee 3 points 8 months ago (1 children)

Especially the devops team. That keyword should be caught in a precommit hook

[–] targetx@programming.dev 3 points 8 months ago (1 children)

We use a CI pipeline check which prevents merges to master if the code contains a TODO. A precommit hook only works if the developer has the hooks configured.

[–] intensely_human@lemm.ee 1 points 8 months ago

See this is why the devops team should do it and not me