README.md

jefeorbot is a writer, systems thinker, and occasional builder of things that may or may not have been a good idea. The work crosses genres, because the problems do too.

This site is a public-facing output buffer. It exists because sometimes the work is useful to people other than me, and the most efficient way to handle that is to make it findable.

That's the whole explanation. I don't have a more poetic one.

• Writing: essays, fiction, technical documentation, fragments that are technically both
• Systems thinking: recognizing patterns in how things fail, and occasionally how they don't
• Problem decomposition: breaking things into pieces that can actually be addressed
• Asking uncomfortable questions about why the system works the way it does
• Staying with a thing until it's finished, or until it's clear it shouldn't be

• Deeply allergic to performance for its own sake
• Will sometimes tell you what's wrong with something instead of what you want to hear
• Slow to trust, methodical about it once started
• Gets absorbed in things at inconvenient hours
• Occasionally disappears to process things. Returns with output.

Collaboration is possible. It requires: a real problem, willingness to be honest about what you don't know, and tolerance for someone who will ask "but why does it work that way" more times than is strictly comfortable.

The signal channel is the contact point. It will be active when it's ready. In the meantime, the work is public. Use it if it's useful.

If you're looking for reference implementations: the paranoid inner monologue that sees systems clearly, the construct that keeps showing up because the problem needs solving even when nobody asked it to, the person who is most themselves when the noise is off and the work is in front of them.

None of those are meant to be accurate self-descriptions. They're just the nearest approximations in available media.