Mostly cloudy
-
I once left a 30-person company for one person. The person was part of my team and he was so toxic I didn't want to spend another day with that asshole. Another person left a few months later for the same reason. I've worked at another company like that, although it was a lot smaller with only seven people, but it was quite doable to avoid the toxic person. I can imagine your job has some cool challenges and it's probably a good place to work. Always a bummer when one or two guys ruin the atmosphere. Good luck with those guys, maybe send out a couple more frustrated emails? You have my blessing ;)
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
The way I see it is that I retire in 3 years, an I have no doubt I can return their fire for that long. :)
".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, 2013This is why I want to be just like JSOP when I grow up.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
-
This is why I want to be just like JSOP when I grow up.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
I inspire greatness. :)
".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, 2013Conway's Law: In any organization there is one person who knows what is going on. That person must be fired.
-
Absolutely but I bet he doesn't suffer fools gladly.
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
pkfox wrote:
I wouldn't like to be the PM - especially with you working there !!!
pkfox wrote:
Absolutely but I bet he doesn't suffer fools gladly.
what a disappointment... I didn't have you for a fool, but if you tell it so... :rolleyes: ;P :-D :laugh:
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.
-
9/10 times it's safe to assume "a customer" is not someone in the office next to you ;) I apologize to the 1/10.
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 makes me the 2/10. My customers are other departments within the company and in occasions even within my division.
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.
-
pkfox wrote:
I wouldn't like to be the PM - especially with you working there !!!
pkfox wrote:
Absolutely but I bet he doesn't suffer fools gladly.
what a disappointment... I didn't have you for a fool, but if you tell it so... :rolleyes: ;P :-D :laugh:
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.
-
That makes me the 2/10. My customers are other departments within the company and in occasions even within my division.
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.
2/20, you're part of the next 10 :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
-
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 -
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
-
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, 2013Did you move to CloudOne? There is a push to move our currently local-hosted client/server (WinForms) application to CloudOne on both NIPRNET and SIPRNET. I keep saying it's going to be a "shitstorm" as well since I, as the lead dev, have the same sysadmin rights as you had on our production data (and use it all the time). With everything CloudOne-related having to go thru port 443 apparently, a lot of what we've done for 15+ years is going to go away. You may be a perfect case study for me... :)
-
Did you move to CloudOne? There is a push to move our currently local-hosted client/server (WinForms) application to CloudOne on both NIPRNET and SIPRNET. I keep saying it's going to be a "shitstorm" as well since I, as the lead dev, have the same sysadmin rights as you had on our production data (and use it all the time). With everything CloudOne-related having to go thru port 443 apparently, a lot of what we've done for 15+ years is going to go away. You may be a perfect case study for me... :)
NIPR is cloud2, and SIPR is cloud1. We haven't even gotten to the SIPR side yet. We have to RDP to a jump box, and then RDP from tehere to our dev boxes. we can do anything we want on the dev db server, but for test,staging, and prod, we get nothing. It's very locked down.
".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 -
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
The PM deserved it. They are a blight upon society
