Thatās a great way to do it. Like at the point someone is aware something is possible, teach them the better way. Give them resources. Bonus points if itās in a way they can learn well. ![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Totally different kind of training environment, but what was pounded in my head, and I pound into students heads
āYou donāt know what you donāt knowā
Explosives? Nuclear engineering?
High risk situations definitely apply ![]()
Hey @amal, the second datasheet link on this page is broken, itās missing the D in DangerousThings, just so you know:
The problem with SQL (databases actually) is that a wrong try might cause irreparable damage to the environment.
I do agree with you that people should be allowed to try things and learn by doing.
I love the energy you are displaying and that is a great trait!
In my work environment I would let you try your hand at doing something before I try to tell you how, because not only the challenge is healthy but learning after trying plants knowledge much better.
but⦠if I had you in one of our Data teams⦠unless I had a mock environment, I would also need some more confidence that you knew what to never do.
That said, Iāve seen an apprentice kill a whole database environment to the level that someone had to drive 4 hours to get a new backup from the second location (airgapped network-isolated data farm).
And the apprentice wasnāt even alone, he had a supervisor. But went too speedy with his trigger finger.
was at the same time hilarious and terrifying.
I totally get that. Iām pretty careful. Thatās why I had reached out to him asking if there was any technical reason not to. Iām afraid of any table altering queries so I have that going for me, too. But like if there was incompatibility with other systems we will have to use later in the project, issues with how the info is stored, it takes up too much processing power and should be a last resort, etc. All things I can imagine reasonably being issues I might not be aware of.
I could accept those outright as a reason not to use it. Because those are the kind of questions that feel really specific to our environment and where weighing in with first hand experience has a lot of bonus value. For all I know our database is hooked up to a flux capacitor thatās allergic to curly brackets.
Everythingās going to be fine. I thought I was 80% done with this project and I asked a question and it sounds like the project as written is not what was requested by the user. We have a meeting tomorrow and heās going to see my date column thatās just three substrings in a trenchcoat. I might even be able to see him clutch his head over it. Itās a big ol chunk of ugly in the middle of my query. But I might get to start over and make it even bigger and badder. ![]()
I think the best hilarifying thing I ever saw at work was when I worked in Post Maintenance Return to Service for a private jet company. All the people who verified the work was being done and documented right were old mechanics who didnāt like computers. Then IT tried to roll out a DIGITAL ONLY release process. The taught one or two of the younger guys and then shut down all the printers.
Planes ended up trapped in the ground for hours. The company was at serious risk of going bankrupt because of the narrow margins and how much was lost every hour. Plus the cost of renting planes from other companies to fulfill customer needs. It was pandemonium and it wasnāt my problem.
Thatās a great attitude.
And a few hilarious remarks. Kudos there! ![]()
Also, the IT thing sounds frightening close to reality for some of the clients I have to deal with! ![]()
Oh no. Well I hope the end of 2022 has nothing but perfect clients and nothing on fire that you donāt want to be (but fire everywhere you do want it) ![]()
![]()
![]()
"You better watch out,
Let me tell you a fact.
If your SQL has literals,
Youāre gonna be hacked.
SQL Injection is cominā to town
Weāve got a shared cache,
Itās memory linked twice.
But it only works well,
When youāre binding all nice.
SQL Injection is cominā to town
(bridge)
We know when youāve been lazy,
And concatenated simple strings.
So just make sure you bind your stuff,
And donāt let the bad guys in.
So⦠you better watch out,
Let me tell you a fact.
If your SQL has literals,
Youāre gonna be hacked.
SQL Injection is cominā to town"
Source: SQL Injection ā A Christmas Carol ā Learning is not a spectator sport
The new check mark freaked me out in my tired state of mind XD
Just a little reminder that heās always watching you
Itās getting under my skin for that matterā¦
So I was hoping to get my 12 mth visit badge early next year but after 29 hours of airports and flying, I seem to have missed a day (despite visiting in the air and at the stopover). Not sure what happened because the longest period of not logging in would have been maybe 18 hours.
Does anyone know if the site counts visits according to a set time zone or something? In other words, how does it work??
Itās black magic that only the resident AI is comfortable messing with.





