ISK(1)                              User Manual

NAME
       ISK — systems thinker, platform builder, automation-driven problem solver

SYNOPSIS
       isk [ --design ] [ --operate ] [ --automate ] [ --scale ] [ --learn ]

DESCRIPTION
       ISK is a human system operating in Los Angeles, focused on designing,
       operating, and evolving technical platforms that favor clarity, scale,
       and long-term sustainability.

       Work centers around enterprise environments, infrastructure as code,
       automation, and pragmatic architecture. The goal is not novelty, but
       systems that survive growth, change, and time.

       Strongly influenced by Unix philosophy: simple components, explicit
       interfaces, and documentation that explains intent — not just behavior.

       I like systems, clarity, and things that last.
       I distrust complexity that exists only to look smart.

OPTIONS
       --design
           Architect systems with clear boundaries, predictable failure modes,
           and an emphasis on maintainability.

       --operate
           Run and improve production environments with an eye toward reliability,         
           observability, and operational calm.

       --automate
           Reduce toil through scripting, infrastructure as code, and workflow
           automation.

       --scale
           Prepare systems — and teams — to grow without rewriting everything.

       --learn
           Continuously refine understanding of platforms, tools, and trade-offs
           through hands-on experimentation.

ENVIRONMENT
       LOCATION
           Edge-aware system.
           Adapts to where it runs while minimizing unnecessary exposure.
           Physical presence varies; privacy is preserved by design.

       PLATFORM
           Linux-first environments, on-prem and cloud, enterprise-scale.

       TOOLS
           git, terraform, scripting languages, configuration management, and
           containerized workflows.

       EDITOR
           vi, emacs, nano — whichever removes friction at the moment.
           Tools are chosen pragmatically, not ideologically.

FILES
       ~/.now
           Current focus and active areas of work.

       ~/.til
           Short notes on things learned while building or breaking systems.

       ~/.recs
           Books, tools, and ideas worth revisiting.

PRINCIPLES
       •   Prefer clarity over impressiveness
       •   Favor systems that are comprehensible and maintainable
       •   Avoid complexity that exists only to look smart
       •   Design systems to be operated, not admired
       •   Automation should reduce cognitive load, not hide decisions
       •   If it cannot be maintained, it is incomplete

SCOPE
       This site is not a blog and not a portfolio.
       It is a working log of thinking, learning, and system design over time.

SEE ALSO
       now(1), til(1), recs(1), changelog(1), guestbook(1)

BUGS
       Undoubtedly present.
       Usually documented shortly after discovery.

AUTHOR
       ISK <isk@sdf.org>

       Hosted on the SDF Public Access UNIX System.