What's in the Bag?

Golfers know the phrase "what's in the bag?"—it’s shorthand for talking about the tools they trust when they head out on the course. From drivers to wedges to that one beat-up hybrid they swear by, every club has a role, and every bag tells a story.

Well, I think developers are a lot like golfers. We each carry a different set of tools. Some we've used for years and know inside and out. Others we’re testing out, seeing how they perform in different conditions. Our tools define our approach—and how we solve problems.

So I’m kicking off a new series on my blog called What’s In the Bag? In each post, I’ll explore a specific tech stack or framework, build something small but meaningful with it, and share my honest thoughts along the way. No hype. No gatekeeping. Just real-world experience with a touch of craft and curiosity.

---

First Up: Deno + Fresh

The first stack in the bag is something I’ve been meaning to explore more seriously: Deno and the Fresh web application framework.

For those unfamiliar, Deno is a modern JavaScript/TypeScript runtime created by the original creator of Node.js. It comes with built-in tooling (like testing and linting), strong security defaults, and native TypeScript support out of the box. Fresh, built on top of Deno, is a full-stack web framework focused on speed and simplicity. It uses "island architecture" to keep client-side JavaScript minimal by default, enabling ultra-fast performance and a better developer experience.

To test this stack, I’ll be building a collaborative to-do app—inspired by a showcase repo from the Deno team that uses server-sent events (SSE) to keep browser tabs in sync. The twist? Multiple users can view and update the same task list in real-time. No account system, no database (yet)—just a live playground for learning.

I'll cover:

• Project setup and routing in Fresh

• How SSE works and why it's simpler than WebSockets for some use cases

• Structuring shared state in a collaborative UI

• What felt intuitive, what felt clunky, and what I’d do differently next time

---

Why This Matters

I’m doing this for a few reasons:

• To stay sharp by evaluating new tools

• To create public artifacts I can point to

• To rebuild the habit of sharing what I learn

And let’s be honest—like any golfer trying out a new driver, sometimes it’s just fun to see what happens when you take a swing.

If you're curious about Deno, Fresh, or just like hearing how developers think through new stacks, I hope you’ll follow along.

---

Join the Conversation

Have you tried Deno or Fresh? Got a tech tool you think should be in the bag? I’d love to hear what you’re exploring or experimenting with. Drop a comment, tag me on LinkedIn, or share your “what’s in the bag” story.

First build drops later this week.

Thanks for being here.