7

I worked on a project that used an archaic homegrown library written by a consultant that had zero documentation, tons of reflection and here is the kicker... the consultant refused to give us the source code as it was "his intellectual property" so we couldn't make any sense of how to actually use it. Moreover, he worked remotely so the timezone difference between us meant that any questions we had took ages to get answered. Glad to be away from that project now.

Comments
  • 2
    I'd say you take off and nuke the whole thing from orbit. That's the only way to be sure.
  • 2
    Next time best to have a contract clearly defining who owns the code.
  • 0
    @benhongh I wish... it was a brown field project ( we too are consultants) and that proprietary library was already being heavily relied on in production. Moreover, it wasn't covered by any tests so nuking it was not an option...
  • 1
    @Jumpshot44 of only it was under our control. The client basically hired a bunch of independent consultants that didn't really work well together...
Add Comment