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.
i keep forgetting to add uptime monitors when i deploy new services. so i wrote a cronjob that does it for me.
opening note
wfd / Feb 28, 2026 / 3 min
Stub i haven't finished writing this yet. i publish drafts early as part of WFD 17.
i keep forgetting to set up uptime monitors. i'll deploy something, move on, and two weeks later realize it's been unreachable because i never added it to the dashboard. it takes two minutes to add one manually. i just never remember.
so i wrote a cronjob that watches my kubernetes ingress resources, diffs them against existing monitors, and creates whatever's missing. it runs every five minutes. i don't have to think about it anymore.
a shell script mounted into a kubernetes cronjob via a configmap. it talks to an external uptime API.
flowchart LR
tf_values["values.yaml"] -->|"loaded into"| tf_helm["helm_release"]
tf_secret["kubernetes_secret (api_token)"] -->|"depends_on"| tf_helm
tf_helm -->|"deploys"| cj["CronJob (*/5 * * * *)"]
cm["ConfigMap (sync.sh)"] -->|"mounted into"| cj
secret["Secret (API_TOKEN)"] -->|"env var"| cj
sa["ServiceAccount (ingresses: get, watch, list)"] -->|"identity for"| cj
flowchart TD
s1["Validate API token"]
s2["Fetch existing monitors (paginated)"]
s3{"Count >= limit?"}
s4["Collect ingress hosts (deduplicate + sort)"]
s5["For each host"]
s6{"Already monitored?"}
s7["Probe /health"]
s8{"/health returns 200 with keyword?"}
s9["Create keyword monitor"]
s10["Create status monitor"]
s11["Print summary"]
s1 -->|"token set"| s2
s1 -->|"missing"| exit0["exit 0"]
s2 --> s3
s3 -->|"yes"| exit0
s3 -->|"no"| s4
s4 --> s5
s5 --> s6
s6 -->|"skip"| s5
s6 -->|"no"| s7
s7 --> s8
s8 -->|"yes"| s9
s8 -->|"no"| s10
s9 --> s5
s10 --> s5
s5 -->|"done"| s11
if a host's /health endpoint returns 200 with something recognizable ("status": "ok" or similar), it creates a keyword monitor that checks for that string. otherwise it falls back to a basic status monitor on the root URL. keyword monitors are better because a service can return 200 while being functionally broken.
the script checks both root and /health URLs before creating anything, so it's idempotent. if the API token is missing it exits cleanly instead of erroring. it also rate-limits API calls between creates.
the pod runs non-root with a read-only filesystem and all capabilities dropped. concurrencyPolicy: Forbid prevents overlapping runs.
stakater/IngressMonitorController is a full kubernetes operator for this exact problem. 715 stars, Apache-2.0, supports eight providers including UptimeRobot, StatusCake, and Pingdom. uses a custom EndpointMonitor CRD.
| IngressMonitorController | my cronjob | |
|---|---|---|
| approach | operator with CRDs | shell script in a cronjob |
| providers | 8 | 1 |
| discovery | opt-in per service via CRD | automatic from ingress resources |
| health probing | no | yes (keyword monitors) |
| complexity | full operator lifecycle | one script, one configmap |
the key difference is opt-in vs opt-out. their operator requires you to create an EndpointMonitor resource for each service you want monitored. mine monitors everything in the namespace by default. adding new providers to theirs also means writing Go and contributing upstream.
the tradeoff is that mine is less robust. 5-minute polling instead of event-driven, single provider, and it doesn't clean up monitors when i delete an ingress.
this might grow into something better or it might stay as a script that scratches an itch. haven't decided yet.