Joel Pennell

About

I run DHU Labs and co-founded TeamWeaver. With AI as my collaborator I've built about fifty working projects. Before that I raised my two kids at home for nineteen years, and before that I spent seven years shipping hardware and software where music, computers, and people meet.

How I build now

AI collapsed the distance between thinking of something and building it. I was pushing at that before the tools were any good, generating code in a chat window and pasting it into files by hand.

I work with several AI agents and they do the implementation, some of it on hardware I built here for running models locally. I do what I've always been better at: deciding what's worth building, holding the scope, and judging whether the thing actually works. How I do that is in four steps on the home page.

The projects cover a lot of ground: a revenue-intelligence tool that turns a sales team's emailed updates into deal records, a personal medical AI that runs locally so health data never leaves the house, a security scanner, a field-coverage app for enterprise field officers. They range that widely because I would rather learn a new domain than repeat one I already know. Most are private or built for someone else's business, so you can't browse them all. I'm glad to talk through any of them.

Where the work is

Founder

DHU Labs

Businesses bring me something slow, manual, or confusing, and I tell them whether software would help, including when the answer is no. When it would, I build it while they watch it take shape.

The products and the custom work are at dhulabs.com.

Co-founder

TeamWeaver

The company I co-founded to measure how teams actually collaborate. It was the first thing I built this way, and I built all of its technology, both versions.

Its free tool, The Meeting Read, needs no signup, so that one you can use right now.

Everything public, one by one

The first career

I studied software at the local two-year college and learned something more useful than the degree: I love the high-level thinking about what software should be and do, and I have no love for writing it line by line.

1999

NetDrives

My final-semester internship was at Glyph Technologies, a company I already knew because their storage powered the samplers I made music with, and I could hardly believe they were right here in Ithaca. They put me on a new venture called NetDrives, where I helped build, test, and ship the Brujo, one of the first standalone consumer MP3 players: a box that played MP3 CDs on your home stereo. Part of the job was explaining to people what an MP3 even was.

Read the November 1999 review or the August 1999 announcement.

1999 to 2002

Neoware

I tested thin-client systems at Neoware, outside Philadelphia, through the dot-com years.

2002 to 2006

Glyph Technologies

I moved home to Ithaca and came back to Glyph as an engineer, on the four-person team behind the GPM-216, a peer-to-peer personal monitor mixer that ran audio over a network and split the work across modular nodes. We built the first hundred units and debuted it at AES in 2005.

Nineteen years at home

When our first kid was born, one of us was going to be at home, and I took the job. For nineteen years that was my work, including homeschooling both kids until they were ready for regular school. It was more work than any job I've had, and all of it was work nobody assigns and nobody reviews, which is most of what working for yourself asks. I kept building through all of it: workstations, music production, and AI the moment it started to matter.

Music got here first

My dad was a postal carrier and lived an hour from his work, so his commute started early and mine did too, and on those drives the radio played synth pop, early reggae, and dancehall before he dropped me off at school. I bought my first record at eleven, learned to DJ on belt-drive turntables and then Technics, and by my teens I was playing parties.

What I always wanted to know was where this music came from and how it was made. Chasing that led me through synthesizers into computers. I was sequencing MIDI on an Atari before I ever heard of BeOS. What pulled me to BeOS was the engineering: a 64-bit file system, an architecture built for media from the ground up, and the way it made the same hardware feel far more powerful than Windows or the Mac OS of the day did. I built my own dual-processor computers to run it, because a BeBox cost more than a teenager had. I put what little money I'd saved into Be stock and lost all of it. The yellow tabs on this site are BeOS window tabs.

Later I beta tested Stanton's digital DJ system, and since 2000 I've run a small electronic music label, Bumpy Records, releasing my friends' music and my own. I own almost ten thousand records. I'm also building an AI music studio.

Stone, then snow

Work started at twelve, stacking stone pallets in the summers at my stepfather's quarry, the one that supplied the stone for Cornell's early buildings.

At seventeen I put my board in my car and drove to Mount Hood, met people on my first day who took me in for the summer, and came home sponsored by Never Summer after their industry friends photographed me riding and sent the pictures in. The plan was to go professional. I taught snowboarding at my local resort, got certified, took an instructor job at a new resort in Park City, and an injury from the summer before got worse on the mountain until it sent me home for good. Home meant getting serious about software.

Get in touch

If you're building something, deciding whether to build something, or want to know whether I can help with a problem, email me. I answer.

If you're hiring, email me or reach me on LinkedIn. Résumé on request.