stephango.com

What is Steph Ango?

Steph Ango is the personal website of a writer and product thinker who publishes short essays on tools, design, software, writing and decision-making, plus notes on his own projects. The site is best understood as a personal essay collection rather than a company or product page: posts are dated and grouped under broad topics such as advice, design, minimalism, money, obsidian and writing.

What you'll find there

• Short essays on tools and craft, for example "Great tools choose to be bad at some things," "File over app" and "Style is consistent constraint."
• Practical workflow notes, such as "How I use Obsidian" and "How I do my to-dos."
• Reflective pieces on judgment and habits, such as "Buy wisely," "Don't delegate understanding" and "Calmness is a superpower."
• Occasional project notes, including a recurring "100% user-supported" theme.

Who it suits

A reader deciding whether to spend time here can use a simple test. If you want long, researched tutorials, this is not the place. If you want compact arguments you can finish in a minute or two and then apply to your own work, it fits well. Designers, writers and people building small software products are the most natural audience, since many posts circle around tool choice, constraints and attention.

A useful next step

Start with one essay in a topic you already care about, then follow its topic tag to see whether the surrounding posts hold your interest. For a concrete example, a developer choosing a note-taking setup might read "How I use Obsidian" alongside "File over app" to see how one person's tool habits connect to a broader argument about owning your data. Treat those as one writer's observations rather than general recommendations.

For comparison, other personal sites in a similar vein include Paul Graham for longer startup and thinking essays, and Craig Mod for writing on walking, craft and publishing.

What topics does Steph Ango write about on his site?

Steph Ango's site is a personal essay collection rather than a single-subject blog. The topics listed on the site run from practical tool and software notes to broader reflections on work, design and how to live.

Main topic clusters

• Tools and software: writing about Obsidian, file formats ("File over app"), how he organizes to-dos, and what makes software worth paying for.
• Design and craft: minimalism, constraint and style, "Black pixels," "Photoshop for text," and design as compromise.
• Work and learning: concise explanations, not delegating understanding, hybridizing rather than specializing, and learning a little every day.
• Money and independence: buying wisely, user-supported products, and paying for quality software.
• Humanist and personal essays: empathy, optimism, love as freedom, calmness, habits and rituals, plus recurring "40 questions to ask yourself" pieces.
• AI and competition: recent entries such as "Use the saw, fear the saw" sit alongside tags for AI, competition and leverage.

A reader deciding whether to follow the site can use the topic tags as a filter: someone looking for note-taking and tool workflows will find the Obsidian and file-format essays most useful, while someone after reflective writing will gravitate to the empathy, optimism and annual-questions pieces. The mix means the site rarely stays on one subject for long.

For comparison, Obsidian's official site at Obsidian covers the software itself, while Ango's essays discuss how he uses it and why he values it.

What practical advice does Steph Ango offer for using Obsidian?

Steph Ango treats Obsidian as a plain-text, file-first workspace rather than a database you pour notes into. The practical advice on his site centers on three habits: keep notes as ordinary files on disk, write in short self-contained notes that link to each other, and choose tools that deliberately do a few things well instead of trying to do everything.

Concrete uses

• Personal knowledge base: one note per idea, linked rather than filed into deep folders, so ideas become "objects you can manipulate" and recombine later (his essay Evergreen notes turn ideas into objects that you can manipulate).
• Writing and publishing: drafting in plain Markdown so the same text moves between editor, blog and archive without conversion. His own site reads like this—dated essays, short, each making one point.
• Long-lived archives: because files sit outside any single app, notes survive app changes. His File over app essay is the argument: formats you can read without the original software are the ones worth committing to.

Who it suits

Writers, researchers and developers who are comfortable with Markdown and want ownership of their files. It is a weaker fit for people who want a polished, opinionated system out of the box—Obsidian's flexibility means you supply the structure, and that is real work.

Trade-offs he names

• Constraint as a feature: Great tools choose to be bad at some things and Style is consistent constraint argue that limits keep a tool coherent. Expect to accept rough edges in exchange for focus.
• Don't delegate understanding: take time to learn the tool's model yourself rather than importing someone else's template wholesale.
• Remove before adding: What can we remove? suggests pruning plugins, folders and rituals before expanding them.

