Details
Joined devRant on 10/10/2018
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
-
Allright, this one begs for a rant.
Me (Linux boi):
0 checkout code
1 update local config file
2 compile
3 deploy locally
4 run
5 use
Coleague (Windows boi):
0 checkout code
1 update local config file
2 compile
3 deploy locally
4 run
-1 "configuration xyz not found in config file"
→ goto #3
After 4 attempts:
ø windows.reboot()
3 deploy locally
4 run
-1 "configuration xyz not found in config file"
3 deploy locally
4 run
5 use
// out of curiosity...
3 deploy locally
4 run
-1 "configuration xyz not found in config file"
NO side actions taken (no configs updated, no code changes made, no nothing. Just simple double-clicking the redeploy script again and again)
Now... How do you objectively explain THAT?
http://weknowmemes.com/2013/01/... IRL :)8 -
Fuck yeah!
6 monitors are success-fucking-fully running on my setup.
Fun detail is that WITH the official AMD driver, one screen wasn't turning on and one had a weird resolution but WITHOUT it, it works completely fine!
Yes, it runs completely fine on Linux (Kubuntu).
Finally have my dream setup.42 -
My phone is my most reliable computer. It made it to 2000 hours of uptime before I restarted it to update.
Props to Android.6 -
Software engineering is doomed.
The next generation of developers is going to suck as fuck
I've come across a lot of situation that made me think this way.
The most notable examples are right here on devrant.
I've seen a shit ton of rants blaming languages for "bugs" when in fact those "bugs" wouldn't have happened if those fuckers would have read the specifications of said languages.
This new generation doesn't read, when they've got a problem they just fucking go to Google for answers, they don't bother reading specifications, language books, rfc, etc, they don't bother reading where the true source of information are. The documentation ? What's that ? Let's go to stackoverflow first, let's think second.
Same back in school I've seen people in the highest grades that couldn't fucking decompress a tar archive.
In the coming decades we will loose the high skilled people, the people that made the software world as it is today we will be left with fuckers only able to blame things for stuff they don't understand.
This is my first true rant. This is me being pissed off.27 -
I see software engineering mostly devolving to be simpler syntax, more widespread and reach more range of people, including non-tech ones.
That’s now obviously leading to more crappy javascript code, more abandoned frameworks, libraries, more shitty software and more dev rants.5 -
Started being a Teaching Assistant for Intro to Programming at the uni I study at a while ago and, although it's not entirely my piece of cake, here are some "highlights":
* students were asked to use functions, so someone was ingenious (laughed my ass off for this one):
def all_lines(input):
all_lines =input
return all_lines
* "you need to use functions" part 2
*moves the whole code from main to a function*
* for Math-related coding assignments, someone was always reading the input as a string and parsing it, instead of reading it as numbers, and was incredibly surprised that he can do the latter "I always thought you can't read numbers! Technology has gone so far!"
* for an assignment requiring a class with 3 private variables, someone actually declared each variable needed as a vector and was handling all these 3 vectors as 3D matrices
* because the lecturer specified that the length of the program does not matter, as long as it does its job and is well-written, someone wrote a 100-lines program on one single line
* someone was spamming me with emails to tell me that the grade I gave them was unfair (on the reason that it was directly crashing when run), because it was running on their machine (they included pictures), but was not running on mine, because "my Python version was expired". They sent at least 20 emails in less than 2h
* "But if it works, why do I still have to make it look better and more understandable?"
* "can't we assume the input is always going to be correct? Who'd want to type in garbage?"
* *writes 10 if-statements that could be basically replaced by one for-loop*
"okay, here, you can use a for-loop"
*writes the for loop, includes all the if-statements from before, one for each of the 10 values the for-loop variable gets*
* this picture
N.B.: depending on how many others I remember, I may include them in the comments afterwards19 -
I need to make a confession. I wrote shell scripts that will automatically turn on my system and will download games and movies for me after office hours, using office internet10