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 topics like commit, tags, reflog etc., while implementations of each of those could be cli, strat (strategies), inner (inner workings), 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 basic implementations, as well as common patterns that have been employed in the past.

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 help explain others. For example, in my note on unit testing, I have made reference to the microservices note. The ability to analogize between different concepts captured in different notes allows an opportunity to build strong generalized understandings. Given that you'd have to understand microservices to be able to draw that same parallel that I've already drawn, these links won't work for everyone. Since these notes are written for myself, I have been fine with taking these liberties and leaning on them heavily.

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 notebook is the sister vault to the general Second Brain.

Tags

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. I try to go back after I have better understood the topic and clear out the notes of spec: tags
  • anal: - Denotes an analogy of the preceding information. When I can, I attempt to link concepts to others that I have previously learned.
  • mn: - Denotes a mnemonic
  • expl: - Denotes an explanation

Resources

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.

Resources

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.

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