# Let's pick t-shirt tagline!

As you all know, we're very close to sending SWAG to some of you! One of items you'll get is this awesome T-shirt!

As you can see, below the logo we placed a very short tagline: "Making code slightly less wrong.". This is the tagline that was proposed in chat. But not everyone is in chat. So we'd like you guys to give us your proposals and vote to pick the one we’re gonna print.

Here're rules:

• We’ll close the list and voting in January 15th, 2016 @ 1:37pm EST. The answer with the biggest number of upvotes on that date wins and goes to printing. Caveat: this is subject to approval from the design team overlords me.

And here're guidelines:

• It should be a one-liner. So it can't be too long (or too short :)). Probably similar in length to "Making code slightly less wrong."... more or less... :)
• Yea, I think that's it.
• Can they use.. colourful language? (like "Crap"). – Dan Jan 7 '16 at 10:05
• @DanPantry I'd say it depends on context :) – Paweł Jan 7 '16 at 10:06
• I can haz my name on it ? :) – Emily L. Jan 7 '16 at 13:35
• @EmilyL. umm.. I don't think so :) – Paweł Jan 7 '16 at 14:15
• # I survived the The Mission If only you could put links on t-shirts. – Dan Jan 7 '16 at 14:58
• Where can I find a file with that image? I can print it on a shirt myself... – Konrad Viltersten Jan 12 '16 at 9:46
• @KonradViltersten well the Code Review logo is a copyrighted property of Stack Exchange Inc. ..I wouldn't mess with that ;-) – Mathieu Guindon Jan 15 '16 at 17:00

# Making code slightly less wrong.

Just so the ones loving the existing line can vote to keep it.

Credits: @Zak

• I think I really like it. – Morwenn Jan 7 '16 at 12:10
• -1 because less wrong is (already used as) a tagline of the Skeptics community (e.g. Skeptics.SE) – ChrisW Jan 7 '16 at 17:00
• @ChrisW and that means that the Skeptics community has some patent on using "less wrong"? – Simon Forsberg Jan 7 '16 at 17:15
• @ChrisW I can't find any reference to "less wrong" being included in the tagline on skeptics.stackexchange.com – Simon Forsberg Jan 7 '16 at 17:18
• @SimonForsbergMcFeely Merely that I wouldn't choose e.g. "pro choice" or "pro life" or whatever as a tagline either. I'm simply saying that this phrase already has some associations which you may or may not be aware of, and which are more-or-less unrelated to this site. – ChrisW Jan 7 '16 at 17:22
• @SimonForsbergMcFeely Also code isn't supposed to be wrong at all, is it? So isn't "slightly less wrong" a bit of false humility, in this context? – ChrisW Jan 7 '16 at 17:28
• Perhaps this could be revised to 'Making good code slightly less wrong'? – Mast Jan 7 '16 at 19:39
• @Mast Or "Making working code slightly less wrong" – Simon Forsberg Jan 7 '16 at 20:51
• @SimonForsbergMcFeely "working" isn't catchy. I like the proposed tagline for it is funny and also makes reviewers humble, and highlights the fact that there is no perfect code :) – Morwenn Jan 8 '16 at 0:16
• -1 Isn't the whole basis of this site that there's a difference between "good" and "not wrong"? – Ben Aaronson Jan 9 '16 at 12:13
• @BenAaronson Reviews need to be reviewed too, so as long as a review hasn't been reviewed, you can only assume that the code is slightly less wrong. – Morwenn Jan 10 '16 at 17:51
• @BenAaronson How about "Making code slightly less bad." ? – Simon Forsberg Jan 14 '16 at 17:27
• @SimonForsberg Yeah, something along those lines, I'd like. "Less awful" could also work, though possibly too negative – Ben Aaronson Jan 14 '16 at 17:29

# Because all code can be improved.

Except Jon Skeet's

• Just as long as you don't include the part about Jon Skeet, I'm okay with this one. – Simon Forsberg Jan 7 '16 at 17:11
• @SimonForsbergMcFeely the non-bold part isn't meant to be part of the tagline – Mathieu Guindon Jan 7 '16 at 17:24
• Why the "Because"? I prefer "All code can be improved" – rolfl Jan 12 '16 at 0:30
• @rolfl because. – Mathieu Guindon Jan 12 '16 at 21:26
• I prefer "All code can be improved" as well because it doesn't necessarily refer to CR as a community but also works as a standalone statement. – Jeroen Vannevel Jan 14 '16 at 15:38

