Joined devRant on 4/12/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Getting along with colleagues who think and act like their skills in pretty much everything are way better than mine, despite - Surprise - they aren't.
Took me a quite long time to learn ignoring that.
Suffix parameters with _, so you can distinguish them from the attributes.
I wonder what IDE the person who has given me that advice uses...
App of a little social network I'm member of didn't connect to the server anymore, since the social network changed their SSL-certification and my smartphone is too dumb to accept the new one.
So, I pulled the source code of the app from GitHub and added some code dealing with SSL-connection-exception-handling.
A warning appears, that there were some errors with the SSL-cert with the question how to proceed and three options:
Quit, Ignore for now, Ignore and don't ask me again.
The code to ignore ssl-errors is just for debug-/develop-purposes, but hey, app with that little "hack" is running only on my phone x)
Now, the app is working again at my smartphone \o/2
Update to my last rant*:
I got to know what my colleague did as he "rewrote" my code:
He just searched some GitHub-Projects and used the good old copy+paste method.
Awesome bro, "rewriting" code until nobody's understanding it is the best method to improve code.
Colleague says some of my code sucks, says he's gonna rewrite and improve it.
After he finish his work, I look in his new written code:
F*ckload of unused methods and classes,
some usings of deprecated API calls...
god. It's okay, if you want to help and improve code (my code wasn't the best, I admit)... but when you do, do it the fuck right.
- Dealing only with your own code
- Having enough time to improve and refactor your code whenever you want
- Bug reports are detailed af and not just like "doesn't work"
- Choosing the IDE (and OS maybe, too) by yourself
- Having enough time for bugfixes, implementations
- Software is ready, when you want it, not anyone else.
- Visiting trainings or seminars to improve your skills whenever you want
Yeah, that would be pretty awesome.3
Search the company on Facebook, the internet, to see some pictures of the offices at an usual workday.
Don't come too overdressed to a job interview, if the employees all wear casual clothes.4
Neighbours asked me to help them setting up their new printer.
Bug: Installation of the driver fails.
Fix: The printer has to be turned on during installation.
I earned 20 bucks for this single press of only one button.
First-Level-Support in the neighbourhood: Annoying but pays like hell.3
Helped an elderly neighbour to fix his landline connection, since it broke down.
Somewhat an emergency, cause he don't have a mobile phone.
It seems, this got around and another neighbour asked if I could plug in his new printer and install the drivers.
Gosh, RTFM and don't buy hardware you can't handle.
No, I won't fix your computer.
BlueJ for Java and the IDLE for Python.
No big difference to coding in NotePad.
Just don't understand, why IDEs for learning purposes are that feature-less.
"Hey, you want to learn to code in that specifc language? It would be a shame, if you have to do almost anything by yourself."4
feature xyz doesn't work.
Spent hours trying to find the bug causing the malfunction, couldn't reproduce it on my devices.
Called to the customer to have a look on his device.
Feature xyz works as intended, the only bug: Too less patience at Layer 8.
Device just needs a little moment to establish a connection.
Patience is a virtue.
Being able to understand and get along with almost any grafical user interface at once without reading manuals, due to knowing the intentions of the UX-designers.
Family and friends are stunned everytime, when they don't know how to do something on programs they don't know, while I often need just a few clicks to archieve it, even if I'm using the program for the first time
I was searching for a good answer about a problem I got. Found an existing thread on stack overflow.
Many answers, all of them upvoted but not working.
One answer being not upvoted was working.
Wanted to upvote it, signed up to stack overflow.
"you can not upvote. too less reputation."
GOD, DAMN IT.2