← Tech Stack
Tech Stack / Software

Software

The daily software layer behind Viggo Meesters’ workflow: Obsidian, Hermes, GitHub, Vercel, Telegram, and delivery tools.

snapshot 2026-06-234 entries
Current shape
Obsidian

Human-facing vault interface for Markdown notes, links, and durable context.

Hermes

Agent runtime and command bus around tools, sessions, scheduled tasks, and skill routing.

GitHub + Vercel

Public repos and static deployments for demos, website pages, and project artifacts.

Telegram

Fastest interface for commands, capture, steering, and delivery.

Why this belongs in the stack
Role in the system

Software is the working environment around the vault, repos, browser, documents, and communication channels.

Why it matters

It matters when a daily app or service becomes important enough that readers need it to understand the workflow.

What stays out
Avoid app inventory sprawl

Skip incidental utilities and one-off experiments.

Prefer stable categories

Group tools by job: writing, communication, storage, browsing, planning, and review.

How it earns a place
Why it is included

Software belongs here when it is a stable part of the work loop: writing, communication, knowledge management, design, or project delivery.

What makes it useful

A software entry earns its place when removing it would change how work is captured, reviewed, published, or resumed.

Why it matters

It matters when a daily app becomes the default for writing, planning, communication, vault work, or publishing; remove tools that are only historical preferences.

Concrete example
In practice

Obsidian is listed because it is the human-facing editor for the vault, while the vault schema and validation logic belong to the Personal Knowledge System pages.

What stays private
What stays private

Mention durable workflow roles, not account details, private workspaces, personal data locations, or app-specific configuration that would become stale or sensitive.