03 / FIELD NOTES
Write down
the why.
How a family media project grew into DrakeLabs: the decisions, mistakes, and lessons along the way.
ReflectionACCESS & USABILITY
Design for the person pressing play.
Jellyfin’s broad client support was part of my choice, but mostly standardizing the family on Fire TV Sticks gave me a more predictable setup to support. The other half of that experience was getting connected.
When my mom or in-laws needed to reopen Tailscale or sign in again, it looked like Jellyfin had stopped working. A fix that was obvious to me was another hurdle for them. That helped drive the decision to spend money on a domain and pursue a simpler route in.
Those choices taught me to include the app, account, and connection steps in the design—not just the server.
Read the full family-media case study → ProcessMY WORK & AI’S ROLE
Give the work accurate credit.
In the earlier lab, AI helped with research and Bash or Python scripts. I manually reviewed that material and did the building and configuration myself.
Direct implementation by agents is a recent change. For this website, ChatGPT and Codex generate the code, styling, and layouts; I provide the story, goals, direction, and review. That is different from independently writing the front end, and I want the distinction to stay clear.
How this website was built → Give the learning a home.
A list of services tells you what exists. DrakeLabs is a place to explain why I chose them, what went wrong, and what I learned. Projects hold the case studies; Infrastructure brings together the practical lessons; this journal preserves how the work developed.
The static portfolio is hosted independently of the systems it describes, giving the documentation a home beyond the lab itself.
What I want to explore next →