Note taking is a skill that everyone seems to think that they have “solved” it. Whatever that means. They are not interested in investing their time to improve their note taking skill. No interest. No skill. No framework. Regardless of my critique, I think they draw conclusion fairly. Why? around 6 out of 10 people are knowledge worker 1. A subset of those need to use note at all. A subset of those who use notes need to create reusable notes.

Last edited [2022-06-23 Thu] Note: This blog will mostly likely ever changes as I form my preference of what I think a good blog should be. Blog. Piece. Article. Whatever you called it doesn’t matter. I will redefine it here. For the rest of the blog, I will use the word blog. I define blog as followed Blog is a collection of text with a goal’s guided narrative.

“Internetworking Architecture” (Leiner et al. 2009) was a fundamental design that enable machines and computers to communicate via internet regardless of underlying communication protocol. TCP/IP were implemented in UNIX operating system triggers a widespread adoption of internet (Leiner et al. 2009). Dispersion of protocols began in research community. Recall that predecessor of internet project (it was named “internetworking” at the time) was funded with the goal to increase speed and efficiency of research collaborations.

An EC2 instance has 4 state of life cycle: running, stopped, and terminated. Furthermore, state transition (or action) of an EC2 instance is launch, rebooting, pending, shutting-down, and stopping, see <ec2_life_cycle>. Figure 1: EC2 instance life cycle Validating that you have correct setup This article assumes that you have setup AWS credentials in your terminal environment. You can check out one of my article named “Setup AWS credentials for your AWS account and create new user” to help you set things up.

In AWS IAM, a policy is the smallest entity of permission. There are types of policies: resources-based policy, identity-based policy, and session-based policy. Figure 1: aws policies Policies can be attached to the following “identity”: user (1 account can have more than 1 users), role, and group (a group has many user) 1. user, role, and group are called identity. In AWS identity is called IAM identity and user, role, and group are called IAM user, IAM role, and IAM user group, respectively.

Straight’s recipe is similar but not identify to one used by MELPA. 1 A recipe describes which local repository to link the files from and how to clone that repository, if repo is not found locally. With this definition of recipe, one can think of recipe as a build step (recipe) of a package. Ultimately, a package is defined is a collection of files required for package’s build. striaght.el views a package in this manner.

This article is based on staright.el README which at the moment doesn’t have written document on how transaction works. So This is a work in progress until I either read straight.el codebase or summarize its documentation. Conceptually, stright.el clones Git repo and them symlinking files into Emacs’s load path. A packages in straight.el is defined as recipe as a files which was symlinked together. I have an article on recipe.

Ask youself the following question. How do you know your understand something? How can you access much do you understand it? If you don’t fully understand it yet, is there a way you can make a snapshot of things that you don’t understand such that you can replace this snapshot whenever a better “version” available to you. Why ability to assess your level of understanding it important? you asked.

When I first get into Emacs, I was a vim user before, so I picked up Doom Emacs without experience with vanilla Emacs. Transition has been smooth so far, but because I never has experience with Vanilla Emacs before when I encounter a bug in Doom Emacs. I always have to first figure out if it is Doom Emacs problem or Emacs problems. Because of this, I put out a new blog series to help me build a stronger foundation of Vanilla Emacs.

This article is an opinion piece on Comparison to other package managers. Emacs package manager are split into 2 categories: package.el wrapper or not package.el wrapper. One idea that straight.el emphasizes a lot is that straight.el manages commits rather than managing a whole a package. Some PM only accept latest commit. Other only accepts repo on github etc. I call this design decision a “smallest unit of design implementation.” Other unique takes on managing Emacs packages are Borg (assimilates packages as Git submodules into .