3 ms·

"There's a time and a place to dig in your heels and say NO to something. It usually comes when someone else has been reckless. If you do it for everything, the

"There's a time and a place to dig in your heels and say NO to something. It usually comes when someone else has been reckless. If you do it for everything, then either you're the problem, or you're surrounded by recklessness. I think you can figure out what to do then." The magic is in telling the difference.

__blockcipher__ 7y ago
Wasn’t her implicit point that you wouldn’t need to know which it is, because the answer to both (“you’re the problem” vs widespread recklessness) is to leave?
- azernik 7y ago
  In the former case, the answer is to change your own behavior. The sentence structure is a bit confusing, but I interpreted that last clause as referring only to the latter case (surrounded by recklessness).
  - HarryHirsch 7y ago
    From her other posts on her blog, it's clear that she means that her managers consider her a problem because when she predicts trouble she is usually right. When you continuously play Cassandra it gets tiring for everyone involved, Cassandra, her manager and the audience viewing the spectacle. Time to find a new job.
    - marcinzm 7y ago
      The flip question is always, how often was Cassandra wrong? We're after all seeing one side here. A perfect Cassandra is potentially useful, a trigger happy Cassandra is just annoying. Even a perfect Cassandra can be annoying if the issues in the end cause minimal monetary fallout.
opless 7y ago
There is a rule of thumb to not ship anything on a Friday. This was a Sunday! And it didn’t seem to have been tested, so where was the Dev/UAT/Prod separation? So many red flags, and I think anyone who has been in development for a while has had some product owner try to break procedures to force whatever pet project that is falling behind to hit some target to get their bonus/gain brownie points. It almost never goes well. But by this time the PO has a scapegoat because it’s no longer their fault it’s not working, it’s production’s fault. (Also it’s not always a PO, it can be a developer or anyone up to c-suite level) Sigh
- K0SM0S 7y ago
  “No but you don't get it, my son is really good at those things, he said he would speed up our Windows machines 10x if I gave him the codes and physical access to the servers during weekends!” That would be a very bad, very cliche joke if it weren't a true war story (2005, good times). Turns out the 15 y.o. had convinced his father that I was "lame" at my job because I didn't tweak regedit. Important lessons were learned by the three of us that day!
  - opless 7y ago
    I actually laughed.
  - ineedasername 7y ago
    Sounds like a "Dude, do you even regedit Bro?"

__blockcipher__ 7y ago

Wasn’t her implicit point that you wouldn’t need to know which it is, because the answer to both (“you’re the problem” vs widespread recklessness) is to leave?

azernik 7y ago
In the former case, the answer is to change your own behavior. The sentence structure is a bit confusing, but I interpreted that last clause as referring only to the latter case (surrounded by recklessness).
- HarryHirsch 7y ago
  From her other posts on her blog, it's clear that she means that her managers consider her a problem because when she predicts trouble she is usually right. When you continuously play Cassandra it gets tiring for everyone involved, Cassandra, her manager and the audience viewing the spectacle. Time to find a new job.
  - marcinzm 7y ago
    The flip question is always, how often was Cassandra wrong? We're after all seeing one side here. A perfect Cassandra is potentially useful, a trigger happy Cassandra is just annoying. Even a perfect Cassandra can be annoying if the issues in the end cause minimal monetary fallout.

opless 7y ago

There is a rule of thumb to not ship anything on a Friday. This was a Sunday! And it didn’t seem to have been tested, so where was the Dev/UAT/Prod separation? So many red flags, and I think anyone who has been in development for a while has had some product owner try to break procedures to force whatever pet project that is falling behind to hit some target to get their bonus/gain brownie points. It almost never goes well. But by this time the PO has a scapegoat because it’s no longer their fault it’s not working, it’s production’s fault. (Also it’s not always a PO, it can be a developer or anyone up to c-suite level) Sigh

K0SM0S 7y ago
“No but you don't get it, my son is really good at those things, he said he would speed up our Windows machines 10x if I gave him the codes and physical access to the servers during weekends!” That would be a very bad, very cliche joke if it weren't a true war story (2005, good times). Turns out the 15 y.o. had convinced his father that I was "lame" at my job because I didn't tweak regedit. Important lessons were learned by the three of us that day!
- opless 7y ago
  I actually laughed.
- ineedasername 7y ago
  Sounds like a "Dude, do you even regedit Bro?"