Skip to main content

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.

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.

Language & Framework Folders

Language and Framework further will always be split into two sections:

  • Internals
  • Ecosystem So an article such as Autocomplete CLI Flags is 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

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. Process Based Organization

See my current process here

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 hire me, please contact me via LinkedIn. While I can be reached via other platforms, LinkedIn is your best bet to get a speedy response. (or email if you have it... ...but I usually don't make those public)