Digital Garden
This is a sort of personal knowledgebase, a place for organizing my notes and reference materials. It is a perpetual work-in-progress, and it is not unusual for topics to be still wild and untended.
The garden was inspired by Ward Cunningham’s WikiWikiWeb, the world’s first wiki, which was originally devised to share knowledge of software design patterns. My garden has since extended to cover all sorts of computer science topics.
It’s compiled from a repository of AsciiDoc documents. Each .adoc file is focused on a single idea or concept. Topics may cross-reference one another, but otherwise each file is a self-contained document.
Read more about the concept of the digital garden.
Legend
- 🌱 Seedling. Early draft.
- 🌿 Budding. Needs attention.
- 🌳 Evergreen. Mature document.
- 🍂 Decaying. No longer maintained.
Hubs
The following topics are broad, umbrella subjects. Each links out to a cluster of narrower, related topics. These are good starting points for exploring the rest of the digital garden.
- Artificial intelligence (AI) 🌳
- Computer science 🌱
- Culture and folklore 🌱
- Data engineering 🌱
- Databases 🌱
- Design patterns 🌳
- Developer tooling 🌱
- Distributed systems mechanisms 🌱
- Hardware 🌿
- Laws and principles 🌱
- Modeling notations and methods 🌱
- Network protocols 🌿
- Quality attributes 🌿
- Requirements and product management 🌱
- Security 🌱
- Software architecture 🌳
- Software delivery and operations 🌱
- Testing 🌳
- Ways of working 🌿
All topics
0-9
A
- A/B testing 🌱
- Abstraction 🌿
- Abstractness 🌿
- Acceptance criteria 🌱
- Acceptance testing 🌱
- Access control list (ACL) 🌱
- Access patterns 🌱
- Accessibility 🌱
- Accessibility testing 🌱
- Accountability 🌱
- ACID principles 🌱
- Active-active 🌱
- Acyclic dependencies principle 🌱
- Adaptability 🌱
- Adapter pattern 🌿
- Adaptive software development 🌿
- Agent 🌱
- Agent2Agent (A2A) 🌱
- Agent handoff 🌱
- Agent harness 🌱
- Agent loop 🌱
- Agent memory 🌱
- Aggregate 🌱
- Aggregation 🌱
- Agile software development 🌳
- Agent orchestration 🌱
- Agent skills 🌱
- Agentic engineering 🌱
- AI assistant 🌱
- AI bias 🌱
- AI coding assistant 🌱
- AI constitutionalism 🌱
- AI regulation 🌱
- Alerting 🌳
- Algorithms 🌳
- Alpha testing 🌿
- Alpha version 🌿
- Analysability 🌱
- Analytical databases 🌱
- Anti-pattern 🌿
- API-first design 🌱
- API gateway 🌱
- Application performance management (APM) 🌿
- Appropriateness 🌱
- arc42 🌱
- ArchiMate 🌿
- Architectural knowledge management (AKM) 🌳
- Architectural pattern 🌿
- Architecture description 🌱
- Architecture evaluation 🌱
- Architecture framework 🌱
- Architecture model 🌱
- Architecture Tradeoff Analysis Method (ATAM) 🌱
- Architecture view 🌱
- Arrange, act, assert 🌱
- Assessment 🌱
- Association 🌿
- Artificial general intelligence (AGI) 🌿
- Artificial intelligence (AI) 🌳
- Asymmetric Cryptography 🌱
- Asynchronous communication 🌱
- Asynchronous processing 🌱
- Asynchronous programming 🌱
- Atomic operation 🌳
- Attack tree 🌱
- Atwood’s law 🌱
- Authentication 🌳
- Authenticity 🌱
- Authorization 🌳
- Auto-scaling 🌿
- Automated testing 🌳
- Availability 🌿
- Availability zone 🌱
- Away-from-keyboard (AFK) 🌳
B
- Backwards compatibility 🌳
- Bash 🌳
- Batch processing 🌳
- Behavior-driven development (BDD) 🌿
- Behavioral testing 🌳
- Beta testing 🌿
- Beta version 🌿
- Big ball of mud 🌱
- Big bang 🌱
- Big data 🌱
- Big design up-front 🌿
- Big O notation 🌿
- Bike shedding 🌱
- The Bitter Lesson 🌱
- Black-box view 🌱
- Blackboard 🌱
- Black-box testing 🌿
- Block storage 🌱
- Bloom filter 🌿
- Blue-green deployment 🌱
- Boy scout rule 🌱
- Booch method 🌱
- Border Gateway Protocol (BGP) 🌿
- Bounded context 🌱
- Bottom-up design 🌱
- Bridge 🌱
- Broker 🌱
- Brooks’s law 🌱
- Building block 🌱
- Building block view 🌱
- Business architecture 🌱
- Business context 🌱
- Business Process Model and Notation (BPMN) 🌿
- Bulk synchronous parallel 🌿
- Bulkhead 🌿
- Bus factor 🌱
C
- C4 model 🌿
- Caching 🌱
- Canary deployment 🌱
- CAP theorem 🌱
- Capability Maturity Model 🌱
- Capacity 🌱
- Cardinality 🌱
- Cargo-culting 🌱
- The Cathedral and the Bazaar 🌿
- Cell-based architecture 🌿
- Certificate authority 🌱
- Change data capture 🌱
- Chaos engineering 🌿
- Checksum 🌱
- CI/CD 🌱
- CIA triad 🌱
- CIDR (Classless Inter-Domain Routing) 🌱
- Circuit breaker 🌱
- Clean architecture 🌿
- Clean code 🌿
- Cleanroom 🌿
- Client-server architecture 🌿
- Cloud computing 🌿
- Cloud networking 🌿
- Cloud service providers 🌱
- Clustering 🌿
- Co-existence 🌱
- Code conventions 🌿
- Code for the maintainer 🌱
- Code kata 🌱
- Code freeze 🌿
- Code reuse 🌿
- Code smell 🌱
- Cohesion 🌿
- Combinator 🌿
- Command 🌱
- Command Query Responsibility Segregation (CQRS) 🌱
- Command query separation 🌱
- Commit early, commit often 🌱
- Common closure principle 🌱
- Common reuse principle 🌱
- Communication patterns 🌱
- Compatibility 🌱
- Completeness 🌱
- Complexity 🌿
- Compliance 🌱
- Compliance testing 🌱
- Component 🌱
- Composition 🌿
- Computer-Aided Software Engineering (CASE) 🌿
- Change data capture (CDC) 🌱
- Computer science 🌱
- Computer vision 🌿
- Concatenative language 🌱
- Concept 🌱
- Conceptual integrity 🌱
- Concern 🌱
- Concurrency 🌿
- Confidentiality 🌱
- Configuration management 🌿
- Consensus algorithms 🌱
- Consistency 🌱
- Consistent hashing 🌱
- Constraint 🌱
- Container 🌱
- Container orchestration 🌳
- Containerization 🌳
- Content delivery networks 🌱
- Context 🌱
- Context engineering 🌿
- Context view 🌱
- Continuous delivery 🌱
- Continuous deployment 🌱
- Continuous integration 🌱
- Conway’s law 🌳
- Connascence 🌿
- Correctness 🌱
- Coupling 🌳
- Crash-only 🌿
- Crash program 🌱
- Class-Responsibility-Collaboration (CRC) card 🌱
- Conflict-free replicated data types (CRDTs) 🌱
- Critical path analysis 🌱
- Cross-cutting concern 🌿
- Cross-functional teams 🌳
- Cross-site scripting 🌳
- Cryptography 🌿
- Crystal Clear 🌿
- Culture and folklore 🌱
- Cunningham’s law 🌱
- Curly’s law 🌱
- Cyclomatic Complexity 🌱
- Cynefin framework 🌿
D
- DACI framework 🌱
- Data-driven programming 🌿
- Data engineering 🌱
- Data integrity 🌳
- Data mesh 🌳
- Data modeling 🌳
- Data-oriented architecture 🌳
- Data-oriented design 🌳
- Data retention 🌿
- Data structures 🌳
- Database branching 🌱
- Databases 🌱
- Database indexes 🌳
- Database query optimization 🌳
- Dead letter queue 🌿
- Deadlock 🌳
- Debugger 🌳
- Decomposition 🌳
- Decoupling 🌳
- Denormalization 🌳
- Dependency 🌱
- Dependency injection 🌳
- Dependency inversion 🌳
- Deployment 🌱
- Deployment pipeline 🌱
- Deployment strategies 🌿
- Deployment view 🌱
- Design patterns 🌳
- Design principles 🌿
- Design rationale 🌱
- Developer Certificate of Origin (DCO) 🌱
- Developer experience (DX) 🌱
- Developer tooling 🌱
- DevOps 🌿
- DHCP 🌱
- Diagramming 🌱
- Diagrams-as-code 🌱
- Digital garden 🌿
- Directed acyclic graph (DAG) 🌱
- Disaster recovery 🌿
- Discovery 🌱
- Distributed caching 🌿
- Distributed databases 🌿
- Distributed file systems 🌿
- Distributed locking 🌿
- Distributed systems mechanisms 🌱
- Distributed system 🌱
- Distributed transaction 🌱
- DNS 🌱
- Do the simplest thing that could possibly work 🌱
- Do what I mean (DWIM) 🌱
- Docker 🌱
- Documentation 🌱
- Doerr’s law 🌱
- Document-oriented databases 🌿
- Document search 🌿
- Domain 🌱
- Domain-driven design 🌿
- Domain experts 🌱
- Domain engineering 🌱
- Domain model 🌱
- Domain-specific language (DSL) 🌱
- Downtime 🌱
- DRY – Don’t Repeat Yourself 🌱
- DSDM 🌱
- Durability 🌱
E
- ECMAScript 🌱
- Edge proxy 🌱
- Efficiency 🌱
- Egoless programming 🌱
- Elastic stack 🌱
- Embedded system 🌱
- Encapsulate what changes 🌱
- Encapsulation 🌱
- Encryption 🌱
- End-user development (EUD) 🌳
- Enterprise application software (EAS) 🌿
- Enterprise architecture (EA) 🌿
- Enterprise resource planning (ERP) 🌿
- Entity 🌱
- Entity Component System (ECS) 🌱
- Entity-Relationship Diagram (ERD) 🌳
- Entropy 🌱
- Envelope encryption 🌿
- Environment 🌱
- ETL – Extract, Transform, Load 🌿
- Evaluation 🌱
- Event bus 🌿
- Event-based systems 🌱
- Event-driven architecture 🌱
- Event sourcing 🌳
- Event storming 🌱
- Event stream 🌳
- Eventual consistency 🌳
- Evolvability 🌱
- Exception handling 🌱
- Execution model 🌱
- Execution orchestrator 🌿
- Exploratory testing 🌿
- Extensibility 🌿
- Extreme Programming (XP) 🌿
F
- Facade 🌱
- Factory 🌿
- Fail-fast 🌿
- Failover 🌿
- Fanout 🌿
- Fault tolerance 🌱
- Feature creep
- Feature-driven development 🌿
- Feature factory 🌱
- Feature flags 🌱
- File storage 🌿
- Firewalls 🌿
- FIRST principles of testing 🌱
- Fitness function 🌿
- Fitts’s law 🌱
- Flaccid agile 🌱
- Floating point arithmetic 🌿
- Forcing function 🌱
- Foreign keys 🌿
- Formal methods 🌿
- Forward-deployed engineer (FDE) 🌱
- Fragility 🌱
- FTP 🌿
- Function signature 🌱
- Function-as-a-Service (FaaS) 🌿
- Functional requirements 🌳
- Functional testing 🌿
- Fundamental Modeling Concepts (FMC) 🌱
G
- Gall’s law 🌱
- Garage startup 🌱
- Gateway 🌱
- Generative AI 🌱
- Geohashing 🌿
- Gherkin 🌿
- Global analysis 🌱
- Goodhart’s law 🌱
- Google Cloud Platform 🌱
- Gossip Protocol 🌿
- Governance 🌱
- Graceful degradation 🌱
- Graph databases 🌿
- GraphML 🌱
- Graph Modelling Language (GML) 🌱
- GraphQL 🌱
- GRASP 🌿
- Gray-box testing 🌱
- Greenspun’s tenth rule 🌱
- gRPC 🌱
- Grug-brained developer 🌱
H
- Hardware 🌿
- Hashing 🌿
- Heartbeat 🌱
- Heterogeneous architectural style 🌱
- Heuristic 🌱
- Hexagonal architecture 🌱
- Hierarchical (acyclic) decomposition 🌱
- High integrity 🌿
- High-level design 🌱
- High-performance computing (HPC) 🌿
- Hock principle 🌱
- Hofstadter’s law 🌱
- Horizontal scaling 🌱
- HTTP 🌱
- HTTP API 🌿
- Hybrid architecture style 🌱
- Hyrum’s law 🌱
- Hypervisor 🌱
I
- ICMP 🌱
- ICONIX 🌱
- Idempotent 🌿
- Immobility 🌱
- Inception 🌱
- Information hiding 🌿
- Inheritance 🌱
- In-memory databases 🌳
- Infrastructure as code 🌿
- Input validation 🌳
- Installability 🌱
- Installation testing 🌿
- Integrated development environments 🌱
- Integration testing 🌳
- Integrity 🌱
- Inter-process communication 🌱
- Interface definition language (IDL) 🌳
- Interface segregation principle 🌳
- Interfaces 🌳
- Internet Protocol (IP) 🌳
- Internet Protocol (IP) address 🌱
- Interoperability 🌱
- Inversion of control 🌱
- Isolation 🌱
- Iterative and incremental development 🌳
J
K
- Kafka 🌳
- Kanban 🌿
- Kerckhoffs’s principle 🌱
- Kernighan’s law 🌱
- Key-value cache (KV cache) 🌱
- Key-value stores 🌳
- KISS principle 🌿
- Knowledge graph 🌱
- Kubernetes 🌿
L
- Language Server Protocol 🌱
- Lady Lovelace’s objection 🌱
- Large language model (LLM) 🌳
- Latency 🌳
- Law of Demeter 🌿
- Laws and principles 🌱
- Laws of software evolution 🌿
- Layered architecture 🌱
- Lazy loading 🌱
- Leaky abstractions 🌱
- Lean software development 🌿
- Learnability 🌱
- Leetspeak 🌱
- Lightweight text markup languages 🌱
- Lindy’s law 🌱
- Linting 🌱
- Linus’s law 🌱
- Linux 🌱
- Liskov substitution principle 🌿
- Literate programming 🌿
- Little’s law 🌱
- Load 🌿
- Load balancer 🌱
- Load balancing 🌿
- Load testing 🌿
- Local-first software 🌿
- Locking 🌿
- Logging 🌿
- Logic table 🌱
- Long polling 🌿
- Loop engineering 🌿
- Low-level design 🌱
M
- Machine learning 🌱
- Maintainability 🌱
- Maker’s schedule 🌱
- Managed hosting 🌱
- Management information systems (MIS) 🌱
- Manual testing 🌿
- MapReduce 🌱
- Mashup 🌱
- Materialized view 🌿
- Maturity 🌱
- Mechanical sympathy 🌱
- Memoization 🌱
- Memory allocation 🌿
- Message broker 🌿
- Message-driven architecture 🌱
- Message queues 🌱
- Messaging protocols 🌿
- Metcalfe’s Law 🌱
- Metrics 🌱
- Micro front-end 🌿
- Microservices 🌳
- MIPS (Million Instructions per Second) 🌱
- Mob programming 🌿
- Model 🌱
- Model access layer 🌿
- Model Context Protocol 🌿
- Model-driven architecture (MDA) 🌿
- Model-driven development 🌿
- Model-view-controller (MVC) 🌱
- Model-view-update (MVU) 🌱
- Model-view-viewmodel (MVVM) 🌱
- Modeling 🌿
- Modeling notations and methods 🌱
- Modifiability 🌱
- Modular design 🌿
- Modular monolith 🌱
- Modularity 🌱
- Module 🌱
- Monitoring 🌿
- Monolith 🌱
- Moore’s law 🌱
- Multi-factor authentication (MFA) 🌱
- Multimodal AI 🌱
- Multi-tenant 🌿
- Mutation testing 🌱
- The Mythical Man-Month 🌱
N
- Nanoservices 🌿
- Natural language processing (NLP) 🌱
- Network protocols 🌿
- Ninety-ninety rule 🌱
- Node 🌱
- Non-functional requirements 🌳
- Non-repudiation 🌱
- Nonce 🌿
- Normalization 🌿
- Norvig’s law 🌱
- NoSQL databases 🌿
- Not invented here! 🌱
- Notation 🌱
O
- Object-oriented programming (OOP) 🌿
- Object storage 🌱
- On-call 🌱
- Observability 🌱
- Observer pattern 🌿
- Onion architecture 🌿
- Ontology 🌱
- Open-closed principle 🌳
- Open-weight model 🌿
- Operability 🌱
- Optimize for deletion 🌱
- Orthogonality 🌱
- OSI model 🌿
- OWASP – Open Worldwide Application Security Project 🌿
P
- PACELC theorem 🌿
- Package principles 🌱
- Pagination 🌿
- Pair programming 🌿
- Parallelism 🌿
- Parameter passing 🌱
- Pareto principle 🌿
- Parkinson’s law 🌿
- Partition tolerance 🌱
- Pattern 🌱
- Peer-to-peer (P2P) architecture 🌳
- Penetration testing 🌳
- Perfect forward secrecy 🌱
- Performance 🌱
- Performance efficiency 🌱
- Performance testing 🌱
- Persona 🌿
- Perspective 🌱
- Peter principle 🌿
- PERT chart 🌱
- Phased commit (2PC, 3PC) 🌱
- Pipe-and-filter 🌳
- Platform-as-a-service (PaaS) 🌱
- Platform engineering 🌿
- Polymorphism 🌿
- Port 🌱
- Portability 🌱
- Ports and adapters 🌱
- POSIX 🌱
- Premature optimization 🌿
- Preprocessing 🌿
- Presentation-abstraction-control (PAC) 🌱
- Principal 🌱
- Principle of least astonishment 🌿
- Privacy 🌿
- Problem space 🌱
- Processor architectures 🌿
- Product data 🌱
- Product requirements document (PRD) 🌱
- Profiling 🌿
- Prompt engineering 🌱
- Programming paradigm 🌱
- Project paradox 🌱
- Prototyping 🌱
- Protocol Buffers 🌿
- Proxy 🌱
- Proxy server 🌿
- Pseudo-Randomness 🌱
- Public Key Infrastructure (PKI) 🌱
- Publish-subscribe (pubsub) pattern 🌱
- Pull architecture 🌿
- Push architecture 🌿
Q
R
- RAAML - Risk Analysis and Assessment Modeling language 🌱
- RabbitMQ 🌱
- RAD 🌿
- Rainbow table 🌿
- Rate limiting 🌳
- Rational Unified Process 🌱
- Reactive programming 🌳
- Reactive systems 🌿
- Recoverability 🌱
- Recovery testing 🌱
- Recursive self-improvement (RSI) 🌱
- Redesign 🌱
- Redis 🌱
- Redundancy 🌿
- Refactoring 🌿
- Reference architecture 🌱
- Reference Model for Open Distributed Processing 🌱
- Referential integrity 🌱
- Registry 🌱
- Regression testing 🌿
- Relational database management systems (RDBMS) 🌿
- Relationship 🌱
- Release early, release often 🌿
- Release model 🌿
- Reliability 🌱
- Remote procedure call (RPC) 🌱
- Replaceability 🌱
- Replay attack 🌱
- Replication 🌿
- Repository 🌱
- Request-response communication 🌿
- Requirements 🌿
- Requirements engineering 🌿
- Requirements and product management 🌱
- Resilience 🌿
- Resource utilization 🌱
- Resource-oriented architecture 🌳
- REpresentational state transfer (REST) 🌳
- Result cache 🌳
- Retry 🌿
- Reusability 🌱
- Reuse/release equivalence principle 🌱
- Reverse engineering 🌳
- Reverse proxy 🌳
- Rigidity 🌱
- Ring zero escalation 🌿
- Risk 🌱
- Robustness principle 🌿
- Role-based access controls 🌳
- Rollback 🌳
- Rolling deployments 🌳
- Rolling release 🌿
- Round-trip engineering 🌱
- Round-trip time (RTT) 🌳
- Rubber ducking 🌿
- Rule of least power 🌳
- Runbook 🌱
- Runtime view 🌱
S
- Safety-critical system 🌳
- Saga 🌱
- Salt 🌱
- Sandbox 🌱
- Scaffolding 🌱
- Scalability 🌱
- Scaling laws 🌱
- Scatter-and-gather 🌱
- Scenario 🌱
- Schema evolution 🌱
- Scope creep 🌳
- Scrum 🌱
- Secure development lifecycle 🌱
- Security 🌱
- Security headers 🌱
- Security testing 🌿
- Secure by design 🌱
- Self-contained system 🌱
- Semantic diffusion 🌱
- SEMAT 🌱
- Sensitivity point 🌱
- Separation of concerns 🌱
- Sequence diagram 🌱
- Serverless architecture 🌳
- Serverless computing 🌳
- Service 🌱
- Service discovery 🌿
- Service level agreement (SLA) 🌱
- Service mesh 🌿
- Server-Sent Events (SSE) 🌱
- Service-oriented architecture 🌱
- Sharding 🌱
- Shell 🌱
- Shift left 🌱
- Shirky principle 🌱
- Shrinkwrap software 🌱
- Signature 🌱
- Software systems 🌱
- Split brain 🌱
- Stakeholder 🌱
- Structure 🌱
- Structure and Interpretation of Computer Programs 🌱
- Silver bullet 🌱
- Single point of failure (SPOF) 🌱
- Single responsibility principle 🌱
- Single source of truth 🌳
- Singleton 🌳
- Site reliability engineering (SRE) 🌳
- Smoke testing 🌿
- SMTP 🌿
- Snapshot tests 🌱
- Software architecture 🌳
- Software-as-a-service (SaaS) 🌱
- Software assurance 🌿
- Software bloat 🌳
- Software craftsmanship 🌳
- Software delivery and operations 🌱
- Software design 🌳
- Software quality 🌿
- Software quality engineering (SQE) 🌱
- Software rot 🌿
- SOLID 🌿
- Spatial databases 🌱
- Spec-driven development (SDD) 🌿
- Specification by example 🌿
- Spiral model 🌿
- Spoofing 🌱
- Spring Framework 🌱
- SQL 🌿
- SQL injection 🌿
- SSADM 🌿
- SSRF (Server-Side Request Forgery) 🌿
- Stable abstractions principle 🌱
- Stable dependencies principle 🌱
- Stack language 🌱
- Stamp coupling 🌿
- Stand-in 🌱
- State 🌱
- Stateful design 🌱
- Stateless 🌱
- Static analysis 🌱
- Stepwise refinement 🌱
- Story-driven modeling 🌱
- Strangler fig pattern 🌱
- Strategy pattern 🌱
- Stream processing systems 🌱
- Streaming 🌱
- Stress testing 🌱
- Structured data 🌱
- Structured programming 🌱
- Sum data 🌱
- Surgical team 🌱
- SWEBOK 🌱
- Symmetric cryptography 🌱
- Synchronization 🌱
- Synchronous communication 🌱
- System 🌱
- Systems Modeling Language (SysML) 🌱
- System design 🌿
- System requirements specification (SRS) 🌿
- System health checks 🌱
- System testing (aka end-to-end or e2e testing) 🌳
T
- Task queue 🌿
- TCP 🌱
- Technical context 🌱
- Technical debt 🌳
- Telemetry 🌿
- Template method 🌱
- Temporal coupling 🌱
- Tesler’s law 🌿
- Test-driven development 🌳
- Test harness 🌱
- Testability 🌱
- Testing 🌳
- Thread safety 🌿
- Threat modeling 🌱
- Throughput (aka. bandwidth) 🌱
- Time behavior 🌱
- Time series databases 🌳
- Time-share computing 🌿
- TOGAF – The Open Group Architecture Framework 🌿
- Top-down design 🌱
- Traceability 🌿
- Tracing 🌱
- Trade-off 🌱
- Transactional databases 🌳
- Transaction 🌿
- Transformer architecture 🌱
- Transport Layer Security (TLS) 🌱
- Trivial Graph Format (TGF) 🌱
- TPS report 🌱
- Trunk-based development 🌱
- Type systems 🌱
- TypeScript 🌱
U
- Ubiquitous language 🌱
- UDP 🌱
- Unified Modeling Language (UML) 🌳
- Unified Process 🌿
- Uniform access principle 🌿
- Unit testing 🌿
- Unix 🌱
- Unix philosophy 🌳
- Uptime 🌱
- Usability 🌱
- Usability testing 🌱
- Use case 🌿
- User error protection 🌱
- User interface 🌱
- User interface aesthetics 🌱
- User-centered design 🌿
- User story 🌳
V
- Value object 🌱
- Value stream management 🌱
- Vector database 🌿
- Vega 🌱
- Version control 🌱
- Vertical scaling 🌿
- Vertical-slice architecture 🌱
- Vibe coding 🌱
- Virtual machine 🌱
- Virtualization 🌱
- Viscosity 🌱
- Visibility 🌿
- Visitor 🌱
- Voice-to-text 🌱
- Vulnerability databases 🌱
W
- Walking skeleton 🌱
- Waterfall (aka. stepwise) model 🌿
- Ways of working 🌿
- Web of Trust 🌱
- Web-oriented architecture 🌿
- Webhook 🌱
- WebSockets 🌱
- WebRTC (Web Real-Time Communication) 🌱
- White box 🌱
- White-box testing 🌿
- Wicked problem 🌱
- Wide-column stores 🌿
- Wirth’s law 🌱
- Workflow management system (WFMS) 🌱
- Worse is better 🌿
- Wrapper 🌱