Operational Pain, Turned Into Tools.

This is where recurring problems become scripts, utilities, web applications, and occasionally open-source projects.

Some tools are polished. Some are experimental.

Most exist because I got tired of doing something repeatedly.

01

On The Bench

Every tool here exists because some repeated task became annoying enough to fix. The solution should never become more complicated than the problem requires.

Status: Live

Timesheet

Source Available
Annoyance

Daily timesheets are easy to forget when logging them takes more attention than the work itself.

Intent

Make time tracking ultra easy, no-brain-use, and usable even on busy days.

Tool

A personal tracker for monthly customer/project logs, kept local because one-person tracking did not need a shared system.

Useful parts
  • Start/stop timer
  • Quick manual entries
  • Monthly CSV export
  • Local backup/import
  • Backup reminders

Status: Active

Fixed Assets Survey

Source Available
Annoyance

Asset surveys should focus on collecting evidence, not managing paperwork.

Intent

Keep barcode scans, photos, notes, and exports tied to the same survey record.

Tool

A mobile-first survey utility with just enough persistence for metadata and photo evidence.

Useful parts
  • Barcode scan or manual entry
  • Asset and sticker photos
  • Duplicate check
  • CSV and photo review export
  • Shared-PIN access

Status: Live

Asset Tag Generator

Annoyance

Printable labels should not send people back to spreadsheet templates.

Intent

Make barcode label sheets fast and predictable enough that manual layout work stops being worth it.

Tool

A client-side label generator for asset tags and inventory labels, because printing sheets did not need shared storage.

Useful parts
  • ONE/BOS A9
  • 30 labels per sheet
  • Custom sheet layout
  • CSV / pasted values
  • Printable output
02

The Problem Came First

I rarely start with an idea for software.

Most tools start with irritation.

A repetitive task. A fragile process. An operational shortcut that should have existed already.

Once the friction becomes large enough, building a tool becomes easier than repeating the work.

Sometimes it becomes a script.

Sometimes it becomes a web application.

Sometimes it becomes an open-source project.

Most of the time it simply makes work better.

03

Workshop Method

Engineering is not about building software.

It is about understanding a problem, measuring it, building a tool, and improving the system.

Software just happens to be the material I use most often.

The goal is always a better system.

  1. Understand the work
  2. Measure the problem
  3. Build a tool
  4. Use it in the real world
  5. Improve it
  6. Share what is useful
04

What's Currently on the Bench

Loose parts, active builds, and notes that have not settled into finished tools yet.

Building

Tools being assembled

  • Asset Tag Generator
  • Echo MCP
  • Fixed Assets Survey
Thinking About

Problems under inspection

  • AI-assisted tool building
  • Operational automation
  • Founder architecture
Reading

Input material

Current books, articles, and research notes that help explain systems, tools, and long-term work.

05

Share What Is Useful

All public projects are available through GitHub.

Open source remains part of the lab because useful tools are easier to trust, reuse, and improve when the source is visible.

Connect on GitHub
06

About This Workshop

This is where small tools end up.

Most projects here started as real problems: a repetitive task, a missing utility, or something that was simply easier to build than to search for.

Some projects become useful. Some remain experiments. Both are welcome.

For longer-form thinking, architecture notes, and decision memory, visit nagorn.me.

Workbench materials

The bench usually has a few materials within reach.

  • Scripts and automation
  • Spreadsheets and checklists
  • Small web applications
  • Operational workflows
  • Documentation and measurement
07

How This Fits Together

Each place has a different job. Together they form a connected ecosystem for thinking, tools, business, delivery, and operations.