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
-
Grumpy cat was in a lot of our internal products, on loading screens and what not, because why not? PM got pissed and said if he sees that fucking cat again blah blah blah. Grumpy cat is now summoned with a Konami code. Grumpy cat will never die.2
-
Much obliged if you stop reloading the folder and searching it every five fucking seconds you fucking cunts.
Good god damn this fucking 'feature' of windows 10 grinds my fucking gears. I hit 'x' to stop seeing the visual distraction of the fucking green loading bar when the folders already loaded. Same thing with music. All I want it to do is open and play my fucking song.
Does it do that?
No instead it spends precious cycles updating fucking indexes or sprinkling crack rocks on the corpse of my cpu or whatever cycle fairies at fucking microsoft programmed it to do while wasting my fucking time.
I wish I had a brick and a microsoft programmer within throwing distance, I'd be sorely tempted to nail the motherfucker square in his fucking big fat melon.
Cunts.
fuck count: 8
6 -
Few years ago as a junior android dev with couple years of self taught experience of working in startups I submitted a simple android app assignment for a junior android dev role. Assignment had only like 8 requirements so I followed them to the letter. That didn't end well.
App was simple just 3 screens. Login screen with username and password input fields, login button.
Had to call a login endpoint after login button was clicked, redirecting to home screen, calling items endpoint, displaying a list of items and when an item was clicked passing item data and redirect to item details screen.
Needless to say big swinging dick senior was not impressed. UI was not perfect, I forgot to display a loading animation when fetching data, didnt handle back button properly.
I agreed with some points but other comments were clearly just nitpicking: his preferred variable naming conventions, his opinions on architecture that was not up to his standard (official google arch at the time was not up to his standard).
He also was mad that app wasn't prepared for release to googleplay (another out of the ass requirement). Like I would prepare a 3 screen app for prod release that he will forget ever existed after 20min of his review.
Lots more of nitpicking, encapsulation this encapsulation that, omg now hes shocked that there are a few warnings after the project is built.
Regardless my self confidence was destroyed at that point and after few more negative experiences I dropped android dev alltogether for a couple years and switched to game dev.
After game dev ran its course I went back to android dev and found a supportive place where I could grow.
Looking back, they were actually hiring atleast a mid level for a junior position but I was grilled as a senior. The guy literally didnt wrote any single positive thing in that review about my code even tho my senior peers said my project was decent back then, its just that I didnt handle a few edge cases and that's all.
I looked up the guy in linkedin, turns out hes a uni dropout who posts all books that he red about software dev in his education section of his linkedin profile. Found a bunch of other narcissistic stuff on his profile. Guy was a fucking idiot. Even if I worked under him it would have probably sucked.
Learned some important lessons I guess. Always get a second, 3rd and 4th opinion and dont take criticism too seriously. Always check what kind of person is providing feedback.4 -
When I just started programming I aways added fake loading screens and hard-coded login screens to my c# applications because it looked cool..
But I also always added an invisible panel to the top right so whenever you click that it would bypass the login screen.
I had to do that because 1. I will forget that password after 2 seconds, 2. I got no time for that login screen.2 -
To all of you:
Nobody enjoys loading screens. Just because the UI reacts on things, doesn't mean that the actual job gets fucking done.
So instead of using some shitty progressbar you copied from a dev who copied it from a 90's textbook, show some cat images.
The fucking internet is full of it and if your shitty Hello World app that is wasting 300MB of my RAM is dieing in the middle of some loading process, you could at least ease my pain.
Please. Show cat images instead of a progressbar. Thank you ❤️8 -
I fucking love Asynchronous Action creators in Redux.
I little more work upfront makes for a well thought out application and makes things like loading screens stupid simple. -
in my previous company , we used to create 4 custom ui states for just 1 screen in android app, and we would have task to create 3-4 new feature screens in 1 sprint (of 14 days) the states would be :
empty state : a state where data is not available. usually consisted of message, a graphic and some action button
data state : the usual state where data is filled on various elements
loading : a shimmer ui showing loading. it was supposed to be pixel perfect to that of the data state. it was basically a different xml, but with grey colored views instead of colorful. the tricky part would usually he to create the dynamic views
error/no connection state : as most of the screens couldbget api error or no internet error, this would be the screen for asking user to retry connection
all of these screens combined with their ui in xmls + kotlin code with barely any stuff being reusable , made the life incredibly difficult. however a lot of our customers would appreciate the interactivity of our app
doing these stuff again nd again , i had become trained to do all those 3-4 (x4) screens and the whole ui stuff in first 4 days of the sprint. but now i am in a company where i am getting passed on to managers after managers and getting tasks to change documentation in 1 week, i find those coding stuff incredibly tough.
gotta get back to shape -
I hate application launchers.
When i start an application, i WANT IT TO START. What i don’t want is your bullshit, custom, logo and splash screen infested piece of shit launcher to start up, with the only option of loading a project or file up, or worse than that, when the only option is to start the fucking application, which should have already happened.
Also, splash screens. Fuck your 5second branded splash screen when your cocksucking application has the fucking loading footprint of MS Notepad.2 -
There have been a few :)
If say it's a videos utter project I initially though was good. Apart from loading a view the controllers didn't do anything - my initial thought was some magic was happening behind the scenes.
However, when I opened up the view things changed.
ALL the business logic happened in the view. Everything. Form processing, consuming an app, file uploads, validation, crud ... You name it, it happened in view. The developer created a raw MySQL connection and build his queries by concatenation g strings, the whole system was wide open to sql injection.
Even more annoying was the "source control" he invented. Every file had several copies. I.e. "User(working).php", "user_v3.php" and even "user(working_no_profile_fields_1.php". It wasn't even like there was any consistency in what file was actually used either. A complete mess. The system had around 69 screens too. No idea how the developer got that gig.2 -
Ubuntu 20.4 is not very cool.
It might look "polished" in some (barely noticeable) areas , which doesn't matter to me as i already used better themes and icon packs. Moreover they tried make ui and icons flwt which looks terrible. It feels like to ubuntu's designers , flat= every icon in a dark gray color. Am not a fan of black topbar either, the old darkish looked much better
The worst thing is that now i have to go through multiple start screens since my laptop is dualboot :/ .
Its now like : black screen > (hp+ubuntu logo) + grub > (hp) > (hp+ubuntu logo + loading icon) > lockscreen > my system
Earlier it was just hp> grub>lockscreen>my system. The fast start up was one of my favourite features of Ubuntu, now its a million loading screens. The lockscreen is cool tho6 -
There was this one time when we've managed to upload a Debug build to Google Play Store.
On the same day we had to create a new build w/ fixes, have the testers perform smoke tests, then switch to some fairly quick overall tests.
If nothing were to come up during those tests, the build was supposed to be passed over to the submission manager for release.
Things weren't going that smoothly in the beginning, w/ the first two builds being broken in one way or another.
Finally, however, we managed to create a properly working build.
QA hadn't had that much time to test it, but no major problems were identified && given the deadline we had to submit it.
The next workday it turned out that the tester responsible for passing the approved build over to the submission manager gave him the Debug build.
The submission manager none the wiser uploaded that build for release.
Result?
The users who managed to update their game got their save data wiped... sort of.
It looked that way given the Debug build was communicating w/ a different server.
In the aftermath of that situation, we had to repair the damage && upload the correct build as quickly as possible.
Also, ever since then a huge text 'DEBUG' was added to the loading screens of Debug builds to make people very aware of which build they were looking at.
As for any repercussions for the tester responsible for the mess, or the submission manager - I have no idea.
They were both still working there, so at the very least none of them got fired because of this.
Top Tags
Weekly Rant
View