Boolean Logic....

Linux pople be like

When ransomeware guys provide better customer support than most companies 😂

The real story: How the Apple was damaged.

A sys admin in his natural environment.

Next thing you know, you're getting an email from your oven about it's updated privacy policy.

Oh my god... Storytime.

A customer comes in with I assume is his father or grandfather.

Customer: I need a computer, but without all the internals

Me: So a case?

Customer: Yes, I need a Dell computer outsides, but without the internal components.

Me: Well, we don't have Dell cases, but we sell custom build cases and they come with a power supply.

Customer: *says nothing, but looks interested*

Me: *walks over to the cases to show him* So this is what the cases look like and we have two types, one for a ATX and one for a micro-ATX.

Customer: *still says nothing, but looks at them*

Me: What motherboard do you have at the moment?

Customer: Well, I don't have anything right now, but I'm replacing another computer that didn't work very well. I'm going to be getting some Dell parts to put in here.

Me: O-okay. So this other computer, I'd like to see it in shop to see what's going on with it.

Customer: Oh, you do NOT want to do that. I hooked it up to another computer and it blew it up.

Me: Huh, that's weird. I'd still like to look at it if possible.

Customer: Oh no, it's all wired wrong and... *some bullshit, but stay with me*

Customer: I am the best at technology. My hand has computer parts in it--government funded. *some more bullshit*

Me: Okay... *I try to bring it back around* Well, I'd still like to see the other computer for myself. So you don't have parts for this new build yet, right? You don't know what type of motherboard you have?

Customer: No.

Me: Well, I would get the internals first, so you know what size of case to get, and then get the case.

Customer: Okay. Thank you for your time.

He shook my hand with his "cyborg" hand and I was tempted to say something about "try not to crush my hand," but elected not to. Also during this entire exchange, the old man continuously farted in the background.

BF: If you were a database, I would join with you.
Me: Left or right?
BF: Inner.

(there are no words)

Apple has Air
Amazon has Fire
Google has Earth
Microsoft should really create something called Water

Why don't keyboards sleep? Because they have two shifts HUEHUEHUE

Don't ever try writing code on a long flight. People LOSE THEIR SHIT.

Client tests the app and provides feedback ... This sucks! Full of bugs, hard to navigate, nothing works!

1 week later after version 2 client provides new feedback: This rocks! Love it. Easy to use and rock solid!

Changes made: background set to light blue.

Just taking the temperature - how many people would be interested in a devRant podcast? We'd probably start with it being every other week.

It would feature things like inside devRant updates, guest interviews, rant readings, and anything else fun we could think of.

Any thoughts?

Who else has the ctrl+s reflex... I do it on everything 😐

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.

Some guy my girlfriend knows, heard I'm a software developer. He had this 'great' idea on how he wanted to start a new revolutionary way of paying on the internet. He wanted to create a service like paypal but without having the hassle of logging in first and going through a transaction. He wanted a literal "buy now" button on every major webshop on the internet. When I asked him how he thought that would work legally and security wise, he became a bit defensive and implied that since I'm the tech guy I should work out that kind of stuff. When the software was ready, he would have clients lined up for the service and his work would start.

I politely declined this great opportunity

This is way too true.

We've all been there

I promise this is my last GDPR rant..

Our team just got the best email from our client hahaha