We were running an obfuscator as part of our build pipeline, but also were not. I discovered we had disabled every rule, and after asking around it turns out that the obfuscator broke the app (because of reflection and things I won't go into).

So I turned it off.

An hour later the CTO came to me and said to put it back. "We have to obfuscate, put it back."

"But... it wasn't doing anything, other than slowing the build down."

"I don't care, we HAVE to run obfuscation. It's in our contract with the client."


  • 2
    How much does it actually add though? Also what language?
  • 5
    And do they tell the client you are using transparent obfuscation?
  • 1
    that's fucked up!
  • 3
    If running obfusctor that doesn't do anything fulfills the contract AND if you're paid to wait for it every time you build... Time for chair jousting!!
  • 0
    @alexbrooklyn it added about two minutes, and it's C#
Your Job Suck?
Get a Better Job
Add Comment