Where I show up

I show up in the open

Not a Discord, not a paid forum, not a private circle. Everything I learn lands in a public repository, a long-form blog post, a wiki, or a thread where someone else can push back on it. If you want to find me, this page is the index.

Public repositories

83+

Rich blog posts and playbooks

ongoing

Threads on Hacker News and beyond

Eight surfaces, all public

These are the surfaces where I actually exist. Pick the one that fits your question. None of them ask for an account.

GitHub

@sarmakska

Eighteen public repositories, MIT-licensed. Every repository has a wiki with architecture, decisions and a roadmap. Issues and pull requests are the primary surface for feedback.

The blog

/blog

More than eighty rich posts on engineering, AI infra, distributed storage and the daily reality of running production systems. Charts, comparison tables, citations. Footer on every post invites readers to flag bad numbers.

The open-source body of work

/open-source

Eighteen repositories grouped by category: AI infrastructure, coding agents, storage and consensus, sandboxing, ops and infra, voice. Every one has a published wiki and a verification gate.

Playbooks and blueprints

/playbooks

Repeatable runbooks for the operations I do every week. Postgres migrations, Cloudflare rollouts, observability on day one, RLS audits. Written so they survive me forgetting the detail next month.

Hacker News and forum threads

Public conversation

When a post goes up on Hacker News, Lobsters or the relevant subreddit, I read every comment. The thread under the post is where the most useful pushback lands. I keep replying as long as the thread is active.

Insights and labs

/insights · /labs

Shorter notes that did not need a long-form post. Experiments mid-flight. Half-formed opinions I want feedback on before they harden into a blog post.

linkedin.com/in/sarmalinux

Long-form professional posts and the place hiring managers reach me first. UK-based, open to a permanent full-time senior engineering role from a company. PAYE only.

Email

hello@sarmalinux.com

For anything that does not fit a public thread. I read every message. Replies usually go out the same day, sometimes the next.

How I treat the public surface

Four rules that keep these surfaces honest. They are the reason I can keep them open.

Public by default

If a question is interesting enough to answer, it is interesting enough to answer in public. The same answer helps the next person who searches for it.

Threads, not gates

No paid tier, no closed Discord, no invite list. If you can find the post, you can read the answer and push back on it.

Numbers cite a source

Every benchmark on the blog says where it came from. The transparency footer invites a correction if the source is wrong.

I read every comment

Hacker News, GitHub issues, blog comments, email. If you took the time to respond, I take the time to read it.

Want to work together?

I am open to a permanent full-time senior engineering role from a company that values the work above. The path is /hire-me. For everything else, the channels on this page already cover it.

Hire me See the open-source work