The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
"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
after you have enough caffeine to apply gaussian sharpening to any lingering smudged edges of dream, spend an hour on CodeProject, send hate mail to advocates of waterfall-development, and perform your haka warm-up [^] before entering the scrum octagon: [^] ?
«While I complain of being able to see only a shadow of the past, I may be insensitive to reality as it is now, since I'm not at a stage of development where I'm capable of seeing it.» Claude Levi-Strauss (Tristes Tropiques, 1955)
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!
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
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.