Digital Garden

This Dendron vault of tech knowledge is organized according to domains and their sub-domains, along with specific implementation of those domains.

For instance, Git itself is a domain. Sub-domains of Git would include things like commit, tags, reflog etc. implementations of each of those could be cli, strat (strategies), inner, and so on.

The goal of the wiki is to present data in a manner that is from the perspective of a querying user. Here, a user is a programmer wanting to get key information from a specific domain. For instance, if a user wants to use postgres functions and hasn't done them in a while, they should be able to query postgres.functions to see what information is available to them.

This wiki has been written with myself in mind. While learning each of these domains, I have been sensitive to the "aha" moments and have noted down my insights as they arose. I have refrained from capturing information that I considered obvious or otherwise non-beneficial to my own understanding.

As a result, I have allowed myself to use potentially arcane concepts to explain other ones. For example, in my note on unit testing, I have made reference to the microservices note. If these notes were made with the public in mind, this would be a very bad strategy, given that you'd have to understand microservices to be able to draw that same parallel that I've already drawn. Since these notes are written for myself, I have been fine with taking these liberties.

What I hope to gain from this wiki is the ability to step away from any given domain for a long period of time, and be able to be passably useful for whatever my goals are within a short period of time. Of course this is all vague sounding, and really depends on the domain along with the ends I am trying to reach.

To achieve this, the system should be steadfast to:

  • be able to put information in relatively easily, without too much thought required to its location. While location is important, Dendron makes it easy to relocate notes, if it becomes apparent that a different place makes more sense.
  • be able to extract the information that is needed, meaning there is a high-degree in confidence in the location of the information. The idea is that information loses a large amount of its value when it is unfindable. Therefore, a relatively strict ideology should be used when determining where a piece of information belongs.
    • Some concepts might realistically belong to multiple domains. For instance, the concept of access modifiers can be found in both C# and Typescript. Therefore, this note should be abstracted to a common place, such as OOP.

This Dendron vault is the sister component to the General Second Brain.


Throughout the garden, I have made use of tags, which give semantic meaning to the pieces of information.

  • ex. - Denotes an example of the preceding piece of information
  • spec: - Specifies that the preceding information has some degree of speculation to it, and may not be 100% factual. Ideally this gets clarified over time as my understanding develops.
  • anal: - Denotes an analogy of the preceding information. Often I will attempt to link concepts to others that I have previously learned.
  • mn: - Denotes a mnemonic
  • expl: - Denotes an explanation


UE (Unexamined) Resources

Often, I come across sources of information that I believe to be high-quality. They may be recommendations or found in some other way. No matter their origin, I may be in a position where I don't have the time to fully examine them (and properly extract notes), or I may not require the information at that moment in time. In cases like these, I will add reference to a section of the note called UE Resources. The idea is that in the future when I am ready to examine them, I have a list of resources that I can start with. This is an alternative strategy to compiling browser bookmarks, which I've found can quickly become untenable.

E (Examined) Resources

Once a resource has been thoroughly examined and has been mined for notes, it will be moved from UE Resources to E Resources. This is to indicate that (in my own estimation), there is nothing more to be gained from the resource that is not already in the note.


This heading is for inexhaustible resources.

  • A prime example would be a quality website that continually posts articles. - Another example would be a tool, such as software that measures frequencies in a room to help acoustically treat it.

  1. .NET
  2. API
  3. Alfred
  4. Android
  5. Apache
  6. Apache Flink
  7. Apollo
  8. Arduino
  9. Auth
  10. Aws
  11. Azure
  12. BIOS
  13. Babel
  14. Binary
  15. BitTorrent
  16. Bitcoin
  17. Blockchain
  18. Browser
  19. C
  20. C#
  21. CAN
  22. CGI (Common Gateway Interface)
  23. CMS
  24. CSS (Cascading Style Sheets)
  25. Caddy
  26. Chrome
  27. Cloudflare
  28. Colors
  29. CouchDB
  30. Crypt
  31. DB
  32. DBeaver
  33. DNS
  34. Data
  35. Datadog
  36. Debugging
  37. Dendron
  38. Deploy
  39. DevOps
  40. Development Process
  41. Docker
  42. Elastic Search
  43. Email
  44. Ember
  45. Enzyme
  46. Esbuild
  47. Eslint
  48. Express
  49. Fastlane
  50. Filesystem
  51. Firebase
  52. Game
  53. General
  54. Git
  55. GitHub
  56. GitLab
  57. Go
  58. Gradle
  59. Graphics
  60. Graphile Migrate
  61. Graphile Worker
  62. Graphql
  63. HTML
  64. HTTPS
  65. Hardware Components
  66. Homebrew
  67. Intellij
  68. Intersect
  69. JSON
  70. JSON Schema
  71. Java
  72. Javascript
  73. Jekyll
  74. Jest
  75. K6
  76. K8s
  77. Kafka
  78. Karabiner Elements
  79. LSP (Language Server Protocol)
  80. Lerna
  81. Linter
  82. Linux
  83. Mac
  84. Machine Learning
  85. Markdown
  86. Maven
  87. Memory
  88. Mobile
  89. Mongo
  90. Mongoose
  91. Mysql
  92. NAS (Network-attached Storage)
  93. Nestjs
  94. Network
  95. Nextjs
  96. Nginx
  97. Ngrok
  98. Nosql
  99. Objection
  100. Open API
  101. Opentracing
  102. Operating System
  103. PDF
  104. Paradigm
  105. Pg Xl
  106. Philosophy
  107. Postgraphile
  108. Postgres
  109. Presenting
  110. Product Design
  111. Protocol
  112. Python
  113. RSS Feed
  114. Ramda
  115. Raspberry Pi
  116. React Native
  117. Redis
  118. Redux
  119. Regex
  120. Retool
  121. Ruby
  122. Rust
  123. Rxjs
  124. SDK
  125. SQL
  126. Sanity
  127. Security
  128. Serverless Framework
  129. Shell
  130. Sketch
  131. Springboot
  132. Sqlite
  133. Storage
  134. Stripe
  135. Styled Components
  136. Svelte
  137. Svg
  138. Synology
  139. System Design
  140. Terraform
  141. Testing
  142. Third Party
  143. Tmux
  144. TypeGraphql
  145. Typescript
  146. Unified Modeling Language (UML)
  147. Unity
  148. Unix
  149. Vim
  150. Virtual Machine
  151. Vscode
  152. WatermelonDB
  153. Web
  154. Webpack
  155. Webserver
  156. Xcode
  157. YML
  158. Yarn
  159. iOS