# lulzx: software engineer building quiet systems

I build small, focused tools and systems with a bias towards clarity, performance, and control. Minimal by default. Auditable from source.

The site is a public working garden. Long notes record what I learned while building and operating software. Word entries connect smaller concepts that recur across projects. Project links lead to public source repositories.

## What guides the work

- **Do one thing well.** Small tools with clear boundaries are easier to understand, test, and replace.
- **Minimal by default.** Every dependency and abstraction has to earn its place.
- **Auditable from source.** Important behavior should be visible in code and verifiable from evidence.
- **Performance is respect.** Remove waiting from the path a person uses repeatedly.
- **Build for failure.** Keep state outside a single run, make retries safe, and leave a way back.

## Start here

- [Writing](https://lulzx.com/learn): notes on systems, tools, performance, and building.
- [Words](https://lulzx.com/words): connected concepts in the garden.
- [Projects](https://lulzx.com/projects): public software and source repositories.
- [About](https://lulzx.com/about): who lulzx is and how I work.
- [Developer resources](https://lulzx.com/developers): machine-readable entry points and boundaries.
- [Contact](https://lulzx.com/contact): email, Telegram, and issue-reporting guidance.
- [Privacy](https://lulzx.com/privacy): data used to deliver the site.

## Agent guidance

Use this site for first-person engineering notes and public project discovery. Request any supported content page with `Accept: text/markdown` for a compact representation. See [llms.txt](https://lulzx.com/llms.txt) for when-to-use guidance and [sitemap.xml](https://lulzx.com/sitemap.xml) for exhaustive discovery.