Mostly cloudy
-
You missed your calling - Director of Public Relations. :laugh:
I don't just ping people - when I'm done, they ring like a freakin bell... :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Well, our transition to the cloud has resulted in diminished access. Before we moved to the cloud, we could still connect to our outward facing database servers via ssms using basically read-only accounts. we could inspect tables/views and even look at stored procs, but we didn't have execute permissions. On our cloud servers, that read-only account has been removed, which everyone thought was fine. Until today. A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases... The word "shitstorm" is being bandied about as a description of what's been happening since i sent that email. In that email, I also happened to mention that I warned this would happen, and was told by the PM that "we'd cross that bridge when we came to it". Here we are, and the bridge is nowhere to be seen, and I am NOT stepping in that fast-moving stream of sewage that I see flowing by. "Shitstorm" indeed.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013#realJSOP wrote:
A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases... The word "shitstorm" is being bandied about as a description of what's been happening since i sent that email. In that email, I also happened to mention that I warned this would happen, and was told by the PM that "we'd cross that bridge when we came to it".
:thumbsup::thumbsup: :laugh: :laugh: I suppose the PM is going to love you from now on :rolleyes:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
#realJSOP wrote:
A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases... The word "shitstorm" is being bandied about as a description of what's been happening since i sent that email. In that email, I also happened to mention that I warned this would happen, and was told by the PM that "we'd cross that bridge when we came to it".
:thumbsup::thumbsup: :laugh: :laugh: I suppose the PM is going to love you from now on :rolleyes:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
#realJSOP wrote:
...I also happened to mention that I warned this would happen...
Nelek wrote:
I suppose the PM is going to love you from now on
Yes, I've also found that people love, love, love it when you give them an "I told you so!" :rolleyes: Most of the time they stop talking to me when I do it and I take that as a compliment and a reward. :laugh:
-
Well, our transition to the cloud has resulted in diminished access. Before we moved to the cloud, we could still connect to our outward facing database servers via ssms using basically read-only accounts. we could inspect tables/views and even look at stored procs, but we didn't have execute permissions. On our cloud servers, that read-only account has been removed, which everyone thought was fine. Until today. A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases... The word "shitstorm" is being bandied about as a description of what's been happening since i sent that email. In that email, I also happened to mention that I warned this would happen, and was told by the PM that "we'd cross that bridge when we came to it". Here we are, and the bridge is nowhere to be seen, and I am NOT stepping in that fast-moving stream of sewage that I see flowing by. "Shitstorm" indeed.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Well, our transition to the cloud has resulted in diminished access. Before we moved to the cloud, we could still connect to our outward facing database servers via ssms using basically read-only accounts. we could inspect tables/views and even look at stored procs, but we didn't have execute permissions. On our cloud servers, that read-only account has been removed, which everyone thought was fine. Until today. A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases... The word "shitstorm" is being bandied about as a description of what's been happening since i sent that email. In that email, I also happened to mention that I warned this would happen, and was told by the PM that "we'd cross that bridge when we came to it". Here we are, and the bridge is nowhere to be seen, and I am NOT stepping in that fast-moving stream of sewage that I see flowing by. "Shitstorm" indeed.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Any PM who kicks the can down the road deserves to be kicked in the can - talk about gathering technical debt!
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
#realJSOP wrote:
...I also happened to mention that I warned this would happen...
Nelek wrote:
I suppose the PM is going to love you from now on
Yes, I've also found that people love, love, love it when you give them an "I told you so!" :rolleyes: Most of the time they stop talking to me when I do it and I take that as a compliment and a reward. :laugh:
But more of a reward that anything else, right? :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I wouldn't like to be the PM - especially with you working there !!! :laugh:
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
On the other hand, if you were halfway competent, you would love having JSOP on your team!
-
You missed your calling - Director of Public Relations. :laugh:
Director of Public Retaliations
Nothing succeeds like a budgie without teeth.
-
Director of Public Retaliations
Nothing succeeds like a budgie without teeth.
-
On the other hand, if you were halfway competent, you would love having JSOP on your team!
This. I had a coworker who was my team leader in a project that had a very strong character. Until I gained his trust (I was the newly inserted member) it's been tough, but once I did he always had my back and the back of our teams. Most of all, if he ever took a decision because the managers or the customers wouldn't, he'd own it. Once I was being chewed off by the customer for having implemented a certain functionality before another, my team leader entered the room, placed between us and said "I told him that priorities, got a problem with that?". Not a peep more from the customer for the remaining months. Best team I ever worked in.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
-
On the other hand, if you were halfway competent, you would love having JSOP on your team!
-
This. I had a coworker who was my team leader in a project that had a very strong character. Until I gained his trust (I was the newly inserted member) it's been tough, but once I did he always had my back and the back of our teams. Most of all, if he ever took a decision because the managers or the customers wouldn't, he'd own it. Once I was being chewed off by the customer for having implemented a certain functionality before another, my team leader entered the room, placed between us and said "I told him that priorities, got a problem with that?". Not a peep more from the customer for the remaining months. Best team I ever worked in.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The problem is... they are so rare :sigh: :sigh: :sigh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Well, our transition to the cloud has resulted in diminished access. Before we moved to the cloud, we could still connect to our outward facing database servers via ssms using basically read-only accounts. we could inspect tables/views and even look at stored procs, but we didn't have execute permissions. On our cloud servers, that read-only account has been removed, which everyone thought was fine. Until today. A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases... The word "shitstorm" is being bandied about as a description of what's been happening since i sent that email. In that email, I also happened to mention that I warned this would happen, and was told by the PM that "we'd cross that bridge when we came to it". Here we are, and the bridge is nowhere to be seen, and I am NOT stepping in that fast-moving stream of sewage that I see flowing by. "Shitstorm" indeed.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013No company is perfect (especially government) and people make mistakes. You just threw your PM under a bus and complained about him TO A CUSTOMER! In my book that's an absolute no go. If you have problems, run it by your manager, if they don't listen and you're dissatisfied, leave. You're now just actively sabotaging the company from within. We have very strict employee laws in the Netherlands and in some cases it can be almost impossible to get one fired. I think this is one of the reasons for direct dismissal though. An absolute dick move, no matter how much you disagree with the policy :thumbsdown: [Edit] JSOP's customer was internal and everyone knew about the situation, making my reply not applicable in this case. Consider JSOP's reputation cleared, at least from this incident :laugh: [/Edit]
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
No company is perfect (especially government) and people make mistakes. You just threw your PM under a bus and complained about him TO A CUSTOMER! In my book that's an absolute no go. If you have problems, run it by your manager, if they don't listen and you're dissatisfied, leave. You're now just actively sabotaging the company from within. We have very strict employee laws in the Netherlands and in some cases it can be almost impossible to get one fired. I think this is one of the reasons for direct dismissal though. An absolute dick move, no matter how much you disagree with the policy :thumbsdown: [Edit] JSOP's customer was internal and everyone knew about the situation, making my reply not applicable in this case. Consider JSOP's reputation cleared, at least from this incident :laugh: [/Edit]
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
No company is perfect (especially government) and people make mistakes. You just threw your PM under a bus and complained about him TO A CUSTOMER! In my book that's an absolute no go. If you have problems, run it by your manager, if they don't listen and you're dissatisfied, leave. You're now just actively sabotaging the company from within. We have very strict employee laws in the Netherlands and in some cases it can be almost impossible to get one fired. I think this is one of the reasons for direct dismissal though. An absolute dick move, no matter how much you disagree with the policy :thumbsdown: [Edit] JSOP's customer was internal and everyone knew about the situation, making my reply not applicable in this case. Consider JSOP's reputation cleared, at least from this incident :laugh: [/Edit]
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Although I do agree with you on this, John is getting ready to retire here soon (I think) and I am pretty sure that he does not give an elephant about tactics and niceties anymore (always?). I could be wrong.
-
Although I do agree with you on this, John is getting ready to retire here soon (I think) and I am pretty sure that he does not give an elephant about tactics and niceties anymore (always?). I could be wrong.
That's really not an excuse for causing harm to the company you work for. If anything, it's a reason to keep him far away from customers.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
That would at least make it a whole lot less bad. That would basically be complaining to coworkers, which is a little like teambuilding :laugh:
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
No company is perfect (especially government) and people make mistakes. You just threw your PM under a bus and complained about him TO A CUSTOMER! In my book that's an absolute no go. If you have problems, run it by your manager, if they don't listen and you're dissatisfied, leave. You're now just actively sabotaging the company from within. We have very strict employee laws in the Netherlands and in some cases it can be almost impossible to get one fired. I think this is one of the reasons for direct dismissal though. An absolute dick move, no matter how much you disagree with the policy :thumbsdown: [Edit] JSOP's customer was internal and everyone knew about the situation, making my reply not applicable in this case. Consider JSOP's reputation cleared, at least from this incident :laugh: [/Edit]
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Sander Rossel wrote:
You just threw your PM under a bus and complained about him TO A CUSTOMER!
This is not quite accurate:
#realJSOP wrote:
A problem came up, and when the customer asked us about it, we had to tell him that he had to talk to the DBAs because the devs could no longer inspect those databases...
This could be because of a policy that developers may not access live systems, or for any number of other reasons. Going by what JSOP said here, the PM was not mentioned in the interaction with the customer. JSOP's complaint about this on CodeProject may be inadvisable (the parties involved may recognize themselves), but the situation is generic enough that it could have occurred with any cloud-based project.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
No company is perfect (especially government) and people make mistakes. You just threw your PM under a bus and complained about him TO A CUSTOMER! In my book that's an absolute no go. If you have problems, run it by your manager, if they don't listen and you're dissatisfied, leave. You're now just actively sabotaging the company from within. We have very strict employee laws in the Netherlands and in some cases it can be almost impossible to get one fired. I think this is one of the reasons for direct dismissal though. An absolute dick move, no matter how much you disagree with the policy :thumbsdown: [Edit] JSOP's customer was internal and everyone knew about the situation, making my reply not applicable in this case. Consider JSOP's reputation cleared, at least from this incident :laugh: [/Edit]
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
- I tried for a month to get to get the account back. 1) My boss tried for a month to get the account back. 2) We warned the customer (sits in the next room) that support would have to come from the DBAs and told them why. 3) A problem comes up, and I reminded everyone we've been trying to get the account back for a month. 4) Everybody already knew what was going on.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Although I do agree with you on this, John is getting ready to retire here soon (I think) and I am pretty sure that he does not give an elephant about tactics and niceties anymore (always?). I could be wrong.
You are not wrong. :) Even when I was younger, my was honest to a fault. I actually got let go a couple of times because of it. Such is life, but at least i didn't sacrifice what I believed in. My principles are fully intact.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
