i'm a software engineer based in the philippines, driven by curiosity and whatever i find interesting. i learn fast with the caveat of goldfish memory (which i call my context lol) and i'm usually self-motivated that i forget to eat.
this is not like other portfolios. feel free to have a look around and explore what makes me, me.
drag empty cork to move around.
drag notes to rearrange them.
use +/− or pinch-wheel to zoom.
click any note to open it.
@schmayterling
open githubrecruiter?
(follow the red line) →the same circle, over and over.
for those who want something simpler
enter simple mode
i enjoy writing code.
if ai solves every problem,
what's left?892 commits. the personal AI agent i've been trying to build since 2023 is finally becoming something i'm proud of.
one question usually turns into three projects and too many open tabs.
typescript, python, rust, go, infrastructure, and agents.
in roughly five weeks
an earlier role handled 2,000+ requests a day at 99.3% uptime.
i update this board whenever my attention changes, so it never settles into a final form.
how WFDs work, when to write one, the states a document can be in, frontmatter format, and the markdown features available.
my desktop is scattered screenshots, dozens of windows, half-finished checklists, and constant switching.
whatever feels urgent or interesting gets the whole pile.
right now, only this website and my ai work count as current.
did i mention this board evolves over time? you might find new stuff here next time. suggestions? email me.
hey@ryanaque.com
i turned weeks of neuroscience papers into her memory system.
weave gives long-running agents memory, state tracking, and retrieval that can be inspected.
i watched a kdrama about a girl who forgets everything every morning and realized my AI agent has the same condition. so i built it a brain.
someone else is
on the other end.
i'm less interested in whether it's good.
ideally when something is coming up, whether it's work related or it's just a personal project of mine i usually let it run at the end because i need pressure to perform things.
diffusion models
i built an AI agent with persistent memory. now i need to figure out if it's remembering the truth or just what i wanted to hear.
AI makes me faster. It also might be making me dumber. I'm figuring out where the line is.
atlas maps symbols, calls, tests, and history so developers and agents can ask structural questions about a repository.
2,239-trial benchmark across 8 OSS repos: Atlas beats a text-search baseline by +0.223 deterministic, +0.127 LLM-judge, at 42% fewer tokens.
orchestrator lets a local model read and control a live chromium page through the devtools protocol.
software engineering is full of rules that people follow without thinking. most of them are wrong for you.
uptime kuma is the self-hosted monitoring tool i contributed to.
opening note
wfd / Mar 9, 2026 / 2 min
Stub i haven't finished writing this yet. i publish drafts early as part of WFD 17.
i keep hearing people use the phrase "best practices" as a conversation-ender. like it's some kind of universal law that applies to every codebase, regardless of what we're actually building.
this is the trap we've built for ourselves. we take things that worked for google at google's scale and try to apply them everywhere else. i've done it too. i spent weeks on a kubernetes setup for a site that gets 100 visitors a day because "that's how you do devops." what a waste of time.
most "best practices" are just cargo cults. we see a big company do something, we assume they're smarter than us, and we copy the ritual without understanding the context.
it's the same reason people go on certification warpaths. they want a piece of paper that says they know the "right" way to do things. but the right way depends on the constraints. and your constraints aren't theirs.
if you're following a rule and it's making your work harder or slower, the rule is probably wrong. or at least, it's wrong for right now.
arguments against following best practices blindly:
arguments for questioning them: