Once we figure out the odds, I kick off a number of simultaneous processes to generate the next chapter of the story the user is experiencing. Here’s a breakdown of the various prompt techniques and other approaches I use to make the experience as immersive as possible!
It blows my mind that to this day, in the year 2025, there’s a large number of software development shops that don’t employ automated testing. There are certainly companies out there who have done a good job with automated testing and are reaping the benefits, but I’d say there’s more that are missing some form of unit or integrated testing as part of their flow. Considering the importance of the business functions that their software provides (otherwise, why are they writing it?), it’s mind-boggling that they’d leave mission-critical functionality untested, or at least not tested in an automated way. Let’s dive in!
Today I’d like to spend some time showing off the approach I used for Infinite Scribe’s odds calculation, as I think it’s pretty neat :) Taking advantage of a few prompt engineering techniques we’re able to come up with a flexible approach that is easily extensible.
Taking a bit of a break from the software development team management posts for a second (they were very cathardic!), part of the reason I’ve been silent on the blog as of late was because I was spending all my time on my generative AI magnum opus - a little mobile app I’ve called InfiniteScribe. I’d like to put together a series of posts describing exactly what I’ve managed to achieve with the game so far in two months, and where I’d like to take it!
A metric I’ve been mulling over the past few months is something called “Release Confidence”. The idea is that you’d be able to measure the confidence implementation teams have in the code that they’re shipping to production - that it’s feature complete, bug free, and won’t cause any issues when deployed. While it’s not something you can measure with hard numbers, there are a few related metrics you can keep an eye on, and having a “low” release confidence can enable some productivity-killing behaviours to compensate for it.