12
mahaDev
6y

Just now... Got a job to create patch files for a couple of jars, which may or may not have varying class files. In total, I have to decompile, check, add and synchronize about 30 class files in 6 jars with a new functionality (that I didn't write). 🙂

FUCK PRODUCTION! WHY CANT YOU MAINTAIN ONE MOTHERFUCKING JAR?

OH? YOU'RE SUPERSTITIOUS THAT ONE TINY, ANT-SHIT SIZED CHANGE IN ONE SIMPLE FUNCTIONALITY WILL FUCK UP *OUR* PRODUCT?

FUCK MANAGEMENT! YOU DON'T HAVE CONFIDENCE IN YOUR *OWN* PRODUCT!

OH? CUSTOMER COMES FIRST? HAVE THE BALLS TO DEFEND YOUR OWN FUCKING SELF AND PRODUCT TO THE CLIENT OR THEY'RE GONNA MAKE YOU YOUR BITCH AND TIE A GAGBALL DIPPED IN HOT SAUCE AROUND YOUR MOUTH! HOW.. THE FUCK.. DID YOU MISS THAT LOGIC??????

Best part, they want it by tomorrow, and they don't wanna test it. Guess who's gonna get slaughtered after a week? ME! 🙂

Comments
  • 2
    Decompose and recompose compilables for prod? Yikes
  • 0
    That blows. Sounds like you need version control, and a build process even if it's just a shell script or an oldschool makefile.
  • 0
    @d4ng3r0u5 lul, we have like 5 branches in SVN running for that one production site, one with a functionality or two each. And whenever we have to add a new functionality, "create a new branch, it's okay", said everyone. Because everyone needs a handy backup.

    We are in the process of moving to Git, but it's slow and tedious because there are a lot of change requests open at the moment.
  • 0
    Why would you need to manually patch the production jars? shouldn't they be build from the source with the modifications needed in place?
  • 1
    @cgomezmendez ideally, that's what's supposed to happen, but when there are 6 jars with different changes in each (they're all out of sync with each other, don't ask.) And the changes need to remain the same. In addition, whatever additions are to be made need to be made on top of that.

    Basically, the site is just fucked up. Gives more headache than revenue.
Add Comment