• 0 Posts
  • 57 Comments
Joined 2 months ago
cake
Cake day: February 22nd, 2026

help-circle

  • This doesn’t spend much time on the scenario where it’s not two peers in the review, but like a junior dev and senior dev.

    I recently did a code review for someone who is very junior 1 , and after spending like two hours fixing all the syntax errors and low level goblins, I realized I couldn’t see the forest at all. I’d been staring at the “this variable is undefined in this case” trees so much. And then they were getting antsy and management was getting antsy…

    1 They’re not actually junior. They’ve been in this role for years. Unfortunately, this org has like no mentorship and no standards, so they haven’t actually learned much in all that time. They’ve just been copy-pasting code until stuff works.




  • Many people take the idea that “everyone is entitled to their opinion” too far, and it turns into “everyone is entitled to their facts”

    Humans are feelings driven, so they’re more likely to go with what their friend says than some mean scientist who makes them feel bad. The inability of people to put aside their feelings is part of why we’re in this mess.







  • I did some webdriver stuff for reasons I don’t remember anymore.

    I also made a simple Django app to track job applications.

    Unsolicited advice:

    • use type annotations. You’ll thank yourself later when your IDE tells you “hey this can be None are you sure you want to call .some_func() on it?”
    • use an ide. Don’t just raw dog it in notepad. You should have syntax highlighting, red squiggles for errors, the ability to go to definition.
    • learn to use a debugger. Pdb is built in and fine.
    • don’t write mega functions that do a thousand things. Split things up into smaller steps.
    • avoid side effects. You don’t want your “say_hello” function to also turn on the lights