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.

Explore work
System field / 01 Conceptual topology

Conceptual lineage

The systems change. The pattern continues.

Different forms, one recurring aim: make the work clearer, more reliable, and easier to maintain.

  1. Foundational system

    Decision support

    Complex workflows made more legible.

  2. Recurring work

    Purpose-built tools

    Software shaped around real operational needs.

  3. Private environments

    Personal infrastructure

    Knowledge, automation, and maintained systems.

  4. Open web

    Public products

    Useful ideas made available as products and experiments.

System index

Smaller systems, lasting influence.

Tools and experiments that belong in the story without becoming another wall of project cards.

Private professional system

Decision Support System

An early internal platform that shaped how I approach complex workflows, decision support, and durable tooling.

Foundational system
Private purpose-built tool

Client Operations Tracker

A private tool for client activity, scheduling, income, and reporting.

Private tool
Private personal tool

Personal Finance Toolkit

An Excel interface backed by Python for budgeting, normalization, and recurring analysis.

Private tool
Private preservation system

Personal Media Archive

Digitizing and organizing a physical media collection into a private, searchable library.

Private system
Public vintage resale project

Coco Radio

An evolving vintage resale project focused on curated finds, visual identity, and the systems behind a small online business.

Visit site

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.