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