About
Motivation / Intro / Getting Started
This is my docusaurus site! The goal of this site is to be a distillation of all the content I've collected over the years. The exact structure will be somewhat flexible and will evolve over time. All docs are "living" docs, I do not plan to include any versioning, but I will have self - notes included, for example wherever you see Pk_ToDo, it means that I need to do something. I am using this specific string so that I can search and find all my outstanding tasks. I may also add some other Pk_<something> tags for other use cases.
Original Structure
Most sections have a standard set of documents to start, but sometimes only a subset. (For example, important resources & basics may be bundled into the About doc if I don't have a whole lot to say). These docs should always be pinned to the top of the list:
- Important Basics: Basically a Quick start guide for when you are brand level to a language/stack/tech or it's been several months/years and you need a refresher.
- Important Resources: Best resources for this language/stack/tech. Each resource has an explanation of why/how it is useful/of high value.
- Interview Questions: Common interview Questions. Mostly Crowdsourced.
- Common Mistakes: Exactly what it sounds like. This includes things that may have been the only choice when implementing something but can be avoided by using newer language features.
- About: Likes and dislikes about the tech/language/stack, my history with the language/tech/stack, etc.
- Bookmarks: This is a direct export of my bookmarks. The difference between this and the "Important Resources" is the lack of organization and extra information. It is simply a snapshot of the things that I apparently cared enough to save as a bookmark.
Update & Some Internal Info
Update 20250506: With the advent of chatGPT, I'm unsure if I want to stick to these sections. Additionally, languages and frameworks that are not my current focus then just end up with a bunch of empty sections - which is obviously not a great UX. For now I've deleted these empty markdowns
I've added a front matter key disable to my front matter template. The idea behind this tag is that I would create some tool to analyze the front matter and exclude these files from the build. This tool obviuously isn't built yet, so in the mean time everyone would still see the empty docs, which is why i just decided to remove them (This isn't the only use case for this tool... today I saw that in one of the sections I had a todo.md... which would be fine in the internal section, but for the technical section I wouldn't want it to appear in the nav).
Sections have emojis to signal status:
| Emoji | Label | Meaning |
|---|---|---|
| 🕰️ | Historical | I haven’t focused on this in years and don’t plan to return. Content may exist, but it’s legacy. |
| ⏳ | Future | Not currently active. Minimal content, mostly project-specific or placeholders for future exploration. |
| 🧩 | Light Use | I actively use this tech (e.g., in projects), but I’m not deep diving or writing much about it. |
| (none) | Current Focus | Actively learning, writing about, or using this regularly. High likelihood of updates or new content. |
Language & Framework Folders
Language and Framework further will always be split into two sections:
- Internals
- Ecosystem
So an article such as
Autocomplete CLI Flagsis about how to add autocomplete to Node.js CLI tools. This is not really about Node.js itself and therefore will be in the ecosystem folder
Well this didnt happen either... I still like this organization, but think I need lots of content in section before I do this organization... also I feel that there is likely to be articles with tons of overap -- i guess the key is going by the title/topic... outbound links are normal, so maybe if im writing an I end up adding quite a bit about the other subject (internals / ecosystem), then just go heavy on the links (dont do a ton of explaining in place)
Background
Over the years I have created hundreds if not thousands of notes in evernote when learning new stacks, working on personal projects, studying, etc. I have an awesome tagging system. I've decided to transfer a subset of these notes to a blog. Over the next few months I'll be cleaning up these notes and publishing them here. There will be a major re-organization effort because not all concepts map 1 to 1, exporting/formatting/importing (ETL lol!), and integrating other sources... my bookmarks, youtube playlists, etc. I hope you find some value in the content here.
Deep Dive Into the Evolution of My Notes system
Pk_ToDo: Refine/fill out content
2009 - 2011 - Use native iphone notetaking app 2011 - Moving to Evernote 2011-2015 - Very light use 2017 - 2022 First SWE job in 2017, I had a long commute (~2hrs each way) and Evernote was the perfect app to use for all (most) my personal projects and studies. Minor changes to structure. Moved some projects to trello for task management. Begin using repeating tasks as well as task lists to group my tasks
2023-4
Moving to Tags as the primary organization system and using notebooks to represent the flow of notes.
See my current process here
2025: I've abandoned the Evernote transfer initiative. I'm already generating so much content with various explorations and projects that it's really just not worth the time investment to transfer everything over. (Since in most cases I don't plan to go back to focusing on those tools or stacks)
Notes:
I'm planning to hide some easter eggs and maybe some CTF style challenges around the site. There is one on this page... docItemMetadata
If you have any suggestions or want to collaborate or anything, please contact me via LinkedIn. While I can be reached via other platforms, LinkedIn is your best bet to get a response. (or email if you have it... ...but I usually don't make those public)