Details
-
AboutInformatic Student
-
SkillsJava, Kotlin, C, SQL, Python
Joined devRant on 11/10/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
-
LEARN THE FUCKING WORDS!
I know that English isn't the native language of my country, but for fucks sake, if I'm telling you the right way to say/write it, remember it!
It's called ROM not ROOM
It's called Mod not Mood
Am I good with Custom ROM's? Yeah
Am I good with Custom Rooms? No, I'm not a fucking interior designer
Am I enjoying Moto Mods? Of course
Am I enjoying Moto Moods? Vruum Vruum bitch.16 -
Oh shit. I found something better. Had to delete previous rant.
Google Assistant is actually being cheeky!27 -
Sure I've said this before, but I was once asked to embed a video in a pdf so people could print it...9
-
Rule 34 ½: For every programming problem, there is already related XKCD, StackOverflow question and indian guy explaining it on YouTube. <323
-
" If you can put an axe through it, it's hardware; if you want to put an axe through it, it's software. " -- Unknown7
-
Q: How to catch an Elephant in the Africa
MATHEMATICIANS: hunt elephants by going to Africa, throwing out everything that is not an elephant, and catching one of whatever is left.
EXPERIENCED MATHEMATICIANS: will attempt to prove the existence of at least one unique elephant before proceeding to step 1 as a subordinate exercise.
PROFESSORS OF MATHEMATICS: will prove the existence of at least one unique elephant and then leave the detection and capture of an actual elephant as an exercise for their graduate students.
COMPUTER SCIENTISTS: hunt elephants by exercising Algorithm A:
1. Go to Africa.
2. Start at the Cape of Good Hope.
3. Work northward in an orderly manner, traversing the continent alternately east and west.
4. During each traverse pass,
1. Catch each animal seen.
2. Compare each animal caught to a known elephant.
3. Stop when a match is detected.
EXPERIENCED COMPUTER PROGRAMMERS: modify Algorithm A by placing a known elephant in Cairo to ensure that the algorithm will terminate.
ASSEMBLY LANGUAGE PROGRAMMERS: prefer to execute Algorithm A on their hands and knees.
ENGINEERS: hunt elephants by going to Africa, catching gray animals at random, and stopping when any one of them weighs within plus or minus 15 percent of any previously observed elephant.
ECONOMISTS: don't hunt elephants, but they believe that if elephants are paid enough, they will hunt themselves.
STATISTICIANS: hunt the first animal they see N times and call it an elephant.
CONSULTANTS: don't hunt elephants, and many have never hunted anything at all, but they can be hired by the hour to advise those people who do.
OPERATIONS RESEARCH CONSULTANTS: can also measure the correlation of hat size and bullet color to the efficiency of elephant-hunting strategies, if someone else will only identify the elephants.
POLITICIANS: don't hunt elephants, but they will share the elephants you catch with the people who voted for them.
LAWYERS: don't hunt elephants, but they do follow the herds around arguing about who owns the droppings.
SOFTWARE LAWYERS: will claim that they own an entire herd based on the look and feel of one dropping.
VICE PRESIDENTS OF ENGINEERING, RESEARCH, AND DEVELOPMENT: try hard to hunt elephants, but their staffs are designed to prevent it. When the vice president does get to hunt elephants, the staff will try to ensure that all possible elephants are completely prehunted before the vice president sees them. If the vice president does happen to see a elephant, the staff will:
1. compliment the vice president's keen eyesight and
2. enlarge itself to prevent any recurrence.
SENIOR MANAGERS: set broad elephant-hunting policy based on the assumption that elephants are just like field mice, but with deeper voices.
QUALITY ASSURANCE INSPECTORS: ignore the elephants and look for mistakes the other hunters made when they were packing the jeep.
SALES PEOPLE: don't hunt elephants but spend their time selling elephants they haven't caught, for delivery two days before the season opens.
SOFTWARE SALES PEOPLE: ship the first thing they catch and write up an invoice for an elephant.
HARDWARE SALES PEOPLE: catch rabbits, paint them gray, and sell them as desktop elephants.9 -
So I wanted to send an email to Microsoft to request a feature in their new "To-Do" app.
I went to the play store and scrolled down to the end where it says "Send an email to developer".
Clicked on that. And here is the email address:
"noreply@microsoft.com"
😑 😑13 -
Senior dev : * doesn't use git *
Me: you seriously should use git...
Senior dev: * still doesn't use git *
Senior dev: * overwrites production files with old files from other computer *
Senior dev: * talks to boss *
Boss: * gets angry at me *11 -
Use SSDs.
It's not hard. They've been around for a while, small ones are cheap now and are more than enough for at least 90% of developers. The rest can probably afford 2TB NVMe.
Why waste 60$ on a worthless 500GB HDD that will load the OS in the time that's enough for you to make scrambled eggs?
Instead, use 60$ on a 128GB SSD. Sure, it's smaller, but if speed is important for you, you can forget a bit about saving all of the porn you see online, or about installing every free game from Steam.
SSDs are cheap already. And the performance advantage they give is ENORMOUS. You can have a core i9, 64GB of fastest RAM bla bla bla, but if you don't have an SSD, a Celeron with an SSD will seem faster.
Get one, and NEVER again cry about long loading times of IDEs, unless you feel like 30 seconds for the longest load time is too much. If your time is THAT valuable, then you can afford NVMe SSDs in RAID 10 (which can be done easily in software with btrfs if you're on Linux).
Seriously!
Every day I see posts like "Visual Studio is crap because it installs for 6 hours", or "Android studio starts in 30 minutes", or "Visual Studio Code sucks because it loads for too long compared to vim".
It's as if you only have access to budget 10 year old computers.27