Details
-
AboutI am Jamie. As per usual...
-
SkillsC#/.NET, Java and a lot of other things...
-
LocationUK
Joined devRant on 8/9/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Customer is always right.....
Committed to sustainable productivity..
Misunderstanding between the IT Department Staff member and the Finance Department Staff member in one of the establishments...
User: Hi, our printer is not working.
IT Service: What is wrong with it?
User: The mouse is jammed.
IT Service: Mouse? Are you sure it’s a printer, as they don’t come with a mouse?
User: Do you think I’m stupid? I’m telling you it’s the printer!
IT Service: I'm telling you, it can’t be the printer! They don’t have a mouse!
User: Oh really?... Mmmmm... I’ll send you a picture.
Scroll down...
. . . . .. .
. . . . . .
. . . . .
. . . .
. . .
. .
.
.
.
The customer is always right.
Listen to him/her and believe what he/she says.
Don’t jump into conclusions!
12 -
Happy international cat day, everybody!
And a nice day to every sysadmin out there, hopefully not too catty.
4 -
Me : "Hey, I can't find the comments.js file, do you know where it is stored?"
Co-worker : "Yep, look in the CSS folder"
Me : "OK, thanks!"
5 seconds later..
Me : "Wait, what?"8 -
Interviewer: What is your native language?
Me: Lisp
Interviewer: The programming language?
Me: Yeth4 -
Aardwolf is very fun and i suggest y'all play it a bit if you're looking for better ways to slack off at work
$ telnet aardwolf.org 4000
*port 23 also works
23 -
Base10 is interesting.
Did you know that any number > 9 has this weird thing where if you sub it's digits from the number over and over, it'll eventually become 9?
For example: 35
35 - 3 - 5 = 27
27 - 2 - 7 = 18
27 - 1 - 8 = 9
Try it with any number you like.41 -
Fuck today was weird.
Today I received almost half a million on my bank account. 😯
Someone changed the ancient cryptic billing system. My user account at work has id 32 in the database, and the dev referenced the size of the creditor id instead of the of the value of the ids itself, and they're u32 ints... So ALL the money moving through our platform was accidentally transferred to my associated bank account.
For all the unit tests we have, this bug tumbled right through.
And no one at finances thought a transfer that big, to a backend dev they know by name, was suspicious — with almost no money going to other creditors...
That worries me a bit. The fact that this shit can happen, even at high test coverage, just because someone mindlessly did a wrong autocomplete or something.
Of course I will send it back... after two weeks and a few hundred € of interest.12 -
GF: What are you doing there?
Dev: I've been trying to reproduce a bug for two hours now...
GF: You need two bugs the opposite sex, otherwise they won't reproduce.
From a sad true story.8 -
When you copy some code and select the code you want to get replaced and accidentally press Ctrl+c again so you have to copy the thing you wanted to copy again 😡12
-
If Doctors Were Like Coders
(cross-posted from https://medium.com/@c09b6133a238/...)
Problem: The patient has a broken leg.
Solution:
1. Ask the patient to reproduce the exact scenario that resulted in the broken leg. Watch closely to see if the leg breaks again. Check for consistency by repeating the scenario a few more times.
2. Explain that this isn’t an intended use case for the leg, and besides, it only affects one person. Ask the patient if, all things considered, he really wants to prioritize his broken leg over your other work.
3. Point out that the patient’s other leg performs just fine under the same circumstances. Ask if he can use his other leg instead, at least as a workaround.
4. Attach several accelerometers to the broken leg and break it again. Stare at the data received from the accelerometers, then shrug and declare it useless.
5. Decide that the patient’s problem must be in his spleen. After all, that’s the only part of his body you don’t really understand.
6. Track down the people who created the patient. Ask them if he’s ever had spleen problems before. When they seem confused, explain that he has a broken leg. Ignore them when they tell you that the spleen they created could not possibly cause a broken leg.
7. Ask Google where a person’s spleen is. Spend half an hour reading the Wikipedia article on Splenomegaly.
8. Open the patient and grumble about how tightly-coupled his spleen and circulatory system are. Examine the spleen’s outer surface to see if there are any obvious problems. Inform him that several of his organs are very old and he should consider replacing them with something more modern.
9. Compare the spleen to some pictures of spleens online. If anything looks different, try to make it look the same.
10. Remove the spleen completely. See if the patient’s leg is still broken. If so, put the spleen back in.
11. Tell the patient that you’ve noticed his body is made almost entirely out of cellular tissue, whereas most bodies these days are made out of cardboard. Explain that cardboard is a lot easier for beginners to understand, it’s more forgiving of newbie mistakes, and it’s the tissue franca of the Internet. Ask if he’d like you to rebuild his body with cardboard. It will take you longer, but then his body would be future-proof and dead simple. He could probably even fix it himself the next time it breaks.
12. Spend some time exploring the lymph nodes in the patient’s abdominal cavity. Accidentally discover that if the patient’s leg is held immobile for six weeks, it gets better.
13. Charge the patient for six weeks of work.14



















