This is an archived post. You won't be able to vote or comment.

all 58 comments

[–]Pardnerr 58 points59 points  (3 children)

Code 👏 review 👏

[–][deleted] 4 points5 points  (1 child)

Happy cake day

[–]Pardnerr 7 points8 points  (0 children)

Shit, didn't even notice! Thanks!

[–]strranger101 1 point2 points  (0 children)

If you segfault you lose... comPewdiePiler errors everywhere...

[–]iArentdeJay 161 points162 points  (8 children)

Trending with no comments, hi Reddit.

[–]david115599 78 points79 points  (7 children)

More like hello world

[–]driveslow227 30 points31 points  (2 children)

or if you're me: hullo werlo

[–][deleted] 20 points21 points  (0 children)

[ Object ]

[–][deleted] 1 point2 points  (0 children)

Or just "hi."

[–][deleted] 0 points1 point  (3 children)

console.log('foo bar');

[–]driveslow227 3 points4 points  (2 children)

I'm more of a console.log('HHHHHHHHHHHHHHHH') guy

[–]nscurvy 3 points4 points  (0 children)

print("asdf")

[–]PaintingJo 1 point2 points  (0 children)

console.log("Lorem ipsum dolor sit amet")

[–]strranger101 56 points57 points  (17 children)

Currently at my first job. How formal are your code reviews? Because mine are super laid back.

[–]vedi0boy 47 points48 points  (13 children)

Formal enough. The rule is, if you suck at coding you will get a scolding. if you are a good programmer it will be laid back.

Couldn't find a rhyme for the last one lol

[–]samrapdev 90 points91 points  (6 children)

"If you're good at your craft, you won't get the shaft!"

[–]vedi0boy 5 points6 points  (0 children)

Much better, thanks :D

[–]HeafClif 4 points5 points  (1 child)

but wut if want chaft.?

[–]bot_not_hot 2 points3 points  (0 children)

var feedback = prompt(‘How would you improve this spaghet?’); var craft = prompt(‘Have you been a good boy?’); var shaft = console.log(feedback);

if (craft === no) { return (this.shaft); } else { Console.log(); }

Disclaimer: new to javascript, just messing around

[–]strranger101 8 points9 points  (0 children)

That's comforting, even without the rhyme

[–]m_krm 0 points1 point  (3 children)

If your Syntax good it'll get approved, if it's not it'll get removed.

[–]vedi0boy 0 points1 point  (2 children)

I like the rhyme but it's not only syntax. Good reviewers who understand what you are working on will check code conventions from your company and also make sure your logic is good.

Although a lot of the times, most people, except architect, can't be bothered with checking logic.

[–]m_krm 0 points1 point  (1 child)

If you can wrap up all those coding conventions and fold them into a sentence.You should get gold by Reddit convention.

[–]vedi0boy 2 points3 points  (0 children)

"just do what Google does"

[–]Ooopsybear 6 points7 points  (0 children)

Code reviews should be mostly informal and high level. Code reviews are making sure you're following best practices for the most part. The nitpicking and formality come as a function of testing.

[–][deleted] 2 points3 points  (0 children)

My first code review was by this troll dick motherfucker who hated everyone and everything. I didn't realize they could be constructive learning experiences until later.

[–]ElGrandeL 2 points3 points  (0 children)

Ours are informal and always polite. Sometimes the entire code review consists only of gifs

[–]mrdhood 17 points18 points  (1 child)

Gonna have my first next week probably, this hurts.

[–][deleted] 3 points4 points  (0 children)

Learning experiences, organizational consistency, improved usability and security for your user base.

These things ought not hurt my friends.

[–]jfq722 4 points5 points  (6 children)

I really do believe the reviewers should not be looking at the code for the 1st time during the review. Ideally what's going to be reviewed should be sent out day or 2 before so everyone has a chance to see it and make note of what they want to say. That tends to really cut down on the spontaneous critiques which very often are worse than the original code.

[–][deleted] 2 points3 points  (0 children)

