They chose mine! THEY CHOSE MINE!

try{
❤️
}catch(){
🍺
}

Commenting out unneeded code instead of deleting it.

z-index : 999999;

The worst bad practice I do is I keep going to work.

Many years down the road I will probably look back and say I should have spent more time with my wife (who are you?) and children (wow, you are tall).

Changing numbers on CSS randomly until it works.

Aka, using magic numbers

I can't even type my name correctly if someone is looking on my screen.

Start a billion personal projects and work on none of them...

I always forget to commit my changes and then when someone reminds me, I usually commit 1 weeks work in one single commit.

SSH as root

I use pictures of clouds as the background for anything related to cloud computing

Sometimes I'm lazy and if I'm writing unit tests and there's a complicated case to test I'll just skip it.

I encrypt passwords with Base64

Ignoring IE compatibility

If (condition)
return true
else
return false
😂😂😂

Oh also empty catch blocks

Pair program with myself. It's lonely but 3x more effective than pairing with my idiot colleagues

Procrastinate until 1 day before deadline

Mixing tabs with spaces ¯\_(ツ)_/¯

Sleep less than 6 hours every night and "compensate" the following day with huge quantities of coffee and energy drinks.

$(this).parent().parent().next().find(..

Not writing tests.

Yes we exist.

I use different variations of the same password. Everywhere.

It's worked out good so far but I can see it all crashing down on me at some point.

chmod 777

git commit -m "did a bunch of stuff"

I commit all my code for the day as one commit 😱

I use "go to"

Memes during team meeting

Z-indexing my whole life.

9
99
999
9999
99999
999999999999
999999999999999999998

git commit -m "Fixes"

Always having a single branch, the master one 😅

Copy & paste code. 😬

Welp. Time to mess with a new distro
*sudo rm -rf /*

*looks at screen* I forgot to back up my db's :|

void my_first_function();
void mySecondFunction();

Inline styling

Taking a picture of my screen with my phone instead of screenshooting it

Hardcoding stuff when im short on time.

print ("Hello World") # prints hello world

Being obsessed with the theme of the editor/ide.

Leaving TODO comments in code

Believing that I don't need to write tests because my code is bug free. 😐

I am always pulling before pushing... a door.

"I don't need to comment this, I'll remember it"

"I'll fix this later"

As a freelancer, I outsource every bit of work to other countries with cheaper labor and charge the client like a rollercoaster

Upgrade on Friday 😬

Relying on Chrome to remember all my passwords. I have no idea any more what passwords I have chosen for several important sites. Don't even want to think about what happens the day I switch PC or reset that cache somehow.

Pushing code to production without testing

"That piece of code sucks...I will fix that tomorrow."

Calling it done when it really isn't.

"Okay sales guy, please keep in mind, this is just a PoC. Do not sell it yet." ...and it is sold.

To convert an int number to a string I do this:-

String s=10+"";

It finally works but it's not pretty... Ah screw it... *commit*

Me with bae

Coding without listening music

*This* is the project I'm actually going to write unit tests for...

Handle all exceptions with
catch(Exception ex)

Same password for everything 😂 I am glad I am not protecting the missile launching codes

Overengineering.

!important
!important
!important
!important
!important

Everywhere.

I comment my code. Thats considered a bad practice between some coders

Deploying something to production without testing it first because it "should" work.

bug report arrives
10 mins later
the issue couldn't reproduced, done 👍

The continuum classy spaghetti code.

Use profanity labelled variables... like the $penis I just used in my code... (makes coding fun, until u get "undefined variable: cannot find $penis on line 31")

Use Windows

Debugging code on the production server with nano #iTooLoveToLiveDangerously

Premature optimization. 🙊

Write comments only I understand

I use variable names so bad that even i forget what they mean

Not cleaning before committing.
You'll probably see lots of /*unused codes*/ in my projects.

- git commit -m "well described comment explaining addition"

oh crap forgot to take out this one thing

- ctrl-S
- git commit -m "ahskdbejjeebdosjeb"

I never comment my code

StackOverflow everything

Copy-pasting code from StackOverflow and hoping that it works straight away

Add random console.logs which end up filling the console on Production

Inline css when feeling effing lazy

.btn {
background-color: red !important
}

When I doubt..

Testing live cause you're to lazy to set up your test environment.. 😂

Reinventing the wheel.

try{

}catch(Exception e){
//do nothing
}

I never touch my code if anyone else have made changes in them without asking me.

I cry like a bitch when I get home.

Console.log("after");

Start using MVC. Put all logic in the View out of laziness.

*Swiches on the PC and opens VS*
Probably I should get some coffee.
*1 hour later, with 0 LOC written*
I should probably code now. Umm, I need music, else I might not focus on the code.
*another hour passes by headbanging to led zeppelin and still on 0 LOC progress*
You know what, this wont work. I should eat and will code with a fresh mind..
*has lunch*
I'll code now.. Maybe I should check up on devrant...
*time goes by with 0 LOC at the end of the day.*
I'll do it tomorrow.
*Next Day, repeats what I did on the earlier day*

Writing in a language I barely know cause clients requirements...

@DeclaringVariablesWithNamesThatAreProbablyTooLong

Staying up late programming (even if I have to work in the morning on a programming job).

Use hard-coded string literals instead of using string resources in Android projects.

z-index: 9999999 !important;

I use an MVC based framework mostly aaaand I'm very fucking lazy sometimes soooo I just run the db functions in the view very often yeah just because lazy really 😄

Nothing a good { left: 10px } can't fix

I use "x" and 'x' interchangeably in the same JavaScript file

Installing a linux distro without purchasing a product key

console.log for debug

Git commits with messages like `bug fixed`, `feature added` etc

Actually wrote an assembly function for a C++ program.
😵

Not adding spaces in for statements.

ex) bad practice
for (i=0;i<10:i++)
{
//some code
}

