Right? Like the information is all there on Google and Iâm taking care enough to check I canât straight up break everything⊠Part of the reason I asked is because I donât see it in use in other queries where I think it should be used. If he was like âyeah when I port it into python for automation, it will stop working. So we canât use it for automated projects.â Thatâs a concern I thought might be valid⊠He was like just âregex can get really complicated really fast and you can get stuck troubleshoot it forever.â
I even said during the interview I use Google a lot to find the best way to do stuff. I want to learn. I donât want to stagnate where I am. And they are trying to teach me different things⊠By having me watch them do stuff over teams, a way I actively canât learn. They also donât want me to stagnate with my current skill set.
I think we will all eventually come to an understanding but itâs going to be really frustrating until then. Probably for them as well. I will learn things out of spite. Iâm incredibly bullheaded. Itâs my defining trait. Iâve had friends warn prospective managers about me before they hired me. So I try to understand it goes both ways. I always become very good at whatever my job is. Thatâs the trade off.
And as much as I am frustrated by things like this, I like the team Iâm on. So once we get past the growing pains I think it will all come together nicely.
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.
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.
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.
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)
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??
