Josh

Every agent framework guards your tools with if-statements. I replaced mine with a mathematical proof. www.joshtuddenham.dev/blog/agent-s...

Another good one is "what tradeoffs did you make when writing this?"

I have also prompted AI to write documentation for what it has built (pointing it at great examples of documentation elsewhere) and that has really helped for me.

I wrote about this recently too, I think it is the biggest thing we will need to grapple with in agentic coding. I used a slightly different term (speed vertigo) but it's the same thing:

joshtuddenham.dev/blog/vertigo/

This is absolutely deranged. Imagine being that disconnected from the trials and tribulations of your employees.

In short, I think allowing users to create a 'personality' for their AI agent, and have it speak to them and treat them in a certain way could very easily lead to even more AI induced psychosis than we already are seeing.

I have noticed this too. Measured takes seem to have nowhere near as much virality as either boosterism or doomerism.

ChatGPT promised to help her find her soulmate. Then it betrayed her ChatGPT sent screenwriter Micky Small down a fantastical rabbit hole. Now, she's finding her way out.

Lots has been written about the security implications of Moltbot/Openclaw, but I think even more dangerous is soul.md. As stories like this show, adding memory to chatbots can lead to profound impacts on users. I dont think we have sufficient guardrails in place yet.

www.npr.org/2026/02/14/n...

I really enjoyed this article, thought it was really even handed and well reasoned.

You're already building Petri nets. You're just building them badly. (alt title - 'we are all building state machines wrong')

joshtuddenham.dev/blog/petri-n...

Screenshot of a complex mathematical theorem from the Elastic Hashing paper defining an injection function phi.

the notation in the 'elastic hashing' paper looks like the Rosetta stone to me.

​implemented it in zig to see if it actually survives 99% load. (it does, mostly).

joshtuddenham.dev/blog/hashmaps/

This is diabolical. Sign me up!

Great work, had been hoping for this!

I just completed "Printing Department" - Day 4 - Advent of Code 2025 #AdventOfCode adventofcode.com/2025/day/4

Love a grid puzzle. My answer is verbose (I know I could probably do the grid checking with a loop) but works:

github.com/joshuaisaact...

I just completed "Lobby" - Day 3 - Advent of Code 2025 #AdventOfCode adventofcode.com/2025/day/3

My solve here:

github.com/joshuaisaact...

Feel like I got the first part surprisingly quickly, then took over an hour on the second. Kept going OOB / running out of length in my byte array.

I've completed "Secret Entrance" - Day 1 - Advent of Code 2025 #AdventOfCode adventofcode.com/2025/day/1

Part 2 of this a classic edge case puzzle, my solution is definitely ugly, but got there in the end:

github.com/joshuaisaact...

I just shipped Music Round for the @tanstack.com × @convex.dev hackathon. - a live multiplayer (and solo) music guessing game with three gameplay modes (a daily, a battle royale and a playlist based).

Music Round Daily #321
✅ ✅ ❌ ❌ ✅
Score: 2,267/5,000

App: tranquil-bombolone-5e7a31.netlify.app

Like George Foreman with his grill, I too have put my name on a product.

Introducing Josh Desk!

Try it out: joshdesk.live

Please excuse the logo - turns out "designer" isn't on my LinkedIn skills list for a reason 😅

Express Error Handling: Because Things Will Go Wrong | Joshua Tuddenham | Full-Stack Engineer From try-catch hell to elegant error handling: A deep dive into implementing robust error handling in Express with TypeScript, custom error types, and global middleware.

Spent some time improving error handling in Wooster (my AI trip planning app) and wrote about the journey. From simple beginnings:

if (error) {
console.log(error);
}

To typed errors, proper logging, and middleware.

Here's the full story: www.joshtuddenham.tech/blog/wooster...

Advent of TypeScript Advent of TypeScript

I've completed 🎅Santa Wants Housing Data - Advent of TypeScript 2024 Day #3 adventofts.com/events/2024/3

From console.log to proper structured logging with Pino 📝

Just published my latest piece on taming chaos in Express backends.

If you've ever littered your code with console.logs (we all have), read how I cleaned up my act with proper logging.

joshtuddenham.tech/blog/wooster-logging

debugging prod: why are my DB queries returning duplicates?

*3 hours later*

oh my CI/CD never deletes old files and I've been running a horrifying hybrid of old and new code for a month

nothing like discovering your prod server is basically a code necropolis where old functions refuse to die 💀