How to make a GOOD Code Review?

Поділитися
Вставка
  • Опубліковано 25 лис 2024

КОМЕНТАРІ • 41

  • @yuriyzhdanov
    @yuriyzhdanov 9 місяців тому +2

    Thank you for your simple English. I can understand everything.

  • @MrKret87
    @MrKret87 4 роки тому +20

    I don't need any code review, I know my code sucks.

    • @sergen1976
      @sergen1976 4 роки тому +1

      MrKret87 the author explained the code review will help you learn to code better :)

  • @KIRILLINGUSS21
    @KIRILLINGUSS21 2 місяці тому +1

    full, beginning, comments, summary, approval or rejection
    polite

  • @CoderFoundry
    @CoderFoundry 4 роки тому +5

    Great Video with great tips. Being nice is an often overlooked superpower.

  • @helloroman
    @helloroman 3 роки тому +1

    „I think you forgot G” - That's what she said. Michael Scott would say 🤣 Congrats on reaching 10k subs. Your channel is really amazing ❤️ Respect!

    • @SmokCode
      @SmokCode  3 роки тому +1

      Thanks for kind words. You're not doing so bad yourself, Mr. Good Times New Roman! Not bad at all...

  • @TravellingFox
    @TravellingFox 3 роки тому +3

    Thanks for making this video. I am gonna show it to my colleagues because you explain the heart and spirit of code reviews so much better than I can possibly do it. =^,^=

  • @RockRiffManiac
    @RockRiffManiac 3 роки тому +1

    Such a detailed and enjoyable video! More people need to watch this

  • @aliBoumedyen
    @aliBoumedyen 4 роки тому +2

    I like the tips about good comments, Good stuff!!

  • @PierreLaBaguette
    @PierreLaBaguette 2 роки тому

    This video has some psychological insights and tips that aren't mentioned in other similar videos. Smart/wise and super useful. Thanks for those too, man!

  • @anicolaspp
    @anicolaspp 4 роки тому

    where can I get that mechanical keyboard?

  • @JavierLunaMolina
    @JavierLunaMolina 4 роки тому +2

    I really enjoyed the video!
    I don't know what's your company's policy on who reviews which code, but I found that if you can choose, people tend to choose good reviewers over bad ones who just approve the changes :)
    When code reviewing, what do you do if you find some code that isn't in the patch but doesn't comply with your quality standard? Do you comment on it for the author to fix it on the same PR or would you just create a task to work on it later?
    Thanks for the video!

    • @SmokCode
      @SmokCode  4 роки тому

      Changes should be related to what is in the commit one way or another - I'd suggest another review if something important isn't fixed. Otherwise - don't fix stuff that isn't broken.

    • @PierreLaBaguette
      @PierreLaBaguette 2 роки тому

      exactly - I prefer my concrete colleague who almost always suggests changes and improvements and basically teaches me over the other colleague who just approves whenever there aren't obvious bugs or code smells

  • @adikztv6371
    @adikztv6371 4 роки тому +2

    very useful video!

  • @igorsk19
    @igorsk19 3 роки тому

    3:00 the most ridiculous part, is this about video editing or code review? :)

  • @robertm647
    @robertm647 4 роки тому

    Great video and excellent tips for writing code reviews.

  • @robinbouwmeester4303
    @robinbouwmeester4303 3 роки тому

    Do you should run and test the changes as a reviewer? Like a whitebox test? We have a testing phase, but this is only blackbox integration test. I experience many pull requests that have unittests with their commit, but when I do an integration test manually the change doesn’t even work 100%. Any suggestions?

    • @SmokCode
      @SmokCode  3 роки тому

      CI pipelines are the only way to go. You need all tests being automatically run as you make your commits to the repository. Look at things like Jenkins, Gitlab CI, Travis or any other tool like that.

    • @robinbouwmeester4303
      @robinbouwmeester4303 3 роки тому

      @@SmokCode we have CI in place, but those tests run only for the master branch.

    • @SmokCode
      @SmokCode  3 роки тому

      @@robinbouwmeester4303 it's a matter of config then

  • @juanpa-a
    @juanpa-a 3 роки тому

    Great video!!!

  • @M4ciekP
    @M4ciekP 4 роки тому

    What keyboard is that?

    • @SmokCode
      @SmokCode  4 роки тому

      Cheap mechanical amzn.to/35cjSag but has custom keycaps amzn.to/3aOBABU that give it this awsum factor.

  • @alvarobazan7683
    @alvarobazan7683 4 роки тому

    I’m working Towards my bachelors in computer science and have 2.5 years left in my program hopefully specializing in block chain technology . Watching your videos are extremely motivating

  • @nasrinkhodayari1186
    @nasrinkhodayari1186 4 роки тому

    simple and efficient

  • @R2r_1337
    @R2r_1337 4 роки тому +1

    Nice!

  • @AhmedHussein-ri3cm
    @AhmedHussein-ri3cm 4 роки тому +1

    Great tips !
    Smok, could you please make a video of how we use advanced data structures and different Algorithms in daily tasks in "Big Companies" , this could be possible ?
    I know that FAANG companies hire Engineers who have a high understanding of DS and Algorithms
    Can a junior engineer join these companies ? can I dream of something like this ?
    as a Senior Engineer, what do you expect from me to know and understand while making an Interview for me.
    Sorry for my strange questions, hope you are fine with them :)
    Your help is highly appreciated, thanks in advance

    • @SmokCode
      @SmokCode  4 роки тому +1

      Every job description has some requirements - depending on the position I would expect different things, but basic CS skills are a must for everyone in tech world. I wouldn't expect advanced stuff from beginners, but data structures and algo is daily bread and butter, so you need to know them.

  • @aknerkan3428
    @aknerkan3428 2 роки тому

    I see what did you do there 02:53 LOL!

  • @sandipansarkar9211
    @sandipansarkar9211 3 роки тому

    nice explanarion

  • @kekekeernest8920
    @kekekeernest8920 4 місяці тому

    2:53 - 3:02, THIS SUCKS!!!!! 😂😂😂😂 , i thinks that is a way better comments

  • @seejanraj
    @seejanraj 2 роки тому

    Thanks

  • @EminoMeneko
    @EminoMeneko 3 роки тому

    2:55 ROFLMAO moment... 🤣 LGTM! 👍

  • @rachel_adams9646
    @rachel_adams9646 4 роки тому +2

    Code reviews have a tendency to become toxic and are often used as a weapon to attack the developer rather than educate. It's my opinion that code review is taken too seriously, its not as important as it’s made out to be. Instead of focusing on the nit-pick of the day, it would be more useful to run the persons code to check the work meets the functional requirements set out in the user story.

    • @SmokCode
      @SmokCode  4 роки тому +5

      I can just say: I feel sad for your toxic environment. Good educative comments can quickly boost your code quality, as you will think of them before posting a CR, and produce better code to begin with.

  • @carlosbp2002
    @carlosbp2002 4 роки тому

    When people understand that code review is just a tool for teaching to write better code is awesome.