all 6 comments

sorted by: hot top controversial new old
[–] 12 points 1 year ago (3 children)

Honestly, the problem I encounter most with junior devs is that no one taught them to use the scientific method when trying to troubleshoot issues. Seems like everyone wants the answer to be handed to them on a platter and that just ain’t the way it goes.

  • source
  • hideshow 3 child comments
  • [–] 7 points 1 year ago (1 child)

    Honestly, that the problem with most people in most departments. No one learned the scientific method. Engineering, product, marketing. So many just panic and throw shit at the wall with how an understanding of how to isolate a variable.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 1 year ago*

    Kind of felt like that last week. Our web-UI would automatically reload when you switched tabs, clearing out what the user had entered into a form. I started debugging, but the build times of our web-UI have been abysmal, making it extremely tedious to sprinkle log statements over the code for narrowing down what triggers the reload.

    So, I decided to fix the build times first. The solution wasn't complex, basically just pull out a module into a separate library to benefit from incremental compilation, but with all the import changes and some additional restructuring, it still ended up being around 2000 lines of code changed.

    Then I went back to debugging the reload problem, looked at it for 10 minutes, maybe rebuilt 3 times or so, and then made a lucky guess where I just changed one word for another and that fixed it. 🫠

  • source
  • [–] 4 points 1 year ago

    real chad dev fix: -2 lines

  • source
  • 12 comments in c/programmer_humor@programming.dev view that post
    [–] 40 points 1 year ago (3 children)

    Senior Dev: removes line of code. Suddenly works.

  • source
  • hideshow 3 child comments
  • [–] 22 points 1 year ago* (last edited 1 year ago) (2 children)

    Ultimate dev: Removes 2,000 lines of code, works an order of magnitude faster.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 17 points 1 year ago (5 children)

    We have that situation at work.

    Stupid dev creates mega-PRs that do a ton of things that are not part of the ticket and thus aren't tested by QA.

    When it then inevitably fails during release testing or in production, better devs need to spend quite a bit of time to figure out what the hell the stupid dev messed up and the fix is then often just a few lines.

  • source
  • hideshow 5 child comments
  • [–] 9 points 1 year ago (2 children)

    What are the reviewers of these PRs doing? Out-of-scope PRs can be rejected and closed, no?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 1 year ago (1 child)

    It's a really weird team mechanic.

    We have two teams working on the same codebase. The teams are very far apart in terms of organization. We are in different departments.

    That dude is in the other team. Each team does their own code review and is supposed to ask for cross-team review for stuff that affects the other team.

    The guy built himself a reputation as an infallible master programmer in his team by bullying everyone else during PRs. You know, nitpicking tiny non-mistakes like variable names, blocking PRs for weeks by always finding some unnecessary detail, then waiting for a few days after that detail was adjusted to find another one and so on. So his team thinks he's the greatest. Or maybe they are afraid to be his next victim or something. Whatever the reason, they just greenlight everything he does. And he never asks for a cross-team review.

    His boss also completely covers for him, so so far our escalations just went nowhere.

  • source
  • parent
  • hideshow 1 child comment
  • [+] 1 point 1 year ago (2 children)
  • load more comments (-1 replies)
    [–] 8 points 1 year ago

    Senior dev fix: creates a new test case alongside the fix

  • source
  • [–] 0 points 1 year ago

    Hey man. There are writing coders (try things out) and thinking coders (plan things in the head, then write). None is better than the other, both have their own advantages and disadvantages.

  • source