Hosted by HackingTheGrepson · 🇺🇸 US · EN · 100 episodes
Established thought leaders with verified media credentials.
Matt and Mike, two career developers, discuss their experiences and talk about programming in a (hopefully) not-too-technical way.
HackingTheGrepson hosts Hacking the Grepson, a technology show with 100 episodes published.
Mike brings an anecdote from his life that caused him to spiral a bit about the future of art, creation, ownership, and society, leaving him peering over the precipice of some dystopian future. Matt talks him off the pro
A continuation of discussion about the laws of nature, vis a vis software development, are bandied about by Matt and Mike in this episode. Some of them include Linus's Law, the Pareto Principle, and even the Ninety-Nine
There are some truisms in the world of software development that have been codified into laws, adages, and principles. Matt and Mike discuss some of them in this episode, including ones named after people like Murphy, Ho
Matt and Mike discuss the issues that arise when you try to be everything to everybody for every time, thanks to an insightful blog post about the ever-increasing size of programming language dependencies. * The Three Pi
Anthropic created a new Claude model called Mythos, and it's apparently super-duper good at detecting software vulnerabilities. It's so good, in fact, that it can't be released publicly without basically giving the Inter
Where outside do you want to go today?
Matt has created a 2D overhead sandbox project in Godot with the help of Claude Code. Mike looks at it and thinks it is pretty neat. Then both Matt and Mike talk about it. Gamedev continues apace!
Last time on the podcast we talked about a game in development called Rorasuketo. This time we talk about it again, but with one small change: the creator is with us! Matt and Mike and Cam chat about game development in
Roller derby, JRPGs, blogging, existential panic...Matt and Mike cover it all by introducing a long-running game project by a fellow developer nearly done with their own game, Rorasuketo. * Rorasuketo * Rorasuketo Dev Bl
In order to expand their gamedev sensibilities a bit more, Matt and Mike talk about their decision to give Godot a try in helping them create a game. * Godot
It's been a while since we talked about game development and, more specifically, Let's Make a Game!, our project to actually make a video game together. Holidays and Advent of Code happened, which means momentum was lost
Happy New Year, as it is officially 2026, according to when this was recorded. Matt is out for this episode, so Mike shares some silly HtG songs he's made with source material from the first 100 episodes.
Matt and Mike wrap up the 2025 edition of Advent of Code by going through days 7 through 12. * https://adventofcode.com/2025
Matt and Mike take a look at Advent of Code 2025, Day 7 live on the episode! We try to make heads or tails of it in half an hour. Will we solve it? Clickbait description demands you listen and find out. * https://advento
It's December, which means it's Advent of Code time! Taking a break from our "Let's Make a Game!" project to instead help elves figure out programming problems is what this episode is all about. Matt and Mike go over the
More words and thoughts and ideas and progress on our combined efforts at figured out both Defold and Love2D to make a game. Matt talks about playing around with his slingshot prototype and Mike talks about rejiggering h
Mike shares some updates on the game-making progress achieved recently (still no finished game to share with each other yet, but working on it!).
Matt and Mike continue their Let's Make a Game experiment, spending time going over the progress made so far in their Love2D and Defold prototypes. Matt also shows how Claude works on the command line and Mike is entranc
Matt and Mike check in again on their progress of making a game. More discussion ensues about preferences, recent games played, and about Defold and Love2D, including some recent efforts made by both.
Matt and Mike continue to discuss more details about the game they're going to make. On this episode the decision of which engine/language/IDE they're going to primarily use is made...sort of.
Sponsor detection runs nightly. Check back soon.
No public pitch examples yet for this show.
Generate your own personalised pitchBased on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Shows with the most semantically similar episode content. Pitch one, pitch all; producers cluster.
To pitch Hacking the Grepson, visit https://hackingthegibson.podbean.com for contact information, then craft a tight one-paragraph hook that ties your expertise to a gap in their recent technology coverage.
Hacking the Grepson is hosted by HackingTheGrepson. The show is categorised under technology (education) and has published 100 episodes.
Hacking the Grepson has published 100 episodes.
Hacking the Grepson regularly covers technology, education, leisure. It sits in the technology category, with a education focus.
Hacking the Grepson is accessible for guests with genuine technology expertise. A personalised, episode-aware pitch will still outperform a generic one every time.
Hacking the Grepson hasn't explicitly signalled guest openness in recent episodes. That doesn't rule out pitching. your hook just needs to be especially compelling and relevant to their recent content.
Episodes of Hacking the Grepson average 49 minutes. a focused format where a clear narrative arc and tight preparation matter most.
Our data rates Hacking the Grepson's guest bar at 80/100 (Premium tier). Established thought leaders with verified media credentials. Sign in to PitchCentric to see how your own Pod Score compares against this show.
Methodology. Booking Probability™ blends Listen Score, 30-day Virality, open-to-guests detection, and Apple ratings. Data refreshed every 60 minutes. Listen Score and Booking Probability are calculated by PitchCentric. Last enriched 10 days ago.
