Web API: "Oh, I see that you're trying to update to our new design with a category and sub-category dropdown layout. Here's one api endpoint that provides you the whole table without fucking input parameters to filter per category and sub-category. Goodluck! And Have fun filtering through the json and sub-json response!

And btw, don't even bother asking me to update the endpoint. Cause admin already said that the UI SHOULD ADJUST TO THE API AND NOT THE OTHER WAY AROUND. AS THE APIs ARE HARDER TO REVISE"

It's not our fault your api design is crap. You piece of shits.

FUCK!!! FUCK IT ALL. FUCK YOU AND YOUR CRAPPY BULLSHT UNDOCUMENTED AND OUTDATED API.

YOUR DATABASE SERVER BACK-END HAS TO BE THE ONE MANAGING THE DISPLAY DATA FOR ITS WEB AND MOBILE CLIENTS. NOT THE OTHER WAY AROUND, DAMN IT.

I'M NOT GONNA SIT HERE ALL DAY HARD-CODING ALL YOUR SERVER'S INADEQUACY.

MAKES ME WONDER DO YOU EVER USE DESIGN PATTERNS OR APPLY DESIGN PRINCIPLES? DRY AT LEAST? DON'T FUCKING REPEAT YOURSELF, DAMN IT.

I CAN'T WAIT TO LEAVE THIS PLACE FOR GOOD.

Reporter: We are now here reporting live from the native mobile app wilderness. As you can see in our captured footage, a developer is going rampage over some mobile UI components.

Native iOS: grrrr... I hate radio buttons!!!..grrr...dropdown lists, too! keep them away from me! I'm allergic to android and web controls, d*mn it! what kind of designer are you!?!

Reporter: That's it for today's devRant episode. Back to you, Steve.

smh.

Why hire a Native iOS Developer when you're going to let him develop an iOS app to look EXACTLY like its Android counterpart?

There's hybrid and cordova for that if you want your apps to look and feel exactly the same.

Can't we all just agree to appreciate the distinct differences in UI for both platforms? Navigation especially? Copy context not UI.

The next time you see developers wearing headphones, please understand that it's our most polite of saying:

"I'm in the freaking 'zone'. Don't you dare disturb my rhythm in coding and lose my momentum. Now unless it's reaaally that important, leave it in our group chat/email and I'll read it later."

Tap gently. We're at overdrive when we headbang to music while coding.

Boss: We need this update deployed and propagated before end of day.

Web: done!
Android: done!
iOS:...
Boss: what's the matter?
iOS: 2-3 business days, sir.

Apple and its app review process. Ugh!

It could either turn out really well or most of the day will be wasted on setting up one's development environment

Is storing-of-data-in-classes-as-static-variables-to-access-them-later-on-from-one-page-to-another a good practice? It always seemed fishy to me...