# Make it work, we'll make it shine

Hints at rule #1 code must already be working, and pretty much sums up what we're all about.

# if (code.isUgly()) { code.review(); }

As a wink to all those who write code for fun and/or for a living. And I think it reads good enough as English for non-coders to "get it".

Alternative (suggested by ChrisW)

### if (code.isUgly) { code.review(); }

(difference is isUgly is a property instead of method)

• Ooh that would look so good on a CR mug! – Mathieu Guindon Jan 7 '16 at 18:20
• @Mat'sMug Yes it would! – Phrancis Jan 7 '16 at 18:20
• Maybe isUgly should be a property not a method. Also the villagers are coming with torches and pitchforks to protest your placement of curly braces. – ChrisW Jan 7 '16 at 18:26
• OK I changed it by removing the extra round braces. – Phrancis Jan 7 '16 at 18:31
• What's with these ugly braces and semicolon? (Obligatory pythonista comment) – 301_Moved_Permanently Jan 7 '16 at 19:13
• At least make isUgly a function call, because publicly accessible members isUgly :) – Emily L. Jan 7 '16 at 19:51
• I'd go with consistency and stick to the SO mug's mug.isEmpty(), so code.isUgly() works for me – Mathieu Guindon Jan 7 '16 at 19:56
• @EmilyL. Look at that, I'm getting a code review on my tshirt tagline ;-) – Phrancis Jan 7 '16 at 20:18
• @Mat'sMug I added both alternatives cuz. – Phrancis Jan 7 '16 at 20:36
• Does 'Law of Demeter' suggest opportunity for improvement? The code appearing twice implies isUgly and review() could be together, as (private) implementation details of Code, for example class Code { internal void improve() { while (isUgly) review(); } bool isUgly etc. } – ChrisW Jan 7 '16 at 23:19
• Should be while – nhgrif Jan 7 '16 at 23:32
• @nhgrif Should be while(code){code.review();} – oliverpool Jan 8 '16 at 8:28
• class Code { internal void improve() { while (improveMore()); } bool improveMore() { ...etc... } } – ChrisW Jan 8 '16 at 21:29
• Forget while loops; make it recursive! Wait, no, then people will just end up on Stack Overflow instead – Flambino Jan 10 '16 at 20:43
• @Mat'sMug On my last assignment, it should be if(true) code.review()... A bit depressing. – Konrad Viltersten Jan 12 '16 at 9:48

## If it's not broken... fix it anyway

• Maybe "If it's not broke, fix it" would be catchier? – Ben Aaronson Jan 14 '16 at 17:30
• Maybe. I was just playing off the "if it's not broken don't fix it" – Raystafarian Jan 14 '16 at 17:31

# Does this code make my ass look fat?

• Oh how I want this shirt. – RubberDuck Jan 15 '16 at 0:05

## There's always room for improvement

Credit to @Pops

I think the phrase came from somewhere on Meta, but I don't know where.

# finally { exceptional code }

Could also be try { exceptional code }, or catch .. of course, with the former being the most logical. But the above reads better, and has a longer "fuse" before you go "wait, what?" :)

Based on a comment exchange with ChrisW on this old community ad suggestion.

• Except, finally runs whether or not... er, whatever. Good one ;-) – Mathieu Guindon Jan 9 '16 at 5:04

# Improving code, bit by bit

I thought I read something similar on the "New Design" post, but couldn't find it.

• I love this. Especially the pun. – user34073 Jan 7 '16 at 16:18
• @Hosch250 It's been almost two days and I still don't get the pun... please, help me out. – Simon Forsberg Jan 8 '16 at 22:26
• @SimonForsbergMcFeely one bit is 1/8th of a byte, isn't it? And changing something bit by bit is also changing things one step at a time. – 301_Moved_Permanently Jan 8 '16 at 22:43
• @SimonForsbergMcFeely Code runs on bits and bytes. – user34073 Jan 8 '16 at 23:15
• @MathiasEttinger Okay then, I did get the pun apparently. I just didn't think it was that funny... – Simon Forsberg Jan 9 '16 at 0:38

