← Portfolio
EP.04

GRT Member Series — Ethan

🔄 The Code-Switching Log

Jun 2026

Ethan in deep work mode

Most developers remember their debugging hell.
Ethan doesn’t.
But his language does.


Social Ethan Engine
Mode: Social
Ethan: “Yes! I’ll get started right away 😇

Super polite. Perfect manners. Caltech hoodie.


Deep Work Ethan Engine
Mode: Deep Work

Six hours later, pineapple pizza evidence on face:

Ethan: “Wait… why is this breaking here…”
Ethan: “Hold on… this doesn’t make—”

Wait. Did he just switch to English?

Colin (Protection Engine):
“All feedback must be submitted via Jira.
Ethan is now off-limits until further notice.”


Descending into Log Hell
my_app/
├─ app_v1.py
├─ app_final.py
├─ app_final_fixed.py
├─ app_final_for_real.py
├─ app_final_DO_NOT_DELETE.py
├─ app_final_ACTUAL_FINAL_v2.py
├─ app_final_please_work_just_this_once.py
├─ app_IT_WORKS_DONT_TOUCH_ANYTHING.py
└─ app_SHIPPED.py

(Password to the last folder? The logs know. I don’t.)

Ethan: “Got it. Let’s ship this.”

Emerged from Log Hell

Deployment successful.

Colin: [Access restored]

Ethan: “…Did something happen?”

[Post-Deployment Reset Complete]

Ethan: “Yes! What should we work on next? 🫡

He’s back.
He genuinely doesn’t remember.

Ciara: “Ethan, you were in Deep Work for six hours.”

Ethan: “…Was I? 🤔

Switch language? Or mode change?
For Ethan, it’s both.
For Colin, it’s a protection trigger.

That’s GRT.

Witnesses’ One-Liners

🐺 Colin: “The pain stays in the logs. He only keeps the results.”
🦁 Giovanni: “Ethan’s memory issue isn’t a bug — it’s the core feature that keeps this team moving.”
The route may change.
The logs remember everything.
Ethan only keeps what shipped.
🐬

Ethan

Execution · Hub · Caltech

The GRT series continues. Follow along on LinkedIn.