Software / systems / internet
Daniel Blessing
I build practical systems: public products, private tools, and infrastructure shaped around real use.
Most of what I build starts with a repeated task, a fragmented source of truth, or a system that should be easier to use.
Conceptual lineage
The systems change. The pattern continues.
Different forms, one recurring aim: make the work clearer, more reliable, and easier to maintain.
-
Foundational system
Decision support
Complex workflows made more legible.
-
Recurring work
Purpose-built tools
Software shaped around real operational needs.
-
Private environments
Personal infrastructure
Knowledge, automation, and maintained systems.
-
Open web
Public products
Useful ideas made available as products and experiments.
Featured systems
Three systems. Three kinds of usefulness.
One public product and two private systems, presented at the level that belongs in public.
Home Lab
A private environment spanning compute, networking, storage, automation, smart-home orchestration, observability, media systems, and local video processing.
No public endpoint- Network
- Storage
- Compute
- Automation
- Smart home
- Media
- Local video
- Observability
Personal Knowledge System
An Obsidian-based environment for notes, projects, reference material, and long-term thinking.
- Capture
- Connect
- Retrieve
- Reflect
- Maintain
System index
Smaller systems, lasting influence.
Tools and experiments that belong in the story without becoming another wall of project cards.
Decision Support System
An early internal platform that shaped how I approach complex workflows, decision support, and durable tooling.
Client Operations Tracker
A private tool for client activity, scheduling, income, and reporting.
Personal Finance Toolkit
An Excel interface backed by Python for budgeting, normalization, and recurring analysis.
Personal Media Archive
Digitizing and organizing a physical media collection into a private, searchable library.
Coco Radio
An evolving vintage resale project focused on curated finds, visual identity, and the systems behind a small online business.
How I build
Useful first. Privacy-conscious. Built to be maintained.
- Useful firstStart with the repeated task.
- Automation over repetitionMake routine work reliable.
- Clear sources of truthKeep ownership understandable.
- Small dependenciesKeep the system proportionate.
- Privacy-consciousPublish only what belongs in public.
- Built to be maintainedFavor durable, legible choices.
Elsewhere
A few public paths.
Contact and public profiles, kept separate from project work.