I work in a dev company. One of our clients hired us to help them out as their devs are failing with their deadlines.

I had to expose app services via an api. I did it. Client company devs didn't like the way I did it as I rewrote their datamodels and declared them as api-use-only. I was demanded to return bkend services' data structures.

I didn't agree and waited until deadline to submit my code.

Now they are honestly thanking me for what I did as I've saved them from a forever-mutating-api-and-angry-integration-customers hell.

Not sure whether should I be happy or worried. I forced my solution onto them. It's not proffessional. But yhe customer is happier now than it would've been.

What do you do in such situations?

  • 4

    Both have elements of right and wrong so I honestly can't say. I guess it depends on personality? Whether you want the client to be happy in the short term but unhappy in the long term, or the other way around. I recall that Louis Rossmann for example also prefers long term customer happiness on the whole topic of "repairing" broken chips by putting the motherboard/graphics card/whatever in an oven (which doesn't reflow the solder balls at all). Generally I quite like the idea of short pain for long term happiness.
  • 3
    I would first try to understand what I am doing in that company. If your job is to help the team get a few deadlines than what you did is the way to go.

    If your job is to teach them how to reach deadlines your way is the one thing you should not do. In that case I would analyze the team. See if it is the whole team thinking this or if it is just one or two people thinking they know it best. Depending on that it changes what the best way to act is.
  • 1
  • 2
    @Codex404 I was there only as an additional set of hands to help out with the workload. I know I did that part well. But I doubt whether I did it the right way.

    @Condor I like that thinking! It makes me look better :)

    BTW the oven trick did work (at least on my GPU). Although temporarely.. I used it witn my Pavilion dv6k
  • 0
    @netikras how long did it last after that? I've heard that it's usually about a month or so. So yeah it does work somewhat when you're in a dilly of a pickle, for the time period it takes to get something else.. but apparently it only causes the die to become a bit more malleable so that a junction here or there in the chip can (temporarily) reconnect.
  • 4
    Honestly a lot of people need best practices shoved down their throat by force. If that’s what it takes then fucking do it. It’s worth the short term bitching to get the long term benefits. Though make sure you have the political capital to back up those sorts of changes. Sure it might be better if everyone held hands and sang songs together but sometimes you just have to get shit done. The one caveat I think would be to ensure you have support of management and that your changes are following best practices and contributing towards long term business profit/success. So long as you can demonstrate that your changes are going to have a net positive impact on the business bottom line you’re in the right in most cases.
Add Comment