Skip to content
View myshkin451's full-sized avatar

Block or report myshkin451

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
myshkin451/README.md

Myshkin 451: agents, knowledge systems, personal publishing

www.myshkin451.com / repositories

A Small Public Room

Somewhere between Prince Myshkin and 451 degrees, I keep a small room for attention: notes, tools, and questions that refuse to become slogans.

I work around agents, knowledge systems, and personal publishing. I am interested in software as a way of thinking in public: not just shipping artifacts, but leaving better traces for the next person who has to understand the room.

This page is deliberately not a trophy case. The public repos are part workshop, part notebook. The real direction is still being made by building, reading other people's code, and contributing where I can.

Current Coordinates

Axis What I keep circling
Agents Collaborators with memory, limits, and context; not mascots, not magic.
Knowledge systems Retrieval, notes, schemas, and the craft of making useful context reappear.
Personal publishing A website as a thinking room, not a billboard.
Open source Small, concrete PRs; quiet fixes; writing that lowers the cost of understanding.

Working Questions

A tool is a thought with handles.

Memory is useful only when it changes what you notice next.

Public writing is not self-display; it is a way to make thinking accountable.

A good contribution leaves the room easier to work in.

Open-Source Posture

I am trying to become useful in public without performing usefulness too loudly.

That usually means:

  • reading before changing;
  • keeping PRs narrow enough to review;
  • explaining tradeoffs instead of selling certainty;
  • improving documentation when code is not the only problem;
  • treating maintainers' attention as a finite resource.

Field Notes

now
  learning from mature projects
  building small agent and RAG tools
  shaping a long-lived personal website
  collecting better habits for context, memory, and review

later
  fewer demos, more durable systems
  fewer slogans, more instruments

quiet work, clear traces, useful context

Popular repositories Loading

  1. code-rag code-rag Public

    Python 3

  2. vibe-harness vibe-harness Public

    Lightweight repository harness for AI coding projects: context, progress, verification, and agent handoffs across sessions and tools.

    Python 1

  3. CPlusPlusPrimer_Exercise CPlusPlusPrimer_Exercise Public

  4. Assignment2 Assignment2 Public

    Python

  5. Assignment3ISML Assignment3ISML Public

    Python

  6. Myshkin451-blog Myshkin451-blog Public

    Vue