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