[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"idea-sqlite-is-underrated":3,"related-sqlite-is-underrated":50},{"id":4,"title":5,"body":6,"cardSize":36,"category":37,"date":38,"description":39,"extension":40,"featured":41,"meta":42,"navigation":43,"path":44,"readingTime":45,"seo":46,"stem":47,"updated":48,"__hash__":49},"ideas\u002Fideas\u002Fsqlite-is-underrated.md","SQLite is Underrated",{"type":7,"value":8,"toc":32},"minimark",[9,13,16,19,22,25],[10,11,12],"p",{},"I keep coming back to SQLite. Every time I start a new side project, I reach for Postgres out of habit, then realize I am building a todo app for one person and a 200MB database server is absurd.",[10,14,15],{},"SQLite handles more than people think. It can do millions of reads per second. It supports JSON columns. It works on phones, servers, and embedded devices. Your browser uses it right now.",[10,17,18],{},"The real advantage is not performance, though. It is simplicity. Your database is a file. You can email it. You can version control it. You can deploy it by copying a file. No connection strings, no user management, no cluster configuration.",[10,20,21],{},"For 90% of the side projects I see developers building, SQLite is the right choice. The other 10% need Postgres. But most people reach for Postgres for 100% of projects because that is what the tutorial used.",[10,23,24],{},"I am not saying abandon Postgres. I am saying think about what you actually need before reaching for the heavy tools.",[26,27,28],"ul",{},[29,30,31],"li",{},"Mohan",{"title":33,"searchDepth":34,"depth":34,"links":35},"",3,[],"medium","Code","2026-03-22","Most apps do not need Postgres. They need SQLite and a clear schema.","md",false,{},true,"\u002Fideas\u002Fsqlite-is-underrated",4,{"title":5,"description":39},"ideas\u002Fsqlite-is-underrated",null,"Qe3JlTD6GjpIyYa4CytBCsnVFGvVdTBOgIPyrC1Z5d8",[51],{"id":52,"title":53,"body":54,"cardSize":48,"category":37,"date":71,"description":72,"extension":40,"featured":41,"meta":73,"navigation":43,"path":74,"readingTime":75,"seo":76,"stem":77,"updated":48,"__hash__":78},"ideas\u002Fideas\u002Fshower-thought-apis.md","Every Company Should Have a Public API",{"type":7,"value":55,"toc":69},[56,59,62,65],[10,57,58],{},"Quick thought: every company with more than 10 employees should have a public API.",[10,60,61],{},"Not because developers will build things with it (though some will). But because having a public API forces you to think clearly about what your product actually does. If you cannot express your core value proposition as a set of API endpoints, you probably do not understand your own product well enough.",[10,63,64],{},"The discipline of writing API documentation is the discipline of clear thinking.",[26,66,67],{},[29,68,31],{},{"title":33,"searchDepth":34,"depth":34,"links":70},[],"2026-03-12","A shower thought that turned into a conviction.",{},"\u002Fideas\u002Fshower-thought-apis",2,{"title":53,"description":72},"ideas\u002Fshower-thought-apis","tSQcgbw4qXFedhHY5deJ6ACdja-hLrJo-VJo0Kbwy9w",1776214201870]