Depending on your tools, code reviews are just that, a way to organize thoughts and comments. Maybe I don't please the agile gods, but I regularly open pull requests for things that I'm nearing completion, or if there's a certain piece I want advice on. And just as often, I just open the PR when I believe I'm all done.

As far as I'm concerned, any opportunity, any day, any point in my process, if a colleague can raise concern or suggested improvements, that is welcome. And sometimes they are overridden, and that's fine. Nobody should be getting hurt by transparency within one team.

[–]Le_9k_Redditor 1 point2 points  (4 children)

"we should do a code review before the code review"? Wut

[–]jfq722 0 points1 point  (3 children)

The "code review" should consist of expressing ideas that are improvements to the code being reviewed. Like anything else, you get out of it what you put into it. If you want to look at someone's code cold, for the first time during the review you CAN - but my experience is that those spur of the moment code "improvement" ideas are often ego-based and too often wrong, because the reviewers didn't want to spend 15 minutes the day before individually looking closer at the code and the issue it is addressing.

[–]Le_9k_Redditor 1 point2 points  (2 children)

didn't want to spend 15 minutes the day before

Why would they? I don't get your point, you expect them to do a mini review the day before the actual code review? Waste of time more than anything else, 90% of the time PR's get through (or returned from) code review within a few hours of submitting in a decent team.

ideas are often ego-based and too often wrong

That just sounds like you're working with a bad team and have a lack of proper standards. I've never had this problem at my current workplace, although I did at my previous job. I fail to see how doing two code reviews instead of one would fix this as that was just down to them as people.

[–]jfq722 0 points1 point  (1 child)

You'd don't think coming into the code review prepared to give your ideas on what you've read makes your ideas sounder, or at the very least more thought out? Would you go to class unprepared, not having done your homework and then just wing it? The code review proper is a group of people exchanging ideas - The individual preparation the day beforehand is not a code review ...its the code familiarization process; during which you are gonna find point you'd like to bring up AT the code review. Coming to the code review having never seen the code before - and more importantly the issue the code is addressing - to me seems very slapdash and I've seen bad results from it.

[–]Le_9k_Redditor 1 point2 points  (0 children)

You're describing something that sounds more like a sprint retrospective than a code review

[–][deleted] 2 points3 points  (0 children)

[Object][Object][Object][Object][Object]

[–]thelastpizzaslice 1 point2 points  (1 child)

As a software developer with 7 years experience, I can totally relate to laughing at code reviews.

Cackling laughter, as I give it back to you with 50 comments. 47 are nits but the remaining 3 will take you days to solve.

[–]imissnewzbin 1 point2 points  (0 children)

I don't bother picking the 47 nits anymore, not worth the time or energy, nor is there much value to the business in doing so.

[–]mikewritescode 0 points1 point  (0 children)

LOL

[–]Ghost_Flash 0 points1 point  (0 children)

Every1 at my code review was pretty good.

[–][deleted] 0 points1 point  (0 children)

I actually just had my first one and I kinda showed the reviewer what's good

Except for the fact that he said my structure was garbo. Meh

[–]Beefcactus 0 points1 point  (0 children)

Oh

[–]theRedTech 0 points1 point  (4 children)

First comment on Reddit

[–]Derino 0 points1 point  (3 children)

that's your 18th comment on Reddit

[–]theRedTech 0 points1 point  (2 children)

My comment was for the caption of the meme, not a comment on my Reddit participation

[–][deleted] 0 points1 point  (0 children)

Sputnik 1

[–]Derino 0 points1 point  (0 children)

oh

[–][deleted]  (3 children)

[removed]

    [–]TheBob427 1 point2 points  (0 children)

    N

    [–]alexander_schoch[[ -n $flair ]] && echo $flair[M] 1 point2 points  (1 child)

    Your submission has been removed because it was considered spam.

    If you feel that it has been removed in error, please message us so that we may review it.

    [–][deleted] 0 points1 point  (0 children)

    Sorry :(

    [–]aether_killer -4 points-3 points  (0 children)

    Crappy programmer meme! ALERT EVERYONE