|
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. 
|
|
|
|
|
Probably a difference between large and small companies perhaps.
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 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
|
|
|
|
|
Yet:
The price of Ethereum on Wednesday was up 2.3% to $301.25.
The irony of it all.
|
|
|
|
|
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.
|
|
|
|
|
|
|
He was one of my favorites too. ![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
|
|
|
|
|
The irony that, back in the 80s, you had to get American actors to play Brits when, nowadays, it appears you have to get British actors to play Americans.
Still, I did like Magnum P.I., and his accent wasn't too bad.
This space for rent
|
|
|
|
|
Higgins, the best character on the show IMHO.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
"Zeus! Apollo! Patrol!"
Software Zen: delete this;
|
|
|
|
|
|
|
I think that is part of the Windows text box control. Same if you press backspace in an empty text box.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
That doesn't happen on any app I've got, one's I've writren or otherwise
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
It does if you use the Win32 edit control directly. MS just disabled the beep by default in their higher level libraries. Because apparently, only Win32 is worth of the beep.
Jeremy Falcon
|
|
|
|
|
Check it out. Pulled up some Win32 code of mine where I had to explicitly stop the beep. Just to preface the code so it makes sense, it's C code and I used typedefs for intrinsic types for this app so I didn't have to change out my entire app if I swap from 32, 64, whatever bits, change compilers with diff implemenations, etc. in the future.
Anyway...
static numeral CALLBACK
subprocEditControl(HWND hWnd, uint32 uMessage, WPARAM wParam, LPARAM lParam, unumber uIdSubclass, dword dwRefData)
{
...
switch(uMessage)
{
case WM_CHAR:
if(wParam == VK_TAB) return 0;
...
}
...
return DefSubclassProc(hWnd, uMessage, wParam, lParam);
}
Jeremy Falcon
modified 10-Nov-17 11:50am.
|
|
|
|
|
She uses the ENTER and BACKSPACE keys interchangeably - they're close enough on the keyboard for that to be acceptable for any standard user.
Remove one or both keys from keyboard.
Problem solved.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
The app beeps when a textbox has focus and the enter key is pressed. I didn't design that 'feature' but I will have to override it.  Try it...put two textboxes in a winform and try to navigate between them using Enter or Shift+Enter. It baffles me how she manages to 'get around' in other programs using just the Enter key. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
It it a WinForms thing specifically? My WPF apps don't to that
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I'll be dam... It DOES do that in WinForms, but not in WPF.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Cool, good to know...I'll add it to the list of possible resolutions! Thanks for testing!
"Go forth into the source" - Neal Morse
|
|
|
|
|
I think WPF doesn't use the Common Controls Library, which WF uses. The beep is a part of that.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Brisingr Aerowing wrote: WPF doesn't use the Common Controls Library
None of WPF's controls or dialogs use the built-in controls or dialogs. They're all emulations of the standard controls, essentially built on DirectX.
Software Zen: delete this;
|
|
|
|
|
I don't know if I should tell you this, but there is some kind of bug in .NET, that happens once in a blue moon, when you use the enter key to enter text in a textbox: Every now and so often the cursor will jump to the next tab stop when you hit enter on a WPF textbox, but the text is NOT entered. If this is a WPF textbox: Good luck! I hope I didn't spoil your evening!
Get me coffee and no one gets hurt!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
Now, how in the world did I not consider that a user might want to use the Enter key this way?. I must be slipping! 