ex) good practice
for (i = 0; i < 10; i++)
{
//some code
}

I skip writing unit tests. YOLO.

Deploying to production with ssh and git pull on a screen session.

inline css !important

When I come back after a week :
Git commit -a -m "changed a lot, no idea of what I changed"

plaintext passwords
🙈

git add -A
git commit -m "fix bunch of shit.'
git push origin master
**98 files changed

hours later
me: omg I forgot to change the hardcoded IP now it's getting 404

git add -A
git commit --amend
git push origin master --force

My worst bad practice:

Saving my Linux Root SSH Keys on a Cloud Storage company.

Have them there, so I wont loose them ever. I password protected them, but you never know what the NSA/FBI/CIA can do 😉

Who needs comments? The variable "tempList" is self-explaining

Overthinking

git push origin master --force

var self = this;

Test the same thing, in multiple places.

naming variables like this:
$a, $b, $b1, $_b

1) Continue helping people after helping too much
2) Getting into online pissing contests
3) Writing lists

Always push to master...

Not using any framework because there are too many.

Forced to make web apps made for IE and edge...

Minimal comments, no tests, push to Master branch... *Cough* though, this is all for personal projects, not team projects.

1- Copy/Paste (code)
1- Googling before trying to fix a bugs by myself first.
1- Never finish my side projects.
2- (Worst) Still doing all the above.

Using Windows

Save file as: djshddus

I wonder how I've found my files.

Several actually

- root DB access on production
- git commit -am "Stuff" (message)
- Not doing backups
- Using personal licensed software for company work
- 1 commit per day or weekend
- Taking work to home

Complex code with no comments. Like I give a fuck

Tagging every commit as a new release.

!important

Opening a new file for notes and keeping it open without saving. I will just add things to it until it's HUGE. Then i have to go through it...

In a meeting with customers to agree on the scope of a new project...

Me: "Hey, we could do this awesome thing that will save you a lot of time that nobody's brought up or mentioned and will take us an extra 4 weeks to implement."

Horrible, but it's my way of training my PMs to leave me out of meetings.

Used a goto statement once, never felt more ashamed

Forgetting to put .DS_store in my .gitignore file so half my repositories are full of them....

deploy new version on the last 5 minutes in office

Premature optimization

I forget to commit changes when I get something working. Then regret it when I monumentally screw something up and have nothing to fall back on

git push --force

Because I always push after every commit, when the slightest fuckup happens I just hard reset, commit again, and force push...

...even if it's just a typo in the commit message

Spend way too much time crafting email responses, littered with subtle sarcasm and hints at their total incompetence with a gentle push in to what they should be focusing on, instead of sending ridiculous half baked fucking foolish requests.

ssh root@hostname

Forget to git pull before pushing.

Maintaining old code as comments, coz... you never know when that bug in your commented code turns out to be the next big feature.

Copy my private ssh key to multiple machines so I only have to configure one key in github, gitlab, bitbucket etc.

The whole company uses for all test systems and development systems the same password :D

Coding with a shotgun... Like when I'm tired I change a parameter again and again hoping it'll work randomly. I'm a bad person :/

When a ticket comes in I usually jump right on it, get about half way done with it, then either get stuck or it's lunchtime/end of day.

I really should take the gifs advice.

function sum(a, b)
return a + b
end

Working with java 🤓

I don't pay much attention to my local file system when developing-- that's what my operating system and IDE are for. ...So I've thought, at least.

Today, my code didn't compile. I'd been noticing some pesky 'running out of memory' notifications, and mostly brushed them aside. I've spent the last hour deleting various log files and defragging the drive.

Writing

// Refactor this

As I write the code... Never actually refactor it

When the work isn't as interesting as I'd like, sometimes I accomplish the easiest, smallest incremental task and waste time the rest of the day.

I guess because it feels like work, I'd rather apply minimal effort. It's a bad habit, and one I'm trying to break.

Mixing tabs and spaces on collabs with my friends

