I'd quickly realised that a set of words which covered most of the alphabet (20 words, leaving b, g, j, q, v, and z excluded) allowed solving virtually all Wordle puzzles. The game quickly lost any challenge.
wimpy
crowd
thank
fuels
Altering order might give faster results. The order presented leaves the most common letters (e, t) for last. Z is quite uncommon, q is virtually always followed by u, similarly common pairs such as ch, sh, and th, as well as three- and four-letter combinations ing and tion, though those won't show frequently in five-letter words of default Wordle.
It would be possible to vary word choice based on revealed matches and hits, but if your goal is simply to solve (rather than minimise attempts), the above list works quite well.
I only play on hard mode for this reason. My next guess must always be a possible answer based on my current information, and that varies the puzzle enough from day to day that I still find it enjoyable to play occasionally.
I haven't played wordle much since it was purchased but NYTimes ran a story in the last couple days saying how "Hard mode" is actually easier based on their research. Just throwing it out there as food for thought not in a "gotcha" sort of way.
Does that not lead you to situations where you have to guess the last letter on each round? Or do you choose words to avoid getting trapped in that situation in the first place?
I try to avoid the common traps, but it can be tricky.
I also impose this additional constraint on myself, which the game doesn't enforce, that I can't reuse letters that have been marked gray. Sometimes you just can't think of the next word, or might be tempted to use a gray letter because that way you could get more information from other letters, but I avoid using them.
yes, I do the same thing. I wish there was a way to get the implementation to enforce that rule too so I never accidentally try a word that I already know can't be the answer.
I thought this was old news? I remember people making videos about using information theory to solve Wordle back when it was particularly hyped. (After writing this I checked, there's even a 3 blue 1 brown video on this)
This isn't groundbreaking science, sure, but it is a great way to get people interested in a topic. After all, it wouldn't be on Hacker News if the word Wordle wasn't in it. I'm a huge fan of using things like this to teach science, math and engineering.
We started using "Solve 100 Wordles programmatically" as our technical interview, and people _love_ it. They get really into it and have fun. It's pretty easy to do inefficiently, and it's great to watch people build on it and try to improve their scores.
It has two benefits: 1/ everyone clearly understands the problem 2/ people see it as fun rather than a drag.
Another small benefit: Everybody understands this isn't what the job is. Nobody is hiring you to beat Wordle, and you solving this is clearly not somehow on the path to their actual task, they are asking you if you can write software which solves a problem and you're demonstrating that you can do that, which makes sense.
I think "Solve 100 Wordles programmatically" sounds like a lot of work, so that'd probably be a "No" from me unless it was last hurdle for a job I was enthusiastic about but unlike "Write a program to solve this class of graph problem" I at least wouldn't be worried that you're trying to get me to do work for free.
Actually Wordle solver as Code Review task sounds like maybe a more interesting live interview than the one we do today. "Here's this mediocre Wordle solver, what is your feedback in review?" has the advantage that they've probably seen a Wordle puzzle before but it's not an example problem they've seen in fifty textbooks.
Well, the 100 Wordles is just "Solve one Wordle" in a for-loop. If you're an even somewhat decent engineer, it takes under 10 minutes to get it working (inefficiently).
Then we encourage people to do whatever they want next: improve their average score, build a frontend UI for it, solve on Hard Mode, etc.
In the past, we never did technical interview questions like this. We always asked people to bring their own project, and work the way they want to. However, with the addition of AI, we hit a wall: we want people to feel they can use AI in a way that mimics how they'd actually work day-to-day, BUT we also need a simple check to make sure they understood engineering basics.
plug to my blog post where I did something similar a few years back! https://willbeckman.com/wordle.html :). Not sure if this is an identical solution, but it was a fun little project.
I'd quickly realised that a set of words which covered most of the alphabet (20 words, leaving b, g, j, q, v, and z excluded) allowed solving virtually all Wordle puzzles. The game quickly lost any challenge.
Altering order might give faster results. The order presented leaves the most common letters (e, t) for last. Z is quite uncommon, q is virtually always followed by u, similarly common pairs such as ch, sh, and th, as well as three- and four-letter combinations ing and tion, though those won't show frequently in five-letter words of default Wordle.It would be possible to vary word choice based on revealed matches and hits, but if your goal is simply to solve (rather than minimise attempts), the above list works quite well.
> The game quickly lost any challenge.
I only play on hard mode for this reason. My next guess must always be a possible answer based on my current information, and that varies the puzzle enough from day to day that I still find it enjoyable to play occasionally.
I haven't played wordle much since it was purchased but NYTimes ran a story in the last couple days saying how "Hard mode" is actually easier based on their research. Just throwing it out there as food for thought not in a "gotcha" sort of way.
Does that not lead you to situations where you have to guess the last letter on each round? Or do you choose words to avoid getting trapped in that situation in the first place?
I try to avoid the common traps, but it can be tricky.
I also impose this additional constraint on myself, which the game doesn't enforce, that I can't reuse letters that have been marked gray. Sometimes you just can't think of the next word, or might be tempted to use a gray letter because that way you could get more information from other letters, but I avoid using them.
yes, I do the same thing. I wish there was a way to get the implementation to enforce that rule too so I never accidentally try a word that I already know can't be the answer.
Yes, that does happen occasionally, and it's part of the game for me to try and avoid getting trapped like that.
gotta see how your strategy holds up in sexaginta-quattuordle
I thought this was old news? I remember people making videos about using information theory to solve Wordle back when it was particularly hyped. (After writing this I checked, there's even a 3 blue 1 brown video on this)
My favourite along those lines was solving wordle in 1 guess using the distribution of coloured squares on social media https://www.kaggle.com/code/benhamner/wordle-1-6
Yes 3blue1brown made a series of videos which explains it : https://www.youtube.com/watch?v=v68zYyaEmEA ; https://www.youtube.com/watch?v=fRed0Xmc2Wg .
This isn't groundbreaking science, sure, but it is a great way to get people interested in a topic. After all, it wouldn't be on Hacker News if the word Wordle wasn't in it. I'm a huge fan of using things like this to teach science, math and engineering.
We started using "Solve 100 Wordles programmatically" as our technical interview, and people _love_ it. They get really into it and have fun. It's pretty easy to do inefficiently, and it's great to watch people build on it and try to improve their scores.
It has two benefits: 1/ everyone clearly understands the problem 2/ people see it as fun rather than a drag.
Another small benefit: Everybody understands this isn't what the job is. Nobody is hiring you to beat Wordle, and you solving this is clearly not somehow on the path to their actual task, they are asking you if you can write software which solves a problem and you're demonstrating that you can do that, which makes sense.
I think "Solve 100 Wordles programmatically" sounds like a lot of work, so that'd probably be a "No" from me unless it was last hurdle for a job I was enthusiastic about but unlike "Write a program to solve this class of graph problem" I at least wouldn't be worried that you're trying to get me to do work for free.
Actually Wordle solver as Code Review task sounds like maybe a more interesting live interview than the one we do today. "Here's this mediocre Wordle solver, what is your feedback in review?" has the advantage that they've probably seen a Wordle puzzle before but it's not an example problem they've seen in fifty textbooks.
Well, the 100 Wordles is just "Solve one Wordle" in a for-loop. If you're an even somewhat decent engineer, it takes under 10 minutes to get it working (inefficiently).
Then we encourage people to do whatever they want next: improve their average score, build a frontend UI for it, solve on Hard Mode, etc.
In the past, we never did technical interview questions like this. We always asked people to bring their own project, and work the way they want to. However, with the addition of AI, we hit a wall: we want people to feel they can use AI in a way that mimics how they'd actually work day-to-day, BUT we also need a simple check to make sure they understood engineering basics.
>In simulations, their approach solved 99% of Wordle puzzles, while the traditional method solved just 90%.
This seems wrong to me, getting a 98%+ solve rate for Wordle is pretty common.
What I'm interested in is the best starting word. Using Shannon entropy, the paper finds that it is "tares".
To paraphrase von Neumann, isn't that how everyone does it?
plug to my blog post where I did something similar a few years back! https://willbeckman.com/wordle.html :). Not sure if this is an identical solution, but it was a fun little project.
Paper: https://orb.binghamton.edu/nejcs/vol8/iss1/6/