Android : devRant is consuming too much power in background
Me : Say what ??
A : I said devRant is consuming too much pow.................
M : Who the fuck told you to rant about it
*Turns the phone off

No one speaks ill of devRant and lives long enough to tell about it.

The horrendous act of having the skills to develop but have a full time job. Knowing you could make 10 x more developing.. 😐

Debugging code:

The bugs have learned to hide

Hell yeah linux

The floor is java

She asked to tell her a joke.
"My life...", said I.
"Error 404, joke not found..." replied she.
She is also a developer.

Yes, that's how you do it...

When you hit rock bottom :/

~nixCraft

Me: I'm gonna be productive today. Will complete this task in one hour!
*starts coding enthusiastically*
After two minutes...
*facebook*
*cat video*
Awwwww
*dog video*
Lol heheh!
*cute kittens n puppies*
Heh, silly cat
*more cats, dogs*
*accidentally notices the time*
Crap! 1.5 hours gone waste....

I just added this to the commit log:

Stray apostrophe.
Like a splinter in my mind.
Now has been removed.

Well you better look again, bitch!

Boss: Are you almost done with that project?
Me: *closing Google search of "dogs in top hats"* I need more time

Just tried to use CTRL+Z to go to the previous page in Chrome

Chrome developer tools, without it I wouldn't be able to see all the errors generated by my awesome programmer skillz

Dev: this task is done, can I put it in review and do something else?

Me: sure, of course.

Dev: cool, just be aware I'll make some changes to it later.

Me: ... wait, then it's not done.

Dev: no it is, I just need to re-read it and make some changes.

Me: yeah, so it will be done when those changes are made.

Dev: but I don't know what those changes are.

Me: ... I get that ... but ... ok I'm extremely confused. Why do you think it's done.

Dev: because I've written everything I need to and I'm happy with it.

Me: ok so why do you want to make changes.

Dev: I don't.

Me: ... ... ... ... you ... you are really not being clear. If you don't want to make changes, and you are happy with it, why are you planning on making changes later ... after marking the task as done.

Dev: well if I re-read it and see something I don't like, I would like to change it.

Me: ok, so re-read it as many times as you like and make as many changes as you like. But don't mark it as done until it is done.

Dev: but it is done.

Me: no it's not.

Dev: it is, look.

Me: ... yeah looks ok at a quick glance.

Dev: ok so I can mark it as done?

Me: are you going to make more changes?

Dev: yes.

Me: then no.

Dev: why?

Me: BECAUSE ITS NOT DONE.

Dev: ok maybe I'm not explaining it clearly.

Me: ... we can both agree on that. Ok so to summarise, we don't mark something as done until we have stopped touching it. We don't half finish something and say it's done and comeback to it later. We mark it as done when we are happy with i.....

Dev: but I am happ.....

Me: *raises hand* I repeat, if it's done, we lock it away and stop touching it. If someone reads it and complains, we can come back to it with a new ticket. But it's not done until we think we are ready to send it on.

Dev: I am ready to send it, I just may want to change it.

Me: ... ... ... ... ... due to a new policy implemented just now, we are only allowed to send 1 email to a person each week. So unfortunately we can only send on 1 copy. So when you have that 1 copy, let me know.

Dev: ok, let me re-read it a few more times then.

Me: there you go.

I think I just hit my lowest point.

Spent ALL of last week trying to get my WAMP server to call a PHP script via AJAX and I kept getting 404s. Spent at least 10 hours on stack overflow trying to figure out why the server wasn't accessing it only to find out today that I was both looking at the wrong directory and also working the file name wrong.

I think I just need to walk away from programming for a while... 😧

Push your commits before anyone else, so you don't have to resolve any merge conflicts 😈