A practical next step

Start with one real project—an essay, a reading log—and create a note per idea, linking as you go. Add structure only when a specific friction appears. If you want to see the method in context, read his write-ups at Steph Ango, and compare the plain-file approach with a dedicated notes tool such as Obsidian itself.

How does Steph Ango approach buying and choosing tools wisely?

Steph Ango treats buying a tool as a decision about constraints, not about features. The clearest statement of this is his essay "Buy wisely" (linked from the site's writing index), and the surrounding essays reinforce the same logic: a good tool deliberately chooses to be bad at some things, and style is a matter of consistent constraint rather than maximal capability. The practical idea is that every purchase should be judged by what the tool refuses to do as much as by what it does.

What that looks like in practice

• Start from the constraint. Ask which trade-offs you can live with before comparing options. Ango's "Great tools choose to be bad at some things" makes the case that focus, not breadth, is what makes a tool trustworthy.
• Prefer tools you can keep. His "File over app" and "100% user-supported" pieces point to durability: data in open formats, and products funded by users rather than by attention or ads. For a buyer, that means checking export formats and the business model before the feature list.
• Buy to remove friction, not to add options. "What can we remove?" and "Don't delegate understanding" both argue against buying your way out of thinking. A tool should shorten the path to work you already understand.
• Pay for quality you will actually use. "Quality software deserves your hard-earned cash" is a straightforward argument for paying for good tools rather than accumulating free ones.

A reader scenario

Suppose you are choosing a notes app for a decade of research. The feature comparison will not settle it. Under this approach you would first decide the constraint that matters most — for example, that your notes must remain readable as plain files — then eliminate anything that fails it, and only then compare the survivors on speed and price. You would also check how the maker is funded, because a tool that must monetize your attention is a different long-term bet than one supported by its users.

Decision criteria to apply

As a next step, read Steph Ango's "Buy wisely" alongside "Great tools choose to be bad at some things" and "File over app," then write down your own one-sentence constraint before you open a pricing page.

What questions does Steph Ango suggest asking yourself every year or decade?

Steph Ango publishes two self-review questionnaires on his site: a yearly set ("40 questions to ask yourself every year," 2016) and a decade set ("40 questions to ask yourself every decade," 2020). Both are grouped by life area rather than a single ranked list, so you answer the ones that apply and skip the rest.

What the questions cover

From the titles and the topics he tags around them, the questions are organized around practical domains:

• Work and craft — what you built, what you learned, what you'd stop doing.
• Money and security — earning, spending, and what "enough" means to you.
• Relationships — friendships, family, love, and who you've neglected.
• Health and habits — rituals, energy, and daily defaults.
• Beliefs and direction — what changed your mind, what you want next.

The decade version works the same way but at a longer horizon: it asks about patterns across ten years rather than a single one.

How to use them

The point isn't to answer all forty. His broader writing on defaults, minimalism, and "what can we remove" suggests the useful move is to pick a handful, write short answers, and look for one thing to change. A concrete example: answer "What did I learn?" and "What would I stop?" for last year, then turn the second answer into a single habit to drop this month.

A decision criterion

Use the yearly list if you want a light annual review you can finish in an evening. Use the decade list at a milestone birthday or a career change, when the question is less "what did I do this year" and more "what pattern do I want the next ten years to break."

For the full text, read Steph Ango directly; the essays sit alongside related pieces such as "How I do my to-dos" and "A little bit every day," which pair well with the review habit.

How can I follow or subscribe to Steph Ango's new essays and updates?

The site lists a dedicated subscribe page for updates, linked as "Receive my updates" (Steph Ango). That page is the natural place to check for the current options, such as an email newsletter or other update channel.

If you prefer not to subscribe, the writing index on the homepage is a practical alternative: essays are grouped by year with dates, so you can revisit it periodically and catch new pieces like "Use the saw, fear the saw" (October 2025). Many essays also carry topic tags (writing, tools, design, advice), which helps you decide whether a new post is worth your time before reading.

A simple decision rule: choose the subscribe page if you want posts pushed to you and don't mind sharing contact details; use the dated index if you'd rather browse anonymously and only occasionally.