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 cork to move.
drag notes to rearrange.
use +/− or pinch-wheel to zoom.
click one to open.
@schmayterling
open githubrecruiter?
(follow the red line) →product work, public-service software, developer tools, infrastructure, reverse engineering, open source.
scattered screenshots
dozens of windows
half-finished checklists
constant switching
organized by gravity, not category.
this website + ai stuff. open this week.
system maps. ui splinters. crash dialogs. blunt debugging. cat memes.
saved mid-understanding, not after everything looks tidy.
i enjoy writing code.
if ai solves every problem,
what's left?same circle. over and over.
less interested in
whether it's good—
diffusion models
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.
892 commits. the personal AI agent i've been trying to build since 2023 is finally becoming something i'm proud of.
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.
unfolding paper…
wfd / Feb 28, 2026 / 3 min
Stub i haven't finished writing this yet. i publish drafts early as part of WFD 17.
I use AI when writing code. Objectively it's better at writing code than doing it by hand, provided you prompt it right. Garbage in, garbage out. The quality of the output is a direct function of how well you frame the problem, the constraints, and the context. If you feed it vague instructions you get vague code.
Oxide's RFD 576 frames it well. The responsibility lies with the person in the chair. The AI is a tool. The output is yours. If the code is wrong, that's on you, because you accepted it. If the architecture is bad, that's on you, because you approved it. The moment you stop understanding what's being generated is the moment the tool becomes a liability.
Ever since WFD 15 I've been starting to wean off heavy AI usage. The reason is simple: I feel dumber.
I had a moment where I kicked off an AI task to solve something and it sat there thinking for thirty minutes. While it was thinking I already finished the task myself. I cancelled the run. Wasted tokens, wasted time, and I could've just done it from the start.
The same thing happens with explaining code I wrote. I know the codebase. I built it. But I hit mental blocks trying to articulate how something works because I've been letting AI do the tracing for me. The muscle for retracing logic and holding context in my head is atrophying.
AI is good. AI is a 10x multiplier. I've heard it all. But it's making me worse at the things I used to be good at because it's doing them for me.
I enjoy writing code. I enjoy writing this document. Delegating everything to AI takes the fun out of the thing I actually love doing. Programming got me started because I liked solving problems. If the AI solves every problem, what's left?
Starting to wean it off. I'm not going cold turkey, but I'm being more intentional about what I delegate and what I do myself. The boring stuff (boilerplate, repetitive refactors, test scaffolding) is fine. The interesting stuff (architecture, debugging, problem-solving) I want back.