About
DWMM Holdings is a small engineering company that builds its own products: firmware, developer tools, design automation and business software.
The person
Replace this with your own introduction: who you are, your engineering background, and what you were doing before this company existed.
Two or three short paragraphs is plenty. The rest of the site already shows the technical range, so use this space for what a list of repositories can’t tell people, like your history and how you like to work.
The business
Replace this with what DWMM Holdings is as a business: how it’s structured, what it sells or licenses, who it works with, and where it’s headed.
If you take contract work, say what kind, and at what stage of a project you’re most useful.
How the work gets made
Every project starts as a written spec, and the spec stays in charge after the code shows up. Each repository has a build plan with its current status, a log of every place the implementation changed course from the plan, and a handoff note that describes where things stand today, unfinished parts included.
That habit is how one shop can cover this much ground without everything being shallow. It also makes coding agents worth using. If an agent can pick up a spec and follow it, so can a new engineer.
The hardware works the same way. The STM32 platform doesn’t use ST’s HAL or any CubeMX-generated code. When something goes wrong close to the silicon, I want to be able to open the file and fix it myself instead of waiting on a vendor.
Principles
- Own the layer underneath
- A hand-written HAL instead of a vendor SDK. A double-entry ledger instead of a table of transactions. Native KiCad files instead of a proprietary format. If I own the foundation, I can fix it.
- Say what isn’t done
- Every repository keeps a status table listing what’s built and what isn’t. If a project on this site is marked "prototype", that’s what it is.
- Local first
- Transcription, media, code review and simulation all run on hardware you control. When something does depend on the cloud, there’s a reason for it.
- One system
- The four business apps share one tenancy, one component library and one set of design tokens. The build checks this, so they can’t slowly drift into four separate products.
Talk to the person who built it
There's no sales team. Email comes straight to me.
dmoore@