this post was submitted on 02 Aug 2024
612 points (97.8% liked)

Programmer Humor

19817 readers
1282 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 182 points 4 months ago (2 children)

Returning and finding everything done is equally suspicious. That's when you have to take a closer look and discover what spaghetti made it through peer review.

[–] [email protected] 65 points 4 months ago (2 children)

Or worse, it means you're not as good as you thought you were.

[–] RadicalEagle 33 points 4 months ago (1 children)

It's not so bad being the worst player on the team. Just means you have a lot of room for improvement as long as you're willing to learn. Honestly it's one of my favorite situations to find myself in. "Oh I suck. How can I get better?"

[–] [email protected] 27 points 4 months ago (2 children)

Sounds good unless you really suck and there is no way for you to improve. I might or might not be speaking from experience.

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

I’m having that same imposter syndrome feeling right now. But one of the SMEs at work today randomly complained to me about another agent and his lack of caring/learning and thanked me for how I am. So. Sometimes it works out well as long as you’ll listen and learn. You can always learn more it just takes time.

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

In most crafts, and I consider software development one, there's rarely no way to improve. The problem arises if the client or the employer wants you to improve too quick, faster than you could, and sometimes faster than even possible.

But to be fair, sometimes developer doesn't want to improve either

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

Imposter Syndrome, I choose you!!

[–] [email protected] 32 points 4 months ago (2 children)

Also, all the automated tests were commented out.

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

Checking the ci logs for the past week, like:

86 test suites passed successfully
    ❌ 0 failures
    ✅ 0 success
    🤷‍♂️ 1785 skipped
[–] [email protected] 21 points 4 months ago (1 children)

Ive heard of stories where people would have an imposed test coverage percentage requirement... and they would just have a single dummy method that printed "." to the console thousands of times. They then have a single test for that one method, and whenever their codebase grows to big, they add more lines to it so that the dummy method has enough lines to meet the test coverage requirement.

[–] [email protected] 10 points 4 months ago (1 children)

Percentage of lines covered by tests is such a terrible metric.

[–] [email protected] 9 points 4 months ago (1 children)

All metrics are terrible when used for anything other than objective analysis

[–] [email protected] 2 points 4 months ago (1 children)

Yeah, every metric that can be applied automatically ends up becoming useless if people are incentivized to break it

[–] [email protected] 9 points 4 months ago (1 children)
[–] [email protected] 1 points 4 months ago

There's always one. Thanks for finding it ❤️