what i'm bout.
WHERE I'M FROM
i was born and raised in a small town. growing up, they repeatedly told me to get off the computer and go outside. the og touch grass™. i'm glad i did, but my fascination with how digital systems work always pulled me back in.
WHAT I USED TO DO
when i was younger, i chased curiosity across various fields. i explored everything from basic scripting to complex web architectures, building whatever tools came to mind.
WHAT I DO NOW
today i'm a software engineer designing intelligent experiences. previously, i was exploring experimental ux and backend scalability. i focus on turning complex technical challenges into seamless human experiences.
WHAT I'M LOOKING FOR
impactful, purposeful work with a diverse team of talented people. i think the personal computer needs its next massive leap in interface design, and i want to help build it.
building systems • prev @startup @engineering
nights
Efrank ocean — blonde
300+ contributions in the 3 months
CURRENT CHAPTER
a snapshot of what i’m focused on, building, learning, and working toward right now. these are not goals—this is the life i am actively living.
— Building
- GUIDO
- Public AI research laboratory
- AI Experiments
— Learning
- Agent architectures
- Memory systems
- Modern LLM engineering
— Improving
- Physical health
- Consistency
- Communication
- Execution
— Exploring
- How research, engineering, and entrepreneurship intersect to create meaningful products.
"how research, engineering, and entrepreneurship intersect to create meaningful products."
CHAPTER 01
the early obsession.
circa 2019
it started with breaking things. i remember disassembling old hardware just to see if i could put it back together. i usually couldn't. but that didn't matter. the point was to understand the system, to pull back the curtain on the magic that lived inside the screen.
eventually, taking things apart turned into putting code together. the terminal felt like a direct line to the machine. there was no interface, no drag-and-drop. just raw commands and immediate consequences.
"the computer is a bicycle for the mind. but you have to build the pedals yourself."
i spent my nights reading documentation like it was literature. i realized that being a software engineer wasn't just about writing logic; it was about designing systems that humans actually interact with.
the deeper i went into ai and agentic architectures, the more i understood that we are at the edge of a fundamental shift. we aren't just programming tools anymore; we are building entities with memory, context, and reasoning.
early architectural sketches. figuring out memory systems.
journal entry — 23:14 pm
i think the real breakthrough isn't going to be making models bigger. it's going to be figuring out how they remember. context is everything. if a system doesn't remember, it doesn't learn.
CHAPTER 02
building the foundation.
CHAPTER 03
the current chapter.
and that brings us to today. building GUIDO, experimenting with human-ai interaction, and treating every line of code like an artifact. the journey continues.
(to be continued...)
ANNUAL REVIEWS
a yearly reflection on what i learned, built, experienced, and discovered.
