Hi! I'm a backend engineer (~8 YOE) with strong backend & DevOps experience and decent frontend skills. Looking for a backend or backend-leaning full-stack role.
I worked at Automattic (US), the company behind WordPress; fully remote, async teams across the globe.
I've been part of teams focused on speed and rapid iteration, and I've also worked on high-quality systems where long-term maintainability and reliability matter the most. I believe this mix of experience has helped me develop a good sense of where each fits best and has enabled me to adapt quickly based on context and requirements.
I've built and maintained time-sensitive, high-throughput, distributed services (millions of ops daily) and owned features and small- to mid-sized projects end-to-end from design to deployment. I do my best working autonomously, and I like to think of myself as a generalist.
Most of my career has been in large enterprises (7+ YOE), but I've also done a fair amount of freelance work (around 1 YOE) for clients.
I have a couple of small open-source projects on GitHub.
I've seen a couple of power users already switching to Pi [1], and I'm considering that too. The premise is very appealing:
- Minimal, configurable context - including system prompts [2]
- Minimal and extensible tools; for example, todo tasks extension [3]
- No built-in MCP support; extensions exist [4]. I'd rather use mcporter [5]
Full control over context is a high-leverage capability. If you're aware of the many limitations of context on performance (in-context retrieval limits [6], context rot [7], contextual drift [8], etc.), you'd truly appreciate Pi lets you fine-tune the WHOLE context for optimal performance.
It's clearly not for everyone, but I can see how powerful it can be.
Pi is the part of moltXYZ that should have gone viral. Armin is way ahead of the curve here.
The Claude sub is the only think keeping me on Claude Code. It's not as janky as it used to be, but the hooks and context management support are still fairly superficial.
Traditional systems (git blame, review history, ticket links) tell you who committed or approved changes, but not whether the content originated from an AI agent, which model it used, or what prompt/context produced it.
Agent Trace is aiming to standardize that missing layer so different tools can read/write it consistently.
Once exercise becomes a habit, it's very easy to do even on days when your mood is terrible. A strict routine (initially) is the trick to making things easier forever.
You definitely want to build that habit when you're at your best.
Interesting, that is good to know. I have definitely experienced Codex fumbling really easy UI tasks so that will be worth giving Claude a try for those.
People keep looking for the "one underrated skill" as if startups had a secret cheat code. In reality, success comes from balancing messy tradeoffs and learning fast under uncertainty.
The real underrated skill is realizing there isn't one.
reply