54

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.

Comments
  • 5
    Do we work at the same place!?!? I feel your pain, exactly how I feel every day.
  • 1
    Man, just give me a fucking hug. I am so tired of this doc shit. We really need a solution for this :(
  • 1
    That why I require the project an Interface Agreement with a mandatory requirement of "use case facilitative" i.e. you can do the whatever the fuck you want to make it modular, and microservice the shit out of your API for all I care, but you need to have the web service end point "screen use case targeted". Have them add a service transformation layer for it e.g. Apigee.
    None of that requirement in place means no project.
  • 1
    Hope this URL works: bit.ly/2mPYK2C
  • 1
    Proper rant is proper! Have an upvote.
  • 0
    Apply proper design principles? Dry at least?? Tell me you fuckers dry??? You just hop out the shower and start getting dressed???? ARE YOU EVEN HUMAN?????
Add Comment