Bennett Foddy makes games that refuse to flatter you. They wobble, they punish, and they expose impatience fast. That is the point. In the SE Daily podcast...
Games That Push Back: Bennett Foddy’s Hard, Honest Design Philosophy
Bennett Foddy makes games that refuse to flatter you. They wobble, they punish, and they expose impatience fast. That is the point. In the SE Daily podcast discussion, his work comes through as a blunt lesson in craft: difficulty is not cruelty when it teaches focus, humility, and care for the player’s attention. I’m Ermenildo Valdez Castro, Jr., and I’ve spent years around stubborn systems; Foddy’s games feel like code with a conscience.
Key Takeaways:
- Bennett Foddy’s games use failure as a design tool, not a bug.
- QWOP, Getting Over It, and Baby Steps all test patience and control.
- The real lesson is about learning, restraint, and honest feedback.
- Great game design can respect the player without making things easy.
- His approach matters to developers, product teams, and anyone building hard software.
What is Bennett Foddy’s style of game design?
Bennett Foddy’s style is simple to describe and hard to copy. He builds games that fight back. The controls are awkward on purpose, the goals are plain, and the road to success is full of slips, falls, and faceplants. You do not glide through his games. You wrestle them.
That sounds rude. It is, in a way. But it is also honest. Most games hide their wires. Foddy leaves the wires in plain sight, then asks what happens when the player must think about every small input. When I first watched people play QWOP, I laughed like everyone else, then felt uneasy because the joke was not just the runner on screen. The joke was how fast confidence dies when a system demands real control. That hit me as a software engineer. Bad assumptions always do.
His best-known games show the pattern clearly. QWOP turns running into a lopsided physics lesson. Getting Over It with Bennett Foddy puts a man in a pot and makes progress feel precious because one slip can erase minutes of work. Baby Steps, his newer release, keeps the same core idea: movement itself becomes the puzzle. The player is not defeating enemies. The player is learning how to hold still, act carefully, and keep trying.
The SE Daily episode on Foddy’s work is worth hearing because it frames him as more than a prankster designer. He is a former professor at NYU Game Center, and that matters. Teaching game design means you see what students miss: the difference between meaningful difficulty and lazy friction. Foddy’s games are difficult, yes, but the difficulty is shaped. It has intent. There is a moral line there, and good makers should notice it. Work should be demanding, not pointless.
Frankly, a lot of modern products forget that. They ask users to adapt to bad design and call it “power.” Foddy does the opposite. He makes the pain visible. If a system is clumsy, he makes you feel the clumsiness. If patience is needed, he makes you earn it.
Why do these games matter?
These games matter because they tell the truth. That may sound dramatic, but it is not. Most digital systems pretend they are smooth until they break. Foddy’s games start broken on purpose, then force the player to learn how meaning is built through struggle. That is useful far beyond games.
- They teach humility. You cannot brute-force your way through QWOP. I’ve seen smart engineers, myself included, hit the wall because they assumed force would beat form. It rarely does.
- They make feedback legible. Every wobble in Getting Over It says something. Good software should do that too. Users should know what happened and why.
- They reward attention. Baby Steps is not asking for speed. It asks for precision. That is a rare gift in a noisy world.
- They turn failure into data. When you fall, you learn. That is basic engineering wisdom, and honestly, basic human wisdom too.
- They protect the dignity of effort. There is a quiet Catholic truth here: labor has worth even when it is hard, even when no one claps. Work forms the worker.
When I worked on large systems, the teams that improved fastest were not the ones that hid mistakes. They were the ones that studied them. Foddy’s games do that in public. They put embarrassment on the table and say, “Now what?” That is uncomfortable. Good. Comfort is overrated.
There is also a design lesson about trust. A game that pushes back can still be fair. That is the key. Fairness means the rules stay consistent, the player can learn, and success comes from growth, not luck. When design gets lazy, it uses difficulty as smoke. Foddy does not. He uses difficulty as a mirror.
If you want a broader view of how thoughtful software feels, the principles overlap with better product thinking, better debugging, and even better leadership. I’d also point readers to this practical piece on software development best practices, because the same habits show up there: clear signals, tight feedback loops, and less nonsense.
How do you design a game that pushes back without cheating?
Start with a rule. Then test it hard.
That is the simple version. The real work is messier, and I’ve seen this from the inside. When teams build hard systems, they often confuse friction with depth. They are not the same. Real depth gives the player or user a fair path to mastery. Fake friction just wastes time.
- Make the core action small. In QWOP, the problem is not a huge world. It is a tiny act: running. Keep the unit of interaction tight. When I reviewed tools at scale, the best ones did one thing cleanly and built outward from there.
- Tie failure to learning. Every crash, wobble, or fall should teach something. If failure only stings, the player quits. If it reveals a pattern, they stay. This is the same reason good incident reviews matter in engineering.
- Keep the rules stable. Players can accept harsh systems. What they hate is inconsistency. That applies to code, too. A flaky platform is a liar in a trench coat.
- Use humor, but do not mock the player. Foddy’s games can be funny, but they rarely feel cruel. The joke is usually on the system or the human habit of overconfidence. That difference matters.
- Respect persistence. Hard games can become grindy if they only repeat pain. Give the player tiny wins. Give them markers of progress. Even a little ridge in the mountain matters.
- Test with fresh eyes. When I was at Microsoft and later at Amazon, I saw elegant code fail because the team had gotten used to its own habits. Same thing here. Fresh testers expose bad assumptions fast.
- Do not lie about difficulty. If your game is punishing, admit it. If your controls are unusual, own that choice. Players can smell fake accessibility talk from a mile away.
- Check the moral shape of the work. This sounds lofty, but it is not. Are you asking the player to grow, or just to suffer? Are you respecting their time? Good craft cares about human dignity.
For readers who like the human side of tech, this career advice for software engineers lines up with the same theme: patience, feedback, and honest self-review.
Here’s the kicker. A game like this cannot rely on one clever trick. It has to hold together as a whole. Controls, pacing, visual cues, sound, and failure states all need to serve the same idea. If one part lies, the spell breaks. That is true in software systems, and it is true in game design.
How do Bennett Foddy’s games compare with mainstream games?
They are almost opposites.
Most mainstream games reduce friction. Foddy adds it. Most mainstream games want you to feel powerful quickly. Foddy wants you to earn that feeling, if you get it at all. That difference is not just about taste. It is about design philosophy.
| Aspect |
Bennett Foddy’s Games |
Mainstream Competitor Style |
| Core goal |
Make effort visible |
Make success feel smooth |
| Controls |
Often awkward by design |
Usually polished and familiar |
| Failure |
Frequent, educational |
Often minimized or hidden |
| Player emotion |
Frustration, then growth |
Comfort, then momentum |
| Replay value |
High for mastery-seekers |
High for broad audiences |
| Design message |
Struggle can teach |
Smoothness sells |
| Risk |
Some players quit early |
Some games feel shallow |
That table is blunt because the truth is blunt. Most games do not want to scare off players. They want retention. Foddy’s work is narrower, but deeper for the right crowd. It asks a player to sit with discomfort long enough to learn what the discomfort means.
I’ve seen a similar split in products. One tool tries to please everyone and becomes mush. Another tool makes a clear choice and serves a real need. The second one may irritate casual users, but it often has a stronger spine.
There is also a lesson in audience fit. Foddy’s games are not for everyone, and that is fine. Not every tool should be for everyone. A hammer is not a spoon. The older I get, the more I respect software, art, and games that know their place.
If you want a broader angle on tools and user behavior, this guide to developer tools and reviews is useful because it shows how different users value different forms of friction. Some want speed. Some want control. Some want both, which is where the hard work starts.
What mistakes do creators make when copying this formula?
They copy the pain and skip the point.
That is the usual failure. A lot of teams see Foddy’s success and think, “Ah, people like punishment.” No. People like meaning. They like mastery. They like the feeling that effort changed them. Strip that away and you are left with an annoying toy.
- Mistake 1: Making controls bad without purpose. Awkward controls can work if they create a clear lesson. If they just annoy people, the design is weak.
- Mistake 2: Confusing difficulty with depth. More retries do not equal more insight. A broken boss fight is not philosophy.
- Mistake 3: Ignoring pacing. Hard games still need rhythm. People need breathers. Even saints needed silence.
- Mistake 4: Mocking the player. Humor is fine. Sneering is not. Players know the difference right away.
- Mistake 5: Failing to reward growth. If the player gets better but the game gives them nothing in return, the loop dies. Give them some sign of progress.
- Mistake 6: Overexplaining. Too much tutorial text kills tension. Let players discover some things. Let the system speak for itself.
I have little patience for the common advice that says, “Just make it hard and people will love it.” That is lazy. Hardness without structure is junk. In engineering, we call that technical debt with a fancy hat on. In games, it is just bad design.
The better question is, “What does the struggle reveal?” If the answer is nothing, stop. If the answer is attention, patience, or a deeper read on the player’s own habits, you are closer to the mark.
This also touches ethics. We are stewards of other people’s time. That matters. Whether you build a game, a product, or a platform, you should not waste hours for sport. A little pain can teach. Pointless pain is just poor workmanship.
Frequently Asked Questions
Why are Bennett Foddy’s games so hard?
Because the difficulty is the design, not a side effect. His games use awkward control, strict physics, and little margin for sloppy input so players must learn patience and precision over time.
Is Getting Over It meant to be frustrating?
Yes, but not only for shock value. The frustration is part of the lesson. The game asks whether you can keep going when progress is fragile.
What is Baby Steps about?
It is a physics-based game about walking, balance, and control. The point is not speed. The point is learning how movement works one step at a time.
Are Foddy’s games good for game designers to study?
Absolutely. They are strong examples of focused design, feedback loops, and the use of failure as a teaching tool. They also show how to build a game with a clear point of view.
Final Thought
I like games that respect effort.
That is why Bennett Foddy’s work keeps sticking in my head, years after the first rage-filled clips made the rounds. The games are sharp, odd, and sometimes maddening, but they are never lazy. They ask for attention. They ask for discipline. They ask the player to accept that growth usually comes with bruises.
When I think back on my own years in software, from Google to Microsoft to Amazon and even Zulily, the best systems were rarely the slickest ones. They were the ones that taught clearly, failed honestly, and treated users like thinking people. That is the quiet power in Foddy’s design. It does not flatter the ego. It forms the player.
And maybe that is the real value here. In a world that sells speed and comfort at every turn, a game that says “slow down, learn the shape, try again” can feel almost radical. Not because it is loud. Because it is true.
That is enough for me, Ermenildo V Castro.