Details
-
SkillsJava, groovy, SQL, impatience
Joined devRant on 3/29/2017
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
-
Is it weird that whenever a slightly dodgy site asks for my address, I give the address of the prime minister:
10 Downing Street
Westminster, London
SW1A 1AA, UK8 -
Just got a Raspberry Pi3 as a gift and I have no idea what I should do with it. Also I didn't knew about Raspberry Pi3 until now. So maybe someone can help with some ideas. :)22
-
Me: so, ifconfig, what is my gateway?
ifconfig: [ip address]
Me: nmap, what is this IP address?
nmap: it's a network switch with an open telnet port.
Me: what happens if I connect to it?
switch: WHAT IS THE PASSWORD?!?!
Me: is it blank?
switch: correct. what do you want to do?
Me: can I look at all the IP and MAC addresses on the network?
switch: WHAT IS THE ADMIN PASSWORD?!?!
Me: is it... admin?
switch: correct. Here's everyone that's connected to the network: [400+ IPs and MACs]
Me: ok python, would you filter through these and tell me what manufacturer each one belongs to?
python: sure.
[~50 manufacturer lookups later]
python: there's a bunch of apple product, a bunch of miscellaneous laptop and printer manufacturers, and some raspberry pis.
Me: raspberry pis?
python: yep. about 20 of them.
Me: What happens if I connect to one?
rpi: WHAT IS THE PASSWORD?!?!
Me: raspberry?
rpi: correct. what do you want to do?
Me: can I make you do my bidding in the background when you aren't being used?
rpi: sure, sounds fine.
I love ignorant sysadmins.8 -
When I know a website runs Hotjar or some other screen recording/mouse tracking tools I draw at least one dick per visit.7
-
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.32 -
The only one rule that governs the entire programmers world: If I work as you want, I'll choose the price. If you choose the price, I'll work as I want.12
-
I just started playing around with machine learning in Python today. It's so fucking amazing, man!
All the concepts that come up when you search for tutorials on YouTube (you know, neural networks, SVM, Linear/Logic regression and all that fun stuff) seem overwhelming at first. I must admit, it took me more than 5 hours just to get everything set up the way it should be but, the end result was so satisfying when it finally worked (after ~100 errors).
If any of you guys want to start, I suggest visiting these YouTube channels:
- https://youtube.com/channel/...
- http://youtube.com/playlist/...9 -
HAHAHAHAHAHAHAHA
SOMEONE WAS HAVING A CONVERSATION WITH ME AND I TOLD THEM I'M A DEVELOPER
THEY ASKED IF I HAD A GIRLFRIEND
HAHAHAHAHAHA
.
.
.
.
of course I do devs are the coolests10 -
Every single time I visit my family during holidays they expect one to fix their computer/smartphone/printer/whateverFuckingShittyIOT-Device... Just printed them postcards this time ¯\_(ツ)_/¯
Also: Hello devRant! Just been reading here for a week and every single day was full of gold - Thanks :)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 -
"Privacy reminder: This website uses cookies, and if you delete them, you'll have to click away this reminder again and again."6