Details
-
AboutGerman Student
-
SkillsHTML, CSS, JS, PHP and learning C++ right now.
-
LocationGermany
Joined devRant on 11/30/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
-
Rant (that's kind of unusual here these days): can you please stop writing "code" as a rant? It's not witty, it's not original, it's not funny anymore, hasn't been since first year of college, it's not impressing anyone here.
I mean... printf("Happy new year\n");... Does anyone find it funny? Couldn't anyone here come up with that?
It only makes you look like you're 17 and trying to make a statement like "look at me, I'm so fluent at pro9ramm1n9, such a 1337!"
/rant7 -
Whenever I come across some acronyms...
CD-ROM: Consumer Device, Rendered Obsolete in Months
PCMCIA: People Can’t Memorize Computer Industry Acronyms
ISDN: It Still Does Nothing
SCSI: System Can’t See It
MIPS: Meaningless Indication of Processor Speed
DOS: Defunct Operating System
WINDOWS: Will Install Needless Data On Whole System
OS/2: Obsolete Soon, Too
PnP: Plug and Pray
APPLE: Arrogance Produces Profit-Losing Entity
IBM: I Blame Microsoft
MICROSOFT: Most Intelligent Customers Realize Our Software Only Fools Teenagers
COBOL: Completely Obsolete Business Oriented Language
LISP: Lots of Insipid and Stupid Parentheses
MACINTOSH: Most Applications Crash; If Not, The Operating System Hangs10 -
Advice that I give to interns/grads:
In uni/college, you're taught *how* to code something to achieve a goal, and 99% of the time the code will work and do the job in a lab.
But when building things for a real production environment, you learn the 100 ways how *not* to code, from seeing things break left right and centre - basically everything and anything can break your code, whether it is users, the OS, other people's code, legacy code, lag, concurrency, the alignment of the moon to your server...5 -
I've been asked to do some investigation at work regarding an IT security incident. Thankfully I've watched plenty of CSI so I'm just working on building a GUI with VB to track the IP...7
-
I've always made this joke, but it happened for real.
There was a existing bug in our machine for a very long time. So long that the validation engineer now treats it as a feature and they raised a issue when the bug was fixed :/7 -
My brother just called me asking for help in some MS server thing and I'm like "I don't know that!" (I really don't), and he replied "Yeah, you know, mom told me to call you to ask for help.". Jesus Christ. Just because I'm in CS it doesn't mean I know everything informatics-related.
I now know your pain, devRanters. I usually don't mind being the IT support (so much that my parents call me to help them when their computers decide to randomly die or do something weird because of something they've done, but I live like 300km away because of uni so I can't just go there and help them. Sometimes I say "Ask your son" (he's taking a tech course in high school), but my brother cuts out of it like "I don't know how to fix it" without even looking at it sometimes. Well duh, me neither at times, but google is your friend damn it. Sometimes I search for the answers. Other times I just poke around in the program until I find what's wrong. Either way, when I say I don't know and/or I can't really do much about it they give me the usual "We're paying your uni fees for what?" (in a joking tone but. I'M NOT STUDYING FOR THAT, I WANNA BE A GAME DEV DAMN IT)), but goddamn it I don't know everything just because I am a CS student. I wanna help but sometimes I can't. Deal with that >:V8 -
Normal people don't understand this concept; they believe that if it ain't broke, don't fix it. Engineers believe that if it ain't broke, it doesn't have enough features yet.
- The Dilbert Principle (1996)1 -
Girl: we need to talk
Me: OK
Girl: you seem to have more time for your computer than me. I want to know how important I am to you.
Me: You are the number 1 in my life.
Girl: *smiles and hugs me*
Me: (thinking)...Just that I start counting from 029 -
my boss bought iphone 7 for testing...inserted his sim card and takes phone with him self all time...2
-
Yesterday: Senior dev messages out a screenshot of someone using an extension method I wrote (he didn’t know I wrote it)..
SeniorDev: “OMG…that has to be the stupidest thing I ever saw.”
Me: “Stupid? Why?”
SeniorDev: “Why are they having to check the value from the database to see if it’s DBNull and if it is, return null. The database value is already null. So stupid.”
Me: “DBNull is not null, it has a value. When you call the .ToString, it returns an empty string.”
SeniorDev: ”No it doesn’t, it returns null.”
<oh no he didn’t….the smack down begins>
Me: “Really? Are you sure?”
SeniorDev: “Yes! And if the developer bothered to write any unit tests, he would have known.”
Me: “Unit tests? Why do you assume there aren’t any unit tests? Did you look?”
<at this moment, couple other devs take off their head phones and turn around>
SeniorDev:”Well…uh…I just assumed there aren’t because this is an obvious use case. If there was a test, it would have failed.”
Me: “Well, let’s take a look..”
<open up the test project…navigate to the specific use case>
Me: “Yep, there it is. DBNull.Value.ToString does not return a Null value.”
SeniorDev: “Huh? Must be a new feature of C#. Anyway, if the developers wrote their code correctly, they wouldn’t have to use those extension methods. It’s a mess.”
<trying really hard not drop the F-Bomb or two>
Me: “Couple of years ago the DBAs changed the data access standard so any nullable values would always default to null. So no empty strings, zeros, negative values to indicate a non-value. Downside was now the developers couldn’t assume the value returned the expected data type. What they ended up writing was a lot of code to check the value if it was DBNull. Lots of variations of ‘if …’ , ternary operators, some creative lamda expressions, which led to unexpected behavior in the user interface. Developers blamed the DBAs, DBAs blamed the developers. Remember, Tom and DBA-Sam almost got into a fist fight over it.”
SeniorDev: “Oh…yea…but that’s a management problem, not a programming problem.”
Me: “Probably, but since the developers starting using the extension methods, bug tickets related to mis-matched data has nearly disappeared. When was the last time you saw DBA-Sam complain about the developers?”
SeniorDev: “I guess not for a while, but it’s still no excuse.”
Me: “Excuse? Excuse for what?”
<couple of awkward seconds of silence>
SeniorDev: “Hey, did you guys see the video of the guy punching the kangaroo? It’s hilarious…here, check this out.. ”
Pin shoulders the mat…1 2 3….I win.6