Programmer Humor

19660 readers

784 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

591

Whatever 'Clean Code' you write now, it'll be shit eventually and in need of a complete rewrite (programming.dev)

submitted 3 months ago by RonSijm to c/programmer_humor

89 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] JackbyDev 12 points 3 months ago (3 children)

Which of these do you prefer?

@Test
  public void turnOnLoTempAlarmAtThreshold() throws Exception {
    wayTooCold();
    assertEquals(“HBchL”, hw.getState());
  }

Or B?

@Test
  public void turnOnLoTempAlarmAtThreashold() throws Exception {
    hw.setTemp(WAY_TOO_COLD);
    controller.tic();
    assertTrue(hw.heaterState());
    assertTrue(hw.blowerState());
    assertFalse(hw.coolerState());
    assertFalse(hw.hiTempAlarm());
    assertTrue(hw.loTempAlarm());
  }

Uncle Bob's Clean Code suggests

Option A

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

I almost pulled my hair out when I read that section. One is super obvious without any prior experience with the code. The other is an obscure abomination only he can understand. He’s obviously super proud of his abomination and thinks it’s a prime example of “clean code”.

[–] JackbyDev 8 points 3 months ago

It's also a good example of how being too dogmatic about function length can hide important details.

[–] [email protected] 8 points 3 months ago (2 children)

Why in the holy mother of rust is A the better option?

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

His idea is that it’s faster to read that short string once you learn how to read it. But then you need to learn how to read it.

In my experience, every time I thought of something clever like this, I’ll almost always regret it a month later when I revisit the code.

[–] JackbyDev 4 points 3 months ago

Ask "Clean" Coders I guess lmao. Beats me.

[–] RonSijm -1 points 3 months ago

I've started to prefer option A to be honest.

In C# I'm using Verify - So I prefer to just use Verify(state); and compare the entire state against a json saved state, instead of manually verifying every individual property