Trait aar!

//TODO: Laugh

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 used to tell people I write JS but actually I just write Jquery.

I wanted to buy all these at a car boot sale (yard sale). But I've got no idea why...

Trying to make a basic api, i now have a head ache. Thanks php

While you're reading this,81739292749201738382 JavaScript frameworks and libraries were written!

When your 3G is faster than your WiFi...

I hired a coder to write a WordPress plugin on my dev server. He no longer works for me and is unreachable. The plugin does most of what it needs to do. But when I dig into the code and the database to find what should be obvious bits of code that do obvious things? None of that code is found. Not even with a recursive directory keyword search for that should be easy to find like CSS class names and IDs. Even the data that comes from the database and that I see on the screen is not actually present in the database!!! Yet it all works. I'm pretty sure at this point the code and data reside in a parallel dimension only the coder can get to. How do I debug code that doesn't actually exist?!

Am I the only one that found this funny?

My wife wants to name our son "Jason". I suggested "JSON" but she didn't respond code 200. She's a doctor. :-/

One of the many things my non-programmer friends needs to learn!

Every single day.

Pro Tip: if you're building a developer REST API, don't forget to add a sample response to each endpoint. I don't want to have to test each one when I'm building my integration, I'd rather build my model in one go with the documentation displayed on a second monitor.

My CSS code in a nutshell

Admit it,. You most of the time use use 'ls' to test a SSH connection ;)

Unfortunately it's true!!!

while(true) {
googleSomething();
try {
develop();
} catch(Exception e) {
stackOverFlow(e);
}
}

nixcraft being nixcraft.