Skip to main content

Thinking forward for regulations

Listening is a skill that can bring some unexpected benefits. Being willing to listen, without an opinion (or, in some cases, no awareness of what they are talking about) can yield bits of useful information on an issue you are facing.

This was the case a few days ago - a pair of us were discussing both a student that was having an issue on a topic, and the regulation of the future, in regards to Machine Learning and AI. (Yes, my conversations do wander - we started out with woodworking). The student was a one who had made a program - since it worked, they were happy with it, as we all are when first learning a topic. Having someone with skill come in and redo nearly everything is a blow to the ego.

Approached correctly, this can teach so much. Praise for getting it working is a important step, then carefully showing how other options may have been a better, more-performant choice is where the learning comes in. If this isn't done at a slow-enough pace: depending on the student, it may take days to ensure they are grasping the concepts, rather than just feeling like they did nothing correct.

Learning is important, and making sure that what is there is the best possible - then improving on that with other inputs is the way to quality.

However, with the pace of technology running at an ever-increasing rate, there really may not be time to make the regulations for technologies that will be common to iterate on what is probable. The regulation that is needed has to be mostly correct with the potential that the underlying technologies may become more advanced by the time these are fully made.

And testing is a huge part of that - you may well have seen the potential issues with the training of machines to do a portion of the job that humans used to do - and if you look at some of the new innovations, the potential of a problematic set of training data causing damage, or overlooking a situation that isn't covered in that training is growing: how are we going to test the lack of bias that is hoped for with these technologies?

I'm sure someone out there has a plan for this - I don't have an answer at the moment to make sure that - worldwide - there are sufficient training data for all the projects, and that they are unbiased. Enshrining the current prejudges and taboos will not serve us well into the future: we need to have a effort made to ensure that the data sets are as fair as possible. We may not be able to update the training in the future: let's plan for that.

Popular posts from this blog

100 Days of Code Retrospective: Finding options

Thanks for the image, brainyquote.com ! Warning: this section has some details you may not wish to know - skip it if desired. So why, with a child and parent(s) that need attention, would anyone start on a learn-it-yourself path? This has been the best of a list of options, some of which weren't healthy. I'm not skinny enough to strip or work in a gym, I've lost my patience for call center work (the bosses, not most of the customers and co-workers), and damaged a shoulder working food service. I have to make plans for the future - parent isn't going to live forever, and the child is both working full-time, and looking for someone to start a long-term relationship with. The relationships I've had left me with not only bills, but a distrust of someone who isn't willing to work as hard as I do. My college degree is mostly worthless, with the changes in technology - by stopping to care for the family, I found myself behind. And the student loan ...

Drop-down values for injection

cover_image: https://www.pexels.com/photo/flat-lay-photography-of-gold-iphone-on-opened-notebook-beside-pen-583847/ canonical_url:  --- Photo by Jessica Lewis 🦋 thepaintedsquare   Learning in public is grand, and when you have a team that is willing to help with something that seems simple, but you fall into overthink for the wrong items, it can really help to type out your thoughts, actions, and what the program does to frustrate you. And in this case, getting a value I could see in the debugger was the issue The automation needs to check for page elements – and the drop-down selector triggers potentially different elements. Plus, depending on the user logged in, there may well be different options available in that drop-down. Then, I can get the options available for the user on the drop down, get their values, cycle through them, and verify each set of elements on the page. My test account for this has four options on the drop-down, so I budgeted a couple of hours to get ...

Redefining my Role

Confession: I am a nice person. I'm the one that will check on people - and be concerned if someone is acting off. Or donate money to make sure the potluck I can't attend has everything it needs. This has had an effect on my career: I was less willing to point out 'in public' errors in the code or things that just felt off to me while testing. And this stopped me from being the best tester I could be. Trying to be kind to someone that was having a rough patch, or simply not wanting to expose them to a potential attack was both me trying to get things correct, but care for them. I've decided to embrace this aspect of myself, and shift my focus. Being 'nice' to the product, or company must include being the voice for both end users and the team. Finding things that will be difficult for them, confusing, or flat-out wrong is a major part of my job. And this was also one reason I don't 'delight', at first, when something doesn't work as expected:...