Why I Launched Dongle: Making the Terminal Feel Like Magic

Jeremiah Israel — Mon, 23 Feb 2026 10:11:17 +0000

Last weekend, I hit a breaking point with the cd command.

As developers, we spend half our lives in the terminal. But for some reason, we still accept the "manual labor" of typing out deep directory paths just to move between folders.

I was tired of the stress of manual pathing, so I built Dongle.

The Problem: "Pathing Fatigue"

Whenever I needed to move to a deep directory to run a command, I found myself doing the cd ../../ ritual. It’s slow, it’s prone to typos, and it breaks your "flow state."

The Solution: Just Get There

I wanted a tool where I could just type a folder name and jump there instantly. No memorizing paths, no ls hunting.

Dongle handles the logic in the background so you can focus on the code, not the navigation. It’s simple, lightweight, and purpose-built for speed.

Today is Launch Day! 🚀

I’ve decided to share Dongle with the world by launching on Product Hunt.

Building this was a reminder that if something in your workflow feels broken, you have the power to fix it. If you're a terminal power user (or want to be one), I think you’ll really enjoy using this.

How you can help:

Check it out on Product Hunt: https://www.producthunt.com/products/dongle-jump-between-folder-structures?utm_source=other&utm_medium=social
Star the repo on GitHub: https://github.com/jeremiahseun/dongle
Give feedback: Is there a feature you'd love to see? Let me know!

Thanks for being part of my "learning in public" journey. Let's kill the cd fatigue together.

What’s the most annoying "small" task in your dev workflow? I’m looking for my next weekend project!

Beyond the Code: What PostHog Taught Me About Systems and Culture

Jeremiah Israel — Sun, 22 Feb 2026 18:46:35 +0000

Lately, I've been an active contributor to the mobile side of the PostHog repository. While I went in to contribute code, I ended up walking away with a completely new perspective on how to build—and live.

1. Automation at Scale

As I dug into the mobile repo, I was struck by how much they prioritize automation. For anyone interested in scalability, PostHog is a goldmine.

Their Co-CEO, James Hawkins, recently talked about the "State of the Hog," where he emphasized making software feel "much more automated." Seeing this vision actually implemented in their GitHub Actions and development scripts has been a lightbulb moment.

2. The Culture is the Code

It’s not just about the .js or .swift files. I’ve been spending a significant amount of time diving into the PostHog Handbook.

If you haven't read it, it’s a masterclass in transparency and speed. It helped me realize that a system isn't just a set of scripts; it's the culture and the "how we do things" that allow those scripts to be effective in the first place.

3. "Systems for Me"

The biggest takeaway? I've started applying these lessons to my own life.

I’m now obsessed with building "systems for me." I’m looking at my personal workflows, my side projects, and even my daily habits through the lens of a PostHog engineer:

How can I automate this?
Where is the manual friction?
Is this documented well enough that "future me" can understand it?

Contributing to open source isn't just about giving back to the community—it's about upgrading your own operating system.

Are you building your own personal systems? I'd love to hear how you're automating your life in the comments!

DEV Community: Jeremiah Israel