# ethos
<div class="pills-container"> <span class="pill">Last Updated: October 28, 2026</span> </div>
> [!INFO] This page is most useful for my current and future collaborators.
## How I work best
I'm currently based in Metro Manila (UTC+8). Because of my current engagements, I'm often stuck in meetings all day. Hence, for independent collaborations, I would appreciate async-heavy work, maybe via Google Doc. If I have any points of confusion, I'd rather talk it out on a short call to unblock quickly. In general, I like to [[#Mistakes I've made|stress-test assumptions]] and explore [counterfactuals](https://en.wikipedia.org/wiki/Counterfactual_thinking) before settling on an intervention. I like to play [Devil's advocate](https://en.wikipedia.org/wiki/Devil%27s_advocate) to ensure that something is worth pursuing in the first place.[^1]
I like being surrounded by sharp and mission-driven people. I work best in environments where people care deeply about their work and their epistemics. I care about making differential progress in the work I do. I believe that [once a metric becomes the goal, it ceases to be a good metric](https://en.wikipedia.org/wiki/Goodhart%27s_law).
I stagnate in [[#What I care about|low-trust environments]]. If I feel like I have to posture and second-guess people's real incentives, it drains me. I work best with people who are direct and do not weaponize ambiguity. I take [honest feedback](https://www.admonymous.co/lenz) especially when well-reasoned, as a sign of care. I lose patience fast when someone talks around what they actually want to say. I will also not understand what you mean until you tell it to me straight (this is really a byproduct of my neurodivergence).
## What I care about
I'm skeptical of anything that tries to generalize a complex system. I think conventional wisdom is often wrong, and I'd rather be epistemically honest than agreeable. A few patterns I actively avoid:
- I feel stagnant in teams that **never** give honest feedback, or take _too long_ to give it.
- I don't fit well in environments where "alignment" means agreement.
- I'm wary of "impact-washing" (i.e., people who claim to work on impactful problems but are really optimizing for personal leverage).
## Mistakes I've made
I believe in learning in public. That's why I keep a changelog of the mistakes I've made in the past, so I can improve in the future.
- I care about showing up for the people and problems in front of me. But **I often take on more than I can chew**, and this sometimes leads to late nights or quiet burnout. The people I wanted to help in the first place end up under-supported anyway. I've since learned that saying yes to everything eventually means that I'm not showing up well for anything.
- I move quickly when I'm clear on my direction and that makes me effective. But **there were times I sprinted ahead thinking that everyone in my team was on the same page**. I later realized that others did not share my mental models or priorities, and they ended up feeling confused and upset. I've since learned that clarity takes more time than I think, especially when I'm working with a group.
- I gravitate towards complex problems and deep thinking. But there have been times where **I spent too long polishing ideas that were fascinating but not directionally useful**. I've since learned that insight without traction is still one form of drift.
- In the past, **I've stuck around in projects where there wasn't real alignment** and just hoped that clarity would emerge in time. But I realized that early misalignment is rarely temporary.
- I've learned that **I can fill a week with real, legitimate work and still produce nothing I'm proud of.** About 45% of my time over the past few months has gone to meetings and coordination, which crowds out the protected thinking time I actually need. The output suffers even when the hours look fine.
- I've learned that my bottleneck isn't capability, it's visibility. **I'm really _really_ bad at asking for help, and I sit on ideas until they feel ready before showing anyone**, so I end up iterating alone and getting feedback too late to matter. I'm fixing this by sharing work in progress and scoping ideas to prototype within 24 hours instead of waiting until they're polished.
[^1]: I also learned this can get quite annoying; though I'd rather you tell me directly if this approach doesn't work for you.
---
[CV](https://bit.ly/ld_cv) · [Substack](https://halfbakedtheories.substack.com/) · [LinkedIn](https://www.linkedin.com/in/llenzl/) · [GitHub](https://github.com/ramennaut) · [Feedback](https://www.admonymous.co/lenz)