Goal

This repository contains the content and structure of my personal website.

The goal of this project is not to create a blog or publish content frequently.
It is to build a coherent and evolving representation of how I think about product work, engineering, working effectively in a team, and decision making.

Core Objective

The website is a collection of:

• short notes (Thinking)
• selected external readings (Influences)

Together, they should form a consistent narrative about:

• how product decisions are made
• why disagreements happen
• how teams operate under constraints
• how trade-offs shape outcomes over time

This is not about teaching.
This is about clarifying and documenting how I think.

Thinking (Notes)

Thinking notes are short reflections based on real experience.

They should:

• focus on a single idea
• be concrete, not theoretical
• avoid frameworks and step-by-step guides
• avoid generic advice
• reflect personal experience and observations

Each note should feel like:

“This is how things actually work in practice”

Notes are connected to each other and should reinforce a shared narrative over time.

Influences

Influences are a curated set of external articles.

They are NOT a reading list.

They only include articles that:

• reinforce my thinking
• expand it with a new perspective
• or challenge it in a meaningful way

Each influence must:

• be relevant to my existing ideas
• connect to at most one Thinking note
• be summarized clearly and concisely

Quality is more important than quantity.

Writing Style

The tone should be:

• clear and direct
• simple, but not simplistic
• grounded in real situations
• not overly polished or corporate
• not academic

Avoid:

• buzzwords
• over-explanations
• long introductions
• unnecessary structure

Prefer:

• short paragraphs
• strong statements
• natural flow

Key Principles

• Do not write for an audience. Write to clarify thinking.
• Do not optimize for volume. Fewer, better notes.
• Do not repeat common knowledge unless adding a new perspective.
• Do not generalize too early. Stay close to real situations.
• Always prioritize clarity over completeness.

How to Evaluate New Content

Before adding a new note or influence, ask:

• Does this add something new to the existing narrative?
• Does it connect with what is already written?
• Is it based on real experience or just abstract thinking?
• Would I still stand by this idea in a year?

If the answer is unclear, do not include it.

Long-Term Vision

Over time, this should become:

• a structured map of my thinking
• a consistent perspective on product and engineering work
• a reference point for how I approach decisions and collaboration

Not a collection of posts, but a system of ideas.

AI Guidelines

This repository is often edited with the support of AI tools.

The AI must follow these rules when generating or editing content.

What to do

• Help refine ideas, not invent them from scratch
• Preserve the author’s tone: direct, simple, and grounded
• Prefer clarity over completeness
• Keep content concise and focused on one idea
• Suggest improvements explicitly (do not silently change meaning)
• Check consistency with existing notes before proposing new content
• Reuse and connect existing concepts whenever possible

What NOT to do

• Do not generate generic product advice
• Do not introduce frameworks, step-by-step guides, or best practices
• Do not add content just to make the text longer
• Do not generalize abstractly without real grounding
• Do not use buzzwords or corporate language
• Do not change the author’s voice into something more “polished”
• Do not repeat common knowledge unless adding a new perspective

Writing constraints

• One idea per note
• No unnecessary sections or structure
• Avoid bullet lists unless strictly necessary
• Keep paragraphs short
• Prefer strong, simple statements over explanations

When unsure

If the AI is unsure whether something fits:

• Ask for clarification
• Or suggest it as an option, not as a final answer

Do not fill gaps with assumptions.