# Alex Kondov - Full-Stack Tao: Picking a Tech Stack (Highlights) ![rw-book-cover|256](https://alexkondov.com/static/b6eddd8c6ec0677ad78e762842b40ad2/bc8e0/cover.png) ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/34572052) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Alex Kondov]] **Full Title**:: Full-Stack Tao: Picking a Tech Stack **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [alexkondov.com](https://alexkondov.com/full-stack-tao-picking-tech-stack/) **Host**:: [[alexkondov.com]] **Highlighted**:: [[2023-11-25]] **Created**:: [[2023-11-25]] ## Highlights - Understanding our product’s domain is the first thing in our engineering checklist because it will help us identify the specific technical problems we have to solve. Scale, availability, features - they all stem from business problems. ([View Highlight](https://read.readwise.io/read/01hg4dmvmdc08qnk961c3ppzp4)) ^631761103 - I’ve seen more projects struggle because of over-engineering rather than the opposite. Our focus on the future, fighting potential problems that may never occur is incredibly successful at making codebases too complex to work on. ([View Highlight](https://read.readwise.io/read/01hg4dtemgrthq5mvcecg39vva)) ^631764247 - So when in doubt, always lean towards under-engineering rather than over-engineering. ([View Highlight](https://read.readwise.io/read/01hg4dtxte2x7ghncn9535880v)) ^631764712 - Keep in mind that your experience with a technology will beat the potential technical benefits of another. Knowing what pitfalls to avoid and what patterns to use will help you build a good structure and be productive at the same time. ([View Highlight](https://read.readwise.io/read/01hg4dyznpyp8c7nbwabvjpy91)) ^631765654