SQLite — A Single-File DB for Local Apps
SQLite is an embedded database that holds a SQL database in a single file. It is one of the most frequently chosen options for local storage in desktop and mobile apps.
7 views
Things I studied and noted down. For courses, see EDU.
Things I studied and noted down. For courses, see EDU.
AI/LLM topics — agents, prompts
HTML, CSS, JS, HTTP, URL basics
TypeScript, Java, Python, Rust
Data structures, Big-O, patterns
React, Next.js, Tauri, Tailwind
Spring, FastAPI, SQL
Claude Code · MCP · Context7 · Figma — overview of AI coding tools
Deployment options and decision criteria
PostgreSQL · Kafka · data strategy notes
Docker, Compose, Caddy, SSH
Windows vs Mac and other dev-environment notes
Cross-platform options compared (Tauri · Flutter · RN)
pnpm, uv, Gradle, Git, regex
KISS · DRY · YAGNI · naming — development philosophy
OAuth · JWT · security fundamentals
Testcontainers, Vitest, pytest
Searching, reading docs, debugging
SQLite is an embedded database that holds a SQL database in a single file. It is one of the most frequently chosen options for local storage in desktop and mobile apps.
7 views
An embedding is the result of mapping text (or images · code) to fixed-dimensional real-valued vectors. On top of the assumption that semantically close items sit close in the vector space, search · clustering · classif…
5 views
A monorepo keeps the source for many projects in a single version-controlled repository. This article covers what a monorepo is, its history, how far a lightweight setup like pnpm workspaces can take us, and what full-s…
5 views
The LLM market shifts fast. Closed-API and open-weight, English-centric and multilingual, cloud and self-hosted, models specialized for Korean — all sit alongside each other.
4 views
The word "agent" is used in several senses, which is a confusing situation. Script automation is called an agent, and so is the shape of an LLM calling tools.
4 views
Everyone has felt lost after being told "read the official docs." Open them and the volume is the size of a book — there's no clear sense of where to start. Documentation is not material to read cover-to-cover like a bo…
The gap between a strong developer and a beginner is closer to "finds what they don't know quickly" than "knows a lot." Search is not a supplement to memorization; it's a separate skill. This article covers how to craft…
This article is aimed at people who are about to begin programming, mapping out the areas commonly encountered early in learning, on a fact basis. A guide for when there is no clear sense of where to start.
iOS app builds go through similar steps to Android (compile → bundle resources → sign → package), but the tools, distribution channels, and policies look quite different. The biggest difference is that macOS and the App…
Building an Android app, regardless of the tool, eventually goes through similar steps. Compile sources, bundle resources, convert to DEX, and sign. The result is an APK or an AAB. This post walks through that flow, the…
Flutter is a UI toolkit from Google that targets mobile, web, and desktop from a single codebase. Its own rendering engine, the Dart language, and the widget tree as an expression model are the core. This post covers Fl…
The desire to build the same app for iOS, Android, and the web from a single codebase has been around for a long time. The tools that emerged as answers picked different approaches in different eras. Some sit on top of…
Several books and studies discuss what "good names" are. This article organizes facts from Clean Code, Code Complete, Mythical Man-Month, and Cognitive Load theory.
Feature flags (a.k.a. feature toggles) are a pattern frequently cited from large-company case studies. Small teams sometimes carry the same expectations into them, but cost and benefit vary by environment. This article…
As LLM-based code assistants become routine, "how should we mark that AI helped?" has split into different team decisions. This article objectively organizes the relevant facts (lawsuits, OSS license positions, commit t…
Choosing to write docs and comments in a native language other than English is a decision development teams in non-English-speaking regions often face. This article covers the convention of separating identifiers (Engli…
A repository hosts documents for two kinds of readers: humans, and code-assistant agents (LLM-based IDE assistants and AI coders). This article covers the standards and conventions for both.
Trying to fix every problem in one big refactor often fails. A pattern of steady cleanup in small units tends to produce more stable results — a common observation. This article covers the Boy Scout Rule and the Strangl…
The phrase "best practice" is often applied without question, but a single answer that fits every environment equally is rare. This article covers facts from three classics (CAP, PACELC, Conway's Law) that show context…
A folder structure is not just file classification — it can become a device that promises dependency direction and the scope of change between code modules. This article covers facts about Feature-Sliced Design, Domain-…
SSOT (Single Source of Truth) started as a data governance term and has expanded into a principle for code, documentation, and schema operations. This article covers the origin, areas of application, and trade-offs.
These three acronyms are often cited together as software design principles. Their origins and meanings differ slightly, and some interpretations even conflict. This article covers the origin, intent, and frequently con…
The question "OOP or functional?" used to be treated like a tribal feud. Today's modern languages support both, and real-world code mixes the two paradigms naturally. This article covers the origin of each paradigm, the…
Solving similar problems repeatedly produces similar shapes. As object orientation went mainstream in the 1990s, a book came out that named and organized those repeated shapes, and patterns became the shared language of…
The question "is this code fast?" has different answers depending on environment, hardware, and input. So computer science describes — as a function — how time (or memory) grows as input size grows. That notation is Big…