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

30 Days of Postman - for Testers!

  https://www.pexels.com/photo/white-and-brown-cat-lying-beside-a-laptop-and-toys-5468268/ Photo by Karolina Grabowska from Pexels   Working with developer- focused tools can be a challenge for some testers: we may know what the words mean, but haven't used those skills recently enough to make the tasks simple. Or we may not have ever used them, other than at a quick glance to make sure that what we are getting matches what it should be sending. And some give results that require us to go find another team member to help interpret the results. Being a more-independent tester has always been one of my goals - being able to use the tools that are common in the team, and be able to do at least basic tasks that support my tests with them. Our team used Postman for many of the API tasks that we had, so exploring this tool was a natural fit. There are alternatives it there, both graphical and command line, so feel free to explore! The items that you can do, and tools that help

Where Is It? Part 1 - Inputs

Photo by Pixabay from Pexels     I am job-searching, and running into some coding challenges. Most of them are simple - some seem to want one-line solutions that require two cups of coffee and a half-hour to figure out what they want. Others are far above where my skills lie, and these I give a try for, and learn. And then there are the ones that offer, seemingly randomly, a challenge - within my skills (or at least my research skills) - that could be used as part of a larger project that I want to work on. This was the case last week, when I tried for a position that was a bit above what I felt I could do comfortably. The challenge was to let someone enter items, and then give back their location. In a language I am just familiar enough to be a danger to myself in. Happily, and thinking forward about how I could use this as a part of a larger program that would  use something like this to interact with the user. And also, this is command line, and thinking of how to set this up to

Do Your Tests Wobble?

Image by delo from Pixabay “The green reed which bends in the wind is stronger than the mighty oak which breaks in a storm.”  ― Confucius  I was asked to pair Blog with Lena Weiberg - much to my shock and delight. This was the perfect opportunity to hear another point of view on something, and share it with the wider community.  ~ Part of being a good tester, to me, is making sure I stay aware of the trends in development. Knowing  how the team is working can help get comments and questions to them at the proper times, and has  the information that can be acted on. In this quest, I attended a recent online conversation where the  topic was primarily on the size of 'steps' taken in software development: making sure each step takes  a reasonable amount of time, that it leaves the system in a state that isn't worse than it was before the  change, and that could - if needed - be deployed at this point.  The concept of “wobble”  (I'm not sure