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

Programmer Humor

32048 readers
1447 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 6 months ago

It's ok we'll QA in prod

[–] [email protected] 1 points 6 months ago

I will say I really like the naming here

[–] [email protected] 7 points 6 months ago

git blame

Naomi Nagata

[–] [email protected] 4 points 6 months ago

Ah, the Season 4 finale of For All Mankind.

[–] [email protected] 7 points 6 months ago (1 children)

Anyone know the artist? Saw another one by them a couple days ago about brute force protection.

[–] [email protected] 9 points 6 months ago* (last edited 6 months ago)

The source is a user on Reddit: https://www.reddit.com/r/ProgrammerHumor/comments/1ayuh4b/comment/krx0p8h/ There are a few more on their profile.

Thanks Google lens

[–] [email protected] 79 points 6 months ago (5 children)

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

[–] [email protected] 5 points 6 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

[–] [email protected] 3 points 6 months ago (1 children)

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

[–] [email protected] 3 points 6 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.

[–] [email protected] 1 points 6 months ago

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

[–] [email protected] 23 points 6 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
[–] [email protected] 11 points 6 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.

[–] [email protected] 6 points 6 months ago

You guys do code reviews?

[–] [email protected] 31 points 6 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.

[–] [email protected] 16 points 6 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.

[–] [email protected] 9 points 6 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.

[–] [email protected] 5 points 6 months ago

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

[–] [email protected] 7 points 6 months ago (1 children)

They still have those control desks in modern missions?

[–] [email protected] 13 points 6 months ago (2 children)
[–] [email protected] 6 points 6 months ago

On the one hand: kind of sad since this isn't too far removed from some workplaces. The hardware and furniture could be sourced from any number of places.

On the other: hot damn. We can get the same kit NASA uses at home. Welcome to the future.

[–] [email protected] 3 points 6 months ago* (last edited 6 months ago)

That's what i meant, all software and plugable devices now. Those desks were prohibitively expensive.

[–] [email protected] 11 points 6 months ago

This got a lot of compression over less than a couple of hours!

load more comments
view more: next ›