Tags
Writing, research, projects, and photos around “Learning”.
The Business Model Canvas from an enterprise investment class, noted for myself: what each of the nine boxes is, the question each box must answer, and why the line 'all of them must be satisfied for a project to succeed' depends on the company's stage.
A note on a distinction: the business model canvas is 'made for yourself,' the startup pitch is 'told to others,' and investor due diligence is 'others scrutinizing you'; the three differ completely in purpose, focus, and framing — don't mix them up.
A personal reading record from 2021 to 2023: what I read, how I keep notes, and a few reflections I still haven't fully worked out.
A good question is not a clever way of asking, but turning a vague sense of discomfort into something verifiable, discussable, and actionable; this is a set of daily exercises for work, learning, and review.
Part of the column “Thinking Practice” · Chapter 3
When entering an unfamiliar business or system, don't rush to start from a local solution. First map the users, the process, inputs and outputs, key constraints, and value, so you know what to ask.
Potential is not a label drawn from a résumé or a single performance. Rather than judging whether someone is "smart enough," observe how they learn, act, think, and recover from setbacks.
Part of the column “Growth & Self-Assessment” · Chapter 1
The value of an engineering retrospective is not in retelling what happened or blaming individuals, but in turning an experience into improvements that can be verified, maintained, and reused.
Turn technical sharing from a regular talk into a knowledge-collaboration system that connects topic selection, research, discussion, and consolidation.
An old signpost written for frontend beginners: information gathering, study logs, algorithm practice, interviews, and internships are all just the beginning.