8 Questions Business Leaders Should Ask Before Jumping Into AI
In this e-book, Revelry product strategy expert Heather Bourdaux and software engineering leader Jason Pollentier share both best practices and key considerations from early…
In this e-book, Revelry product strategy expert Heather Bourdaux and software engineering leader Jason Pollentier share both best practices and key considerations from early…
In my previous post, I wrote about using OpenAI‘s Functions API to force their large language models (LLMs) to return structured, machine-readable responses. The natural…
Like so many others, I’ve been playing around with language models lately. Also like so many others, I’ve been alternately amazed and amused at…
Termites and software bugs have this in common: they must be identified and managed quickly to avoid devastation. Termites can destroy the structural integrity…
Most software teams have left behind the Waterfall(1) methodology in favor of approaches that move faster and flex more to accommodate changes and maximize the…
We at Revelry have a #wordelry channel in Slack where we share our Wordle scores and commiserate about unlucky guesses. It’s a great way…
A really hard problem can feel like a great chance to flex our skills and finally use some of those architectural patterns we’ve been…
A while back several Revelers were chatting in Slack about learning and working as a software engineer. Some interesting ideas were being thrown around…
Lately I’ve been exploring various automated testing techniques, and it’s about time I got to property-based testing, also known simply as property testing. I…
Mutation testing involves running your test suite many times, modifying the application code in different ways to see if the tests catch the change.
The hard part of this was recognizing the algebra beneath layers of domain-specific business rules.
The team that seeks out feedback and views it as an asset rather than a slap in the face is the team that delivers real value to clients.
I was lying in bed this morning planning the best way to handle a merge conflict I know is coming with a colleague’s PR today, and I realized I’d like to know a couple of tricks for certain situations. Here they are:
Make sure you’re doing this consistently, because down the line it makes a big difference to somebody digging through git history.
Jason had a theory: He dislikes abbreviations and acronyms, ambiguity and magic. And he likes explicitness and clarity. So he wondered why some code naming conventions seem to punish verbosity (when it’s required) and what this all has to do with language naming conventions.