To sandbox or not
-
Reading this morning, about the error that seems to have locked several hundred million dollars of Etherium crypto currency, I wonder how many CP members are allowed to poke around in live systems. To me it seems like wandering around a minefield with closed eyes.
We're philosophical about power outages here. A.C. come, A.C. go.
if you play with matches you get burnt!
-
if you play with matches you get burnt!
-
Reading this morning, about the error that seems to have locked several hundred million dollars of Etherium crypto currency, I wonder how many CP members are allowed to poke around in live systems. To me it seems like wandering around a minefield with closed eyes.
We're philosophical about power outages here. A.C. come, A.C. go.
It seems like every month in QA we get someone asking how to undo an SQL DELETE or UPDATE query where they forgot the WHERE clause and the production DB is well and truly screwed. And of course we have to tell 'em "go talk to you boss, now. Run, do not walk." Sandbox, separated dev environment, whatever: if you are testing development code against a live system, you are an idiot, and will get burned.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
Reading this morning, about the error that seems to have locked several hundred million dollars of Etherium crypto currency, I wonder how many CP members are allowed to poke around in live systems. To me it seems like wandering around a minefield with closed eyes.
We're philosophical about power outages here. A.C. come, A.C. go.
I don't even have access to the production domain, if I want to get the latest production data I need to go beg a favour from the project manger woh won't even fart unless he has been through the checklist for it.
Never underestimate the power of human stupidity RAH
-
It seems like every month in QA we get someone asking how to undo an SQL DELETE or UPDATE query where they forgot the WHERE clause and the production DB is well and truly screwed. And of course we have to tell 'em "go talk to you boss, now. Run, do not walk." Sandbox, separated dev environment, whatever: if you are testing development code against a live system, you are an idiot, and will get burned.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
he shouldn't have access to the Prod environment to begin with.
-
he shouldn't have access to the Prod environment to begin with.
Slacker007 wrote:
he shouldn't have access to the Prod environment to begin with.
At my last job we had access to production and even did the code updates. Then we hired a networking nazi dude who took our access away. Slowed us way down. At this job I have access to production. Sometimes it is necessary. I hate working places where they put barriers in place just because.
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
Slacker007 wrote:
he shouldn't have access to the Prod environment to begin with.
At my last job we had access to production and even did the code updates. Then we hired a networking nazi dude who took our access away. Slowed us way down. At this job I have access to production. Sometimes it is necessary. I hate working places where they put barriers in place just because.
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
I have been doing this for over 15 years, and have never had access to Prod. Didn't slow us down. With that said, we had deployment engineers and sys admins that had access to Prod. Our DBAs had access to prod, but the engineers/developers did/do not. I don't agree with your standing that you should have access to Prod. If you are fixing things in Prod then you guys are messing up somewhere else down the production line. My two cents. :) Edit: also, if you have an issue in Prod that needs to be fixed, then you try to roll back at all costs. That is what a rollback plan is for. your deployment engineer should have one. :doh:
-
I have been doing this for over 15 years, and have never had access to Prod. Didn't slow us down. With that said, we had deployment engineers and sys admins that had access to Prod. Our DBAs had access to prod, but the engineers/developers did/do not. I don't agree with your standing that you should have access to Prod. If you are fixing things in Prod then you guys are messing up somewhere else down the production line. My two cents. :) Edit: also, if you have an issue in Prod that needs to be fixed, then you try to roll back at all costs. That is what a rollback plan is for. your deployment engineer should have one. :doh:
-
Reading this morning, about the error that seems to have locked several hundred million dollars of Etherium crypto currency, I wonder how many CP members are allowed to poke around in live systems. To me it seems like wandering around a minefield with closed eyes.
We're philosophical about power outages here. A.C. come, A.C. go.
Yet: > The price of Ethereum on Wednesday was up 2.3% to $301.25. The irony of it all.
Latest Article - Class-less Coding - Minimalist C# and Why F# and Function Programming Has Some Advantages Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Reading this morning, about the error that seems to have locked several hundred million dollars of Etherium crypto currency, I wonder how many CP members are allowed to poke around in live systems. To me it seems like wandering around a minefield with closed eyes.
We're philosophical about power outages here. A.C. come, A.C. go.
Herbie Mountjoy wrote:
I wonder how many CP members are allowed to poke around in live systems.
I don't do it. I refuse credentials and make a specific point of asking operations for data rather than access. If direct access is required then I do it in a pair set up with an operations person. I also push that idea as part of the development process - developers should never have access. I worked at one place where a casual question lead to be me finding out that the DBA was doing all of their development work on the production database and was not checking anything into source control. As I recall I don't even think they knew what source control was.
