• L (unregistered)

    spotted TRWTF:

    We didn't have time ..., so instead we spent six months

  • linepro (unregistered)

    I can up the last one.

    I worked for an exchange systems company that provided the trading, clearing and delivery systems for a derivatives exchange. I went on honeymoon to Malaysia with everything ticking along nicely, naïvely booking the thing with the company travel agent for a 15% employee discount.

    Things went pear shaped while I was away and returned to the hotel after a day out to find a fax requesting that I cut the honeymoon short and travel to Tokyo leaving my newly we behind.

    Needless to say I sent a return fax (on their dollar) politely declining.

  • (nodebb) in reply to L

    Most likely it was a "quick" fix taking just as long as a proper fix would take.

    I'm sure anyone in the industry has seen it. Something that should only take a week or two taking months.

  • Darren (unregistered) in reply to miquelfire

    It's more likely the situation where a 'temporary' fix is put in place - 'just to tide us over for now' - with the intention to do something 'proper' in the future. As we all know, temporary is the most permanent word in the world and these sticky-plaster fixes end up hanging around for years because they work and no-one sees any value in putting in the time and effort to replace it.

    I've got a 'temporary' monitoring solution I wrote that's coming up to it's third birthday, and I foresee it being around for ever as there's nothing else which will replicate the very specific requirements. The suppliers (plural) of the two pieces of software it's monitoring have shown zero interest in fixing - or even admitting the existence of - the underlying issues.

  • (nodebb)

    What is this “unpaid weekend work” thingy. Never heard of it before.

  • Leverage (unregistered)

    It seems common that one customer will pony up the cash and then try to rake in 10x the purchase.

  • Officer Johnny Holzkopf (unregistered)

    The passage "they actually called to tell me this while I was on vacation the week after my wedding" just sounds wrong: How is it possible for work to call you when you're obviously on vacation? Is the idea of "work phone (number)" vs. "my phone (number)" still a strange concept? If you take a call from work, that's work-time, and you should be compensated for the loss of you-time (or we-time in this context), and it also should be in your contract, otherwise the calling party should risk a heavy fine... that would be mighty fine!

  • Daniel Orner (github) in reply to Officer Johnny Holzkopf

    In a previous job, I once legimitately got a call on my personal phone while I was on my honeymoon. Wasn't even super urgent, something related to my performance eval. Was really annoyed.

  • (nodebb) in reply to Officer Johnny Holzkopf

    Depends on the country I guess.

    Here in Australia, we only just implemented the whole 'Right to disconnect' thing. As good as our great country is for a lot of things (fair work, work safety, health, etc...), that was one thing we didn't have.

    Which meant your employer could call you (even on your personal number) and request something of you, of course you could ignore the phone, or say you didn't want to do what they wanted, but then they were able to do things like pass you over for promotion, disciplinary action, fire you, etc...

    A lot of it also ended up unpaid.

  • (nodebb) in reply to bjolling

    This is a company where the client just cost the company a weekend of software development hours and the employees had to pay it.

    It won't appear on any company budget, won't affect the bottom line in an obvious way and unless somebody is logging their own hours, nobody will ever know.

    Unpaid overtime is something I cannot shove down the throats of people who say "owners take on all the risk" far enough.

Leave a comment on “Whales Ahoy!”

Log In or post as a guest

Replying to comment #699163:

Log Out

« Return to Article