News for hackers. Stuff that matters.
Re:The health care toll today’s work culture exacts on emplo... by badpun on Friday March 23, 2018 @07:42AM (#16656975)
> Epic fail. Always be honest and direct with people. If there is some policy preventing the most direct and appropriate answer then don't respond at all. People are generally good at discerning when you are tap-dancing or spinning your wheels (cowardly bullshit).

I'm doing that in my current company and I feel it will get me fired (which I don't mind that much). When asked why my development tasks are taking so long, I'm honestly pointing out the myriad of architecture/design and infrastructure/CI/CD fuckups I have to spend time dealing with every day (I work in a major bank). Of course, people responsible for setting up things this way are still running things, and don't want to hear about consequences of their previous decisions.

Re:The health care toll today’s work culture exacts on emplo... by austincheney on Friday March 23, 2018 @07:56AM (#16657060)
I remember hearing this when I was at Travelocity. "uggghhh, they are being a bottleneck". The easiest solution to this is to vocalize and advocate for best practices. If doing that crushes a project timeline then make the product owner or project manager accountable for defying product quality in email. The old "I want that in writing".

If the product is crap in production everybody will be harmed, but at least you might have a get out of jail card. When I have pulled this in the past it serves as a forcing function for decision makers to revisit their poorly conceived decisions. For some reason it is so much easier to make bad decisions and order the consequences of such across an organization than it is to simply own it.