Development30 topics
Software development
Software development is the work of deciding where the boundaries in a system go, what runs on each side of them, and what moving one of those boundaries will cost once the code is live. This section covers 30 topics — architecture, the browser, seven backend languages, four mobile platforms, language models and the databases underneath all of it. Every page turns on the constraint that actually separates the options, rather than on the API surface.
What is inside
Each area below is a group of topics. Open one to read its pages.
- ArchitectureWhere to draw the boundary, what it costs to move it later, and how services talk.MonolithMicroservicesAPI design
- FrontendThe browser as a runtime: the cascade, the event loop, and how three frameworks update the DOM.ReactVueAngular
- BackendSeven languages, organised by execution model rather than syntax — from goroutines to ownership and the EVM.Node.jsGoRust
- MobileEach platform by its defining constraint: the JS bridge, the render loop, ARC, the lifecycle.React NativeFlutterPWA
- AI & LLMSix pages built as one argument: the model cannot look anything up, and what to do about it.RAGFine-tuningAgents
- DatabasesWhat the engine enforces, where the data physically lands, and what shape it should take.SQLNoSQLModelling
Where to start
- Choosing an architectureRead Monolith first, even if you are sure you want microservices — it is the argument the other three answer.
- Picking a backend languageThe five backend pages compare execution models directly. Node.js and Python are the fastest way to see the difference.
- Building anything with an LLMStart with LLM Fundamentals. The two facts it establishes are what the other five AI pages exist to correct for.
- Designing a schemaData Modeling owns shape, SQL owns what the engine enforces, NoSQL owns where the row physically lands.
Other sections
- InfrastructureInfrastructure is everything that turns code into something running that you can observe, change and roll back. This section covers 11 topics in four groups: DevOps and the pipeline that builds one artifact and promotes it unchanged, the three major clouds and how each contains a mistake, MLOps — the same problems again for a model instead of a binary — and the monitoring that makes an incident answerable at three in the morning.
- QAQuality assurance is the practice of deciding what to check, running those checks often enough to be worth having, and knowing what changes when the thing under test stops giving the same answer twice. This section covers 9 topics in three groups: the types of testing everyone half-remembers, automation with Playwright, Cypress and Selenium, and testing products built on language models — where an assertion becomes a score rather than an equality.
Found this useful?
Share it with someone who is working on the same problem.