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
Search - "aaaaaaaaaaaaaaaaaaaaaaaaa"
-
Managers: Fullstackclown!!!! When are those features we poorly designed and spec'd going to be released to production!?!?!??!!
Juniors: WE SO DUMB DUMB REEEEEEEEEE HELP FULLSTACKCLOWN!!!!! WE PRODUCE GARBAGE CODE THAT TAKES MORE OF YOUR TIME!!!!!!!!
Designers: Hur dur, how can I export this stuff to png, help us, Fullstackclown!!!
Fullstackclown: * inhales sharply * AAAAAAAAAAAAAAAAAAAAAAAAA7 -
Fuck. Medium.
Fuck all the articles on it too.
Do you seriously think I am so fucking dumb that I cannot keep my attention on a paragraph of text without at least one image for five seconds straight?
Three quarters of your shitty fucking article are images. They don't even relate to a damn thing in the article. It's just a fucking stream of random image subtitles.
It's just as bad as people randomly mashing pictures they found via Google search into their Power Point presentation because they actually have no content, breaking all copyright laws in the process, so they can stretch their mindless bullshit as long as humanly possible.
FUCK. YOU.6 -
I spent 2 hours last night trying to figure out how to rotate an image in Java without clipping it. I was all in with a pencil and paper sketching everything out to make sure my math was right.
Turns out I was calculating the new image size correctly, but I used to wrong variables to define the new dimensions...
Sigh. -
Me at 2:00 AM be like:
“WHY THE **FOOK** IS THIS CONSTRAINT BREAKING???”
“WHY IS XCODE SUCH A PIECE OF SHIT?”
“BROKE THE PROJECT FILES... HERE WE FUCKING GO AGAIN.”
“MEMORY ERRORS? H O W”23 -
Old story, happened some way back. I worked part-time for a small web development company that did between other things something called SharePoint development, basically .net webforms with shit glitter on top of it.
The most weird part of it, was the fact that we were working on vms that hosted the app, it was our dev, test and staging environment, as well as were we showed the client the polished turd.
Did I say that it was on a vm? Well it was on a remote vm, that each of use had access to it, through our domain accounts, and they couldn't configure the windows server to accept more than two or three users at once to be connected.
That was our test enviroment and dev enviroment, sooo showing the app to the client meant for the rest of us to not write any code because it might crash or get stuck.
The app was accessible and discoverable by url and through google search from outside, I dont think that should have been allowed.
The most disastrous part was that we had NO source versioning whatsoever, just plain old copy and paste in different folders.
Deploying to client meant remoting to the clients host or whatever it was, and manually copying the source files
If someone wanted to debug the application you had to shout, and you also could hear it, in the office: "I'm debugging!" or "I'm deploying!". Because we were on the same machine, there was only one process with the server and it meant that if you debug or deployed it would block it for the others.
Should I talk about code quality? Maybe not.1 -
This is it, today I am getting one of my wisdom teeth removed. Wish me luck! Also, if I’m talking here, I just wanna say: I am officially moving away from SwiftUI and switching to UIKit. I’ve been constantly building my way around SwiftUI, constantly bypassing SwiftUI and adding UIKit layers around it. It has been such a headache using SwiftUI to construct such complicated views and I figured that the pace of development has been rapidly declining due to SwiftUI. I am going to rewrite the whole app again but in UIKit (it’s still native).
(Also, Floyd, sorry for the mistag again. :P)6 -
At work we've been having problems with printers... Like anyone that has to deal with printers.
They kept disappearing and reappearing for users on every log on.
We got a support contact with Microsoft because it was group policy doing it.
Their final solution (after weeks of remote sessions and long phone calls) is to install pstools on every machine, and run about 7 commands as the system user to delete and then re add registry keys.
ON EVERY LOG ON AND LOG OFF. WTF...
This is an educational institution where "computer hacking" is taught... It's not gonna take long before someone realises that pstools is installed...rant printersareevil microsoft printers group policy aaaaaaaaaaaaaaaaaaaaaaaaa kill me now please windows group policies are useless1