A mystery play 🔥 At first glance, the town feels welcoming. Smiling faces greet every newcomer, doors remain unlocked, and strangers offer help before it's even requested. The streets are spotless, the gardens perfectly maintained, and every conversation ends with the same reassuring smile. Yet beneath the warmth lies something unsettling.
No one seems to remember where they came from, and every resident speaks as though they share a secret they will never reveal. The clocks around town show slightly different times, and every evening, the streets fall eerily silent at exactly the same hour. Visitors notice that maps never quite match the roads, and anyone asking too many questions is politely redirected with practiced kindness.
The people are friendly—almost too friendly. Their smiles linger a little too long, their eyes seem to follow you wherever you go, and they always know your name before you've introduced yourself. Nothing openly threatening ever happens, but an invisible tension hangs in the air, making it impossible to relax.
The place isn't haunted by ghosts or monsters. It's haunted by the feeling that everyone belongs there—except you. And once you arrive, leaving may not be as simple as finding the road out.
I’ve been razzmatazzing and flibbertigibbeting with Claude Code and somehow ended up with a new yels.dev.
It finally feels like me: simple on the surface, slightly complicated underneath, and very much alive.
You can see who I am, what I do, the work behind Herodot, RaptorLabs, CyberLink Security and Solmint, plus a selection of projects I’ve built across AI, cybersecurity, Web3, product systems, education, archives, and experimental digital spaces.
Here's exactly what it looks like to work with me 👇
Hiring someone you've never worked with is a leap of faith... and honestly, most "hire me" posts don't help. They tell you what someone offers, not how it actually goes. So let me close that gap.
Before we even start: a quick discovery conversation
No commitment, no pressure. We talk through what's actually eating your time, what "support" would ideally look like for you, and whether I'm the right fit. If I'm not, I'll tell you and probably point you somewhere better.
Week one: I get the lay of the land
This isn't me disappearing into a task list. I ask questions about your tools, your workflow, your pet peeves, the thing you keep meaning to fix but haven't had time for. By the end of week one, I've usually already spotted at least one small inefficiency worth flagging.
Ongoing: communication that doesn't require babysitting
You'll get regular updates on what's moving, what's done, and what needs your input on a cadence we agree on upfront (daily check-in, weekly summary, whatever actually fits how you work). No mystery. No "what has she even been doing" moments.
What "done" looks like
Done means the task is complete and handed back in a way you can actually use labeled, organized, explained if needed. I don't consider something finished just because it's off my plate; it's finished when it's usable on yours.
The honest part: I'm not going to pretend every project is flawless from day one. Systems get refined. But refinement happens through clear communication, not radio silence and that's the part I take seriously.
If the biggest thing holding you back from hiring support is "but what am I actually getting into?" hopefully this answers it.
💬 Got a question about how this would work for your specific situation? Ask. I'd rather answer it now than have it be the reason you don't reach out.