# A community working together for better code

Because that's how I feel :)

# Because every programmer needs a reviewer.

They just might not know it yet.

# Where good code comes to get better

• "Where bad code comes to die"? – Konrad Viltersten Jan 12 '16 at 9:50

# { Brace yourselves }

One of the most common review remarks.

• ...if you will, with a bit of meme/pop culture reference (review is coming!). – Lundin Jan 13 '16 at 12:33

# The code cleanup crew

(Make it 30 characters)

# It takes a community to raise a program...

• and it takes one mistake to raise an exception (sorry, had to) – Flambino Jan 8 '16 at 18:54

^ That there is nothing: no tag line at all, only the CODE Q REVIEW logo.

# We can refactor it. We have the technology.

• Don't leave your terminal with an interactive session when marketing might come wandering in. – greybeard Jan 11 '16 at 15:24
• @greybeard is this a reference I should be aware of :x – Dan Jan 11 '16 at 15:27
• None that I'm aware of. We have the technology rings neither coder nor reviewer. – greybeard Jan 11 '16 at 15:38

# Helping you code better

It's not really about making the posted code better. It's really about making the posters write better code in the future. Teach a man to fish.

At first I thought "making your (working) code better", but that's too pedantic, not easy-going enough. "working" code is kind of implied, no need to mention.

# codereview.stackexchange.com

Perhaps a bit boring though.

• 1. perhaps? 2. a bit? – Simon Forsberg Jan 7 '16 at 17:13
• It would be nice if the website URL could be included though... – Simon Forsberg Jan 7 '16 at 17:19
• @SimonForsbergMcFeely yeah. on the back perhaps? – Mathieu Guindon Jan 7 '16 at 17:19
• I'll vote against a URL on the shirt. It just feels like it'd have more of a business card feel to it, which is a lot less cool than the feel it has now. – Veedrac Jan 10 '16 at 9:10

## Making code better, together

"Long enough to cover the subject, and short enough to create interest."

# Making your code suck less

(tongue-in-cheek)

# Detail-Oreinted Developers

Says it all, I think.

PS: typo is intentional, stop fixing it ;-)

• @mattsmug oh come on! – jonrsharpe Jan 7 '16 at 19:18
• LOL! I totally just... lol – Mathieu Guindon Jan 7 '16 at 19:32
• @jonrsharpe got me as well lol. – Phrancis Jan 7 '16 at 20:48
• I find the fact that two members here fixed your bug rather apropos for Meta. For a T-shirt slogan, though, not so much. – 200_success Jan 12 '16 at 7:59

# We take code seriously

Because those who don't just push and deploy.

# Mission Accomplished

or better, lower case:

# mission accomplished

I suggest that, because of this post (plus other reasons which may as well remain nameless) but an overt reason is that people might be proud of having finished their mission (writing working code), and celebrate that. The T-shirt associates that celebration with taking it to the next level (i.e. code review), and implies that the mission is even more accomplished after code review.

Also, given that "brevity is the soul of wit", like @Paweł said, "it can't be too short". ;-)

• Fun fact: "Brevity is the soul of wit" is a quote from a character who just won't shut up, contradicts himself all the time, uses overly large metaphors, repeats himself constantly, and never stops talking, like a drunk man at a subway or a sober man who's so desperate for company he'll talk to the drunk guy just for a little company. – Fund Monica's Lawsuit Jan 8 '16 at 0:07
• You're referring to Shakespeare, are you? ;-) – ChrisW Jan 8 '16 at 0:10
• Yep! We just finished (re)reading Hamlet in English, and I found myself laughing my ass off (again) when Polonius says "Brevity is the soul of wit" right before launching into a two-dozen-line monologue that could have been summed up as "Yep, Hamlet's crazy. With love for my daughter." – Fund Monica's Lawsuit Jan 8 '16 at 0:11
• Paweł said it can't be too short, but I think it could be shorter. – ChrisW Jan 8 '16 at 0:14