Skip to main content

AI Muggins


I play a card game called cribbage. I often play it with my son. One interesting part of the game is the muggins rule. This means that you can claim points from other players turns, if they miscount the score. 

The scoring is slightly nerve racking, with each of us double and triple checking our scores, to avoid falling foul of ‘muggins’, that’s part of the fun. 

Man tinkering with AI / Robot
But my son and I also find ourselves discussing other hands of cards, in a sort of alternate history version of the game. “So if I had a 7 instead of a 2 of hearts, then I’d get a double run and score at least 8 more points”.  

“Yes Dad, if you had different cards then you would likely have a different score, but you don’t” he says while rolling his eyes. 

This sort of bitter-sweet history rewriting is a convenient tool for us to swallow the awkward truth of the real world. We often create alternate things to object to. 

Take Chat GPT 4 and tools like Copilot X. These are powerful tools, capable of doing useful tasks quicker and more easily than other tools.   

But no... (People say), they are dangerously sentient, or not sentient, fake, poor at this one task or too good at some other thing that people get paid for. To paraphrase my son, “Yes, if they were X then they would not be Y”.  

These tools are, well..., Tools. They have their limits that we are still discovering – they also have great abilities which we are also only just realising. Unlike our existing tools we haven’t had a chance to evaluate them and find their place. A task made harder by the fact that AI technology is improving extremely fast at the moment. 

Just in the realm of software test automation alone there are many opportunities where GPT4 and Copilot could help. For example, summarising test results, and providing the results in a human readable form. E.g.: 


 Or explaining test code, without the need for cumbersome abstraction layers like cucumber, E.g.: 

This is a GPT4 API interpretation of the tests for my cribbage scorer.

The creation of basic unit tests for existing code to enable easy refactoring, or when combined with ‘function calling’ being able check the results contained in a body of text. E.g,:  

This is my Cribbage Scoring Plugin, available in ChatGPT4.

Testers & Test engineers often fall into the “Ha it can’t do this” school of thought with new tools. Rather than thinking I’ve been given access to a particularly useful text and code analysis and generation tool for a price that approaches free. 

A tool that is improving month by month, a tool that extends my reach and increases my performance (compared to those shunning it because it couldn’t do some party trick or a skill you’ve spent your career honing. 

Comments

Popular posts from this blog

What possible use could Gen AI be to me? (Part 1)

There’s a great scene in the Simpsons where the Monorail salesman comes to town and everyone (except Lisa of course) is quickly entranced by Monorail fever… He has an answer for every question and guess what? The Monorail will solve all the problems… somehow. The hype around Generative AI can seem a bit like that, and like Monorail-guy the sales-guy’s assure you Gen AI will solve all your problems - but can be pretty vague on the “how” part of the answer. So I’m going to provide a few short guides into how Generative (& other forms of AI) Artificial Intelligence can help you and your team. I’ll pitch the technical level differently for each one, and we’ll start with something fairly not technical: Custom Chatbots. ChatBots these days have evolved from the crude web sales tools of ten years ago, designed to hoover up leads for the sales team. They can now provide informative answers to questions based on documents or websites. If we take the most famous: Chat GPT 4. If we ignore the

Can Gen-AI understand Payments?

When it comes to rolling out updates to large complex banking systems, things can get messy quickly. Of course, the holy grail is to have each subsystem work well independently and to do some form of Pact or contract testing – reducing the complex and painful integration work. But nonetheless – at some point you are going to need to see if the dog and the pony can do their show together – and its generally better to do that in a way that doesn’t make millions of pounds of transactions fail – in a highly public manner, in production.  (This post is based on my recent lightning talk at  PyData London ) For the last few years, I’ve worked in the world of high value, real time and cross border payments, And one of the sticking points in bank [software] integration is message generation. A lot of time is spent dreaming up and creating those messages, then maintaining what you have just built. The world of payments runs on messages, these days they are often XML messages – and they can be pa

Is your ChatBot actually using your data?

 In 316 AD Emperor Constantine issued a new coin,  there's nothing too unique about that in itself. But this coin is significant due to its pagan/roman religious symbols. Why is this odd? Constantine had converted himself, and probably with little consultation -  his empire to Christianity, years before. Yet the coin shows the emperor and the (pagan) sun god Sol.  Looks Legit! While this seems out of place, to us (1700 years later), it's not entirely surprising. Constantine and his people had followed different, older gods for centuries. The people would have been raised and taught the old pagan stories, and when presented with a new narrative it's not surprising they borrowed from and felt comfortable with both. I've seen much the same behaviour with Large Language Models (LLMs) like ChatGPT. You can provide them with fresh new data, from your own documents, but what's to stop it from listening to its old training instead?  You could spend a lot of time collating,