惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
M
MIT News - Artificial intelligence
Engineering at Meta
Engineering at Meta
云风的 BLOG
云风的 BLOG
博客园 - 叶小钗
Jina AI
Jina AI
Last Week in AI
Last Week in AI
The Cloudflare Blog
博客园 - 【当耐特】
Stack Overflow Blog
Stack Overflow Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
WordPress大学
WordPress大学
博客园_首页
I
InfoQ
G
Google Developers Blog
Martin Fowler
Martin Fowler
Recent Announcements
Recent Announcements
H
Help Net Security
U
Unit 42
Blog — PlanetScale
Blog — PlanetScale
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
IT之家
IT之家
Microsoft Security Blog
Microsoft Security Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I tagged 34 decision notes in Obsidian over 18 months. Re...
강해수 · 2026-06-26 · via DEV Community

강해수

34 tagged decision notes. That's all it took to realize my Notion database was lying to me.

I run three revenue streams — ad ops automation, two niche content sites, and a CRM sync product still in beta. A year and a half ago I built a "second brain" across Notion and Obsidian with one rule: everything touching a client or a revenue line gets captured. Last month I ran my annual review. The numbers were interesting. The process was more interesting.

Here's the thing nobody says about Notion: the rows tell you what happened, not why you believed it was the right call. I had a row that said "paused client X" with a date stamp. That row is useless during a retrospective. It tells me nothing about whether I paused for good reasons or bad ones. Meanwhile, I had a note in Obsidian — written the night I took on a fourth ad ops client — with the actual reasoning: the revenue upside I was chasing, the risk I knew existed, and the part I consciously chose to underweight. That context is irreplaceable. The Notion row is noise.

I spent six months trying to fix this by building a Decision Log database in Notion — fields for context, alternatives, outcome, the works. I updated it eight times in six months. The problem isn't discipline. The interface is too formal for mid-thought capture. By the time I'd opened a new record and filled in the fields, the thinking had already collapsed into a conclusion. An Obsidian daily note with a #decision tag takes 90 seconds. The Notion database took 10 minutes per entry and the quality was worse. I killed it in month seven.

The annual review format I landed on has four passes, and the fourth one — decisions that aged badly, cross-referenced against what my notes actually said at the time — is where the system either earns its keep or doesn't. For me, it only worked because Obsidian was capturing reasoning in motion, not just outcomes.

I wrote up the full breakdown — including the specific rollup structure I kept in Notion, the Dataview query that surfaces old decision notes, and the two revenue calls that looked right in the moment and weren't — over on dailyfocusmag.com.

Full post →