Details
Joined devRant on 2/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
-
There is no reason for any developer to not know git well. No fucking reason. Stop making shit harder for everyone by being like “oh I’m not the keenest on git” STFU and just learn it better you pussy.28
-
I don’t know if I would call it a quirk of the language or serious abuse of it :P
But I managed to get a null ref exception when comparing a local int variable to an int parameter to the same function in C#.
Since a local or parameter of type in cannot be null and I compared the variables them self and dud not try to access any property on them (and no extension method or implicit case or similar) my first thought, along with all colleagues that chipped in to help, was that this should not be possible.
Turns out the method was called through reflection and in that part it injected null as the base object to call the method on.
Since local variables actually are referenced through the parent object this was what was causing the null ref.
That took some time to figure out.4 -
Error reporting. Yeah it is a pain to come up with something that users will understand. As devs we need meaningful stacktraces so we can diagnose the problem but the normal person doesn't care. Also not having consistent messages looks terrible for the user's experience.
I hate it when there is no standardized error messages and/or json structure between teams or individual members of said teams. Why should we have 10+ different structures to code for in our apps? There is RFC 7807 for a reason. It has a defined structure plus accounts for custom properties. If you are a c# developer, check out the ProblemDetails class. It has made my life easier and I can guarantee everyone that all of my team's projects return this structure. -
I'm getting really tired of those dumbass programmers that do not understand shit and then come to me when production breaks. (I am also a programmer, not really a DevOps engineer, but I'm the least worst at DevOps stuff, so it's my job...).
We're programming some kind of document management tool. Today we had a release, and one of the new features is to download all of your documents as a zip file, which is asynchronuously generated. When it's done, the user gets a mail with the download link to the zip file.
The feature works basically, but today it broke our production service, as somebody was running a test of it.
Turns out all the documents are loaded into memory to be zipped. So if you have 2 gigs of documents, a container with memory restrictions in that area will crash.
I asked the programmer who reported this «ops problem» to me, why he didn't just shit the files into a temp foler in order to zip them in there.
He told me that he wanted to do so, but did not know how to mock this for a unit test, and therefore went to the in-memory «solution», which was easier for him to mock.
For fuck's sake, unit tests and mocks are fucking tools, not ends in itself! I don't give a fuck about your pointless mocking code when the application crashes!
When I got to deal with such dumbasses, I'd prefer to mock those motherfuckers with a leaky bucket of liquid shit, which basically accomplishes the same task from my perspective: dripping shit all over the place and make everything suck as fuck.3 -
Most annoying part of frontend application development is testing 😐 Any others have a same problem as me?6
-
Fuck me. I just posted a huge post on StackOverflow with images and huge puddles of code everywhere because I had been stuck since yesterday and five FUCKING minutes after asking, I read the code on the website (Pretending to be an outsider solving my own problem) and find the FUCKING TYPO.11
-
I just noticed programmers can cite Shakespeare in 1 character.
"To be or not to be..." = 2b|!2b = true = 17 -
Some empty-headed helpdesk girl skipped into our office yesterday afternoon, despite the big scary warning signs glued to the door.
"Hey, when I log in on my phone, the menu is looking weird"
"Uh... look at my beard"
"What"
"Just look at this beard!"
"Uh.... OK"
"Does this look like a perfectly groomed beard"
"Uh... it's pretty nice I guess"
"You don't have to lie"
She looks puzzled: "OK... maybe it could use a little trimming. Uh... a lot of trimming". "I still like it though" she adds, trying hard to be polite.
"I understand you just started working here. But the beard... the beard should make it clear. See the office opposite to this one?"
"Yeah"
"Perfectly groomed ginger beards. It's all stylish shawls and smiles and spinach smoothies. Those people are known as frontend developers, they care about pixels and menus. Now look at my beard. It is dark and wild, it has some gray stress hairs, and if you take a deep breath it smells like dust and cognac mixed with the tears caused by failed deploys. Nothing personal, but I don't give a fuck what a menu looks like on your phone."
She looked around, and noticed the other 2 tired looking guys with unshaven hobo chins. To her credit, she pointed at the woman in the corner: "What about her, she doesn't seem to have a beard"
Yulia, 1.9m long muscled database admin from Ukraine, lets out a heavy sigh. "I do not know you well enough yet to show you where I grow my unkempt graying hairs... . Now get lost divchyna."
Helpdesk girl leaves the scene.
Joanna, machine learning dev, walks in: "I saw a confused blonde lost in the hallway, did you give her the beard speech?"
"Yeah" -- couldn't hold back a giggle -- "haha now she'll come to you"
Joanna: "No I already took care of it"
"How?"
"She started about some stupid menu, so I just told her to smell my cup". Joanna, functional alcoholic, is holding her 4pm Irish coffee. "I think this living up to our stereotype tactic is working, because the girl laughed and nodded like she understood, and ran off to the design department"
Me: "I do miss shaving though"68 -
Just interviewed a guy with ~8 years of experience:
Me: *Asked him to write a simple algo logic on a paper*
Him: I don't do much of algo design. I'm much of a design patterns and software design guy.
Me: How would you design a singleton class in Java?
Him: *writes a sloppy code*
Me: Hey, thanks for your time. Our HR will get back to you with further updates.
Moral: Interviews can be very short when the candidate doesn't code.15 -
If Microsoft bought GitHub to increase the amazing open source projects it has already been doing ( typescript and vs code) then I am all for it. This isn't your father's Microsoft and people seem to be missing that lately. Their contribution to open source software has been incredible the last few years and I'm excited to see how they grow that with the acquition.2
-
If Gordon Ramsay made code reviews, I would watch that show. Especially the insults he would use for handling clients.
"This code has so much spaghetti, it decided to open it's own restaurant"23 -
Child: Dad, why does the sun rise in the east and set in the west?
Dad: Son, it's working, don't touch it.5 -
I have what seems to be an unpopular opinion about buying software as a software developer.
First off, I support open source all the way. There should always be free and open tools for people to use if the need or want to.
Second, if you underpaid, broke, unemployed, or a student then this doesn’t apply to you. You keep pushing forward!
With that said, let’s get to the meat of it all...
I pay for good software. Even when it is expensive. Even when there are “workable” free or open source solutions.
I do this for a number of reasons...
1. They are better, hands down.
(Tower > GitKraken, SourceTree, GitHub Desktop) (Kalidascope > every other diff tool) (JetBrains IDEs > Atom, Brackets ...)
2. I’m no longer a broke student. I make enough money to buy them.
3. Most important: I’m a fucking professional software developer, not a fucking joker.
- If I was a carpenter then I could always hammer nails with the back of my work boot. It’s free and paid for and will do the job. Instead I would buy a good hammer because I’d be a professional and not a fucking joker complaining about the price of the tools to do my job.
4. I use a Mac, sometimes Linux and NEVER Windows. Which means I have a platform that actually has useful apps built for developers who are willing to pay for it.
5. I don’t get caught up in developer circle jerks about how all development software should be open source and free.
————
So there you go.
Does this offend you?
Good!
Come at me bro23