System.out.println() to debug

Commit and push to live site without testing on Friday and being super confident about it.

And the payment system stop working on the weekend

@ to hide warnings in PHP.

Using post-it notes for todo lists and never look back at them.

testing in production

Naming variables x z y . And of course my all time favourite xx.🤐

Using inline css

Using the waterfall model

Use different indentations in same program.
for(.....) {

}

if
{
}
else
{
}

void doSomething
{
}

static{

}

I have to stick to one convention anyhow soon.. :/

Not using getters and setters and accesing variables publicly.

License code under creative commons. Only sometimes though (I mainly use GPL)

No comment

Eating caveman diet, not doing caveman hunt.

All classes (with a few exceptions) have nothing but static methods just so that I can call them like "Class::Method()" from anywhere in the project...

Not using php composer because I don't know what hocus pocus that thing does.

I refuse to write test scripts to tickets I fix.

Using PHP

position: relative;

!important

I use clearfixes.

git commit --amend --no-edit
git push -f

Copy and paste similar code where I have to change X values but ALWAYS mange to only change X-1 values so i get weird behaviour start debugging what in the end then takes longer than to write it new in the first place. Hate myself for that.

No comments...

//TODO: Write a really awesome rant that people relate to and upvote many times

Using white theme

And loving it

On a server with a couple websites I help out with, I have 'sudo su' in my bashrc.

Ignoring JIRA notifications

Todos in code sitting there in personal projects forever

Visual studio - not naming controls

No documentation, even if it's for personal private projects.

I still can't wrap my head around code I made 2 years ago...

Trying to make everything a one-liner. In the process overusing ternary operators, comma operators, short circuiting and/or operators.

Until someone else needs to review or understand what I created, and I'm forced to change... 😥

Not working at a software company.

Agreeing to everything during a long, boring meeting and finally realizing that you just agreed to rebuilding the entire great wall of china within span of 3 weeks

Working with calculator(Core 2 Duo) after using 4th gen i7....
.
.

Oh just forgot to tell...
Calculator had windows 10 with no search working.

Worst day...
From Multitasking to ↣ ..…

Click dismiss on the backup reminder

Test code only after writing the entire class

Giving an unrealistic timeline for a project. Got reprimanded a few times because of this. Oh and my procrastination habits do not help..at all.

$ python
>>> class Object:
>>> pass
>>> self = Object()
>>> self.attr = val...
>>> * copy paste code from some class
<Ctrl>+d
Testing ☑️

I get stoned to program most times.

I quite often run untested scripts on production systems or hot fix JavaScript files on live using Emacs...

Comments? Ain't nobody got time for those

git push -f --all origin

ShortDeadlines + BadUserRequirements + DumbClients = ForcingMeToUseFuckingWordpress

I use spaces instead of tabs. Working beside me, my mates were irritated of that beautiful sound(they called it noise) from my keyboard.

According to people here, ternary operators. I don't care what I'm doing, if I can use a ternary operator instead of an if, get ready for it!
I guess implicit brackets on conditionals and for loops if it's a single line. Anything that saves me typing boilerplate, but it's still readable, I'm gonna do it.

C#: inner classes, inner classes everywhere
C++: inline and C everywhere

ignoring a broken unit test suite. although ive just convinced the tech lead to let is look into getting it working again.

overflow:hidden;

I save all my work relate passwords in a single text file on my computer. I always have it open too.

Too many systems, too many password requirements, expires too frequently.

!important in CSS and not commenting complex algorithms in c#

Print debugging everything

My biggest bad habit (for now!) is rushing changes. I have no real deadlines, yet I rush commits and cause failures in our CI tool every week

I am very enjoying wk47. Having a naughty smile everytime. 😅

Two things actually bad I do :
* Put some printing lines everywhere to debug, and then, debug.

* A syntax than can be pretty bad if not handled properly :

if (your test)
do_something();

I actually always put a tabulation to see the hierarchy and break lines, which is not optimized AT ALL but help me to read, and I hope helps other to read too.
But that's a bad habit tho if you have bad presentation of your code (which I don't have, given how people compliments my code presentation)

// TODO
// FIXME

Having these everywhere...

Listen how i shoud do my work from clients who can't download they're own photos from Facebook.

I make too much files for my C programs

Fixed bug x
Fixed bug y created by bugfix for x
Revert before bugfix x

var a, i, bc, mc

I'm too lazy to set up a proper code review from a branch. Instead, I just make dozens of quickly obsolete tags. I should probably learn to use subversion better, but... ¯\_(ツ)_/¯

still using windows forms w/ c# for desktop programs.

Not commenting my code just to return 2 weeks later to wonder what kind of special asshole wrote the code. And what the heck it does.

Stating the obvious when writing comments. 🙈

I used to this when I was starting to learn how to code and let someone read it, 'cause it's better to have comments than nothing, right? 😂 I was wrong.

But that led me to improve writing informative comments and self-documenting codes.