I've written a number of little scripts over the years, many of which I use every day. Here's a little collection.

I argue for wider usage of delimiter-first in the code. three friends [tic, tac, toe] becomes three friends ・tic ・tac ・toe.

Cultivating memories instead of snapshots.

Knowing the consequences I want, what choice would create them? What big choice would nudge a hundred others that way?

Our design goals are safety, performance, and developer experience. In that order.

Contrary to popular belief, simplicity is also not the first attempt but the hardest revision

code, like steel, is less expensive to change while it's hot.

Safety

NASA's Power of Ten — Rules for Developing Safety Critical Code

• Use only very simple, explicit control flow for clarity.

• Put a limit on everything. Fail Fast

• Assertions detect programmer errors. The only correct way to handle corrupt code is to crash.

• Assertions are a safety net, not a substitute for human understanding.

  • Build a precise mental model of the code first.

  • encode your understanding in the form of assertions,

  • write the code and comments to explain and justify the mental model to your reviewer,

  • and use VOPR as the final line of defense, to find bugs in your and reviewer's understanding of code.

• No memory may be dynamically allocated (or freed and reallocated) after initialization.

• Declare variables at the smallest possible scope, and minimize the number of variables in scope.

• Good function shape is often the inverse of an hourglass: a few parameters, a simple return type, and a lot of meaty logic between the braces.

• Centralize control flow. When splitting a large function, try to keep all switch/if statements in the "parent" function, and move non-branchy logic fragments to helper functions.

• Centralize state manipulation. Let the parent function keep all relevant state in local variables, and use helpers to compute what needs to change, rather than applying the change directly.

Developer Experience

• Add units or qualifiers to variable names, and put the units or qualifiers last, sorted by descending significance. latency_ms_max rather than max_latency_ms.

• Callbacks go last in the list of parameters.

• Order matters for readability (even if it doesn't affect semantics). On the first read, a file is read top-down, so put important things near the top. The main function goes first.

• Don't overload names with multiple meanings that are context-dependent.

Server racks as home furniture.

Trigger warnings for movies, TV, books, video games and more!

I’ve completely eliminated the alarm clock from my morning routine for about six months. The biggest impacts it's had on my life are: I’ve become a morning person. I wake up feeling great and feel less sleepy during the day.

• Приложения для сбора хайлайтов из статей и книг не помогают запоминать прочитанное

• Для того, чтобы запоминать прочитанное не нужна хорошая память

• Лучший способ запомнить прочитанное — понять то, что ты прочитал

• Чтобы на самом деле понять прочитанное, нужно приложить усилия

• Объясняй другим идеи, чтобы лучше понимать и запоминать их

• Заведи блог

• Участвуй в сетевых дискуссиях

• Откажись от автоматизации

Вывели с клиентом универсальную «инструкцию к терапии». На случай, если кому-то это нужно. Как часто и бывает, у него была популярная мечта сначала что-то поменять в голове, а потом зажить по-новому.

• make it for yourself first

• automate the backups; prefer to edit locally and push

• avoid SBCs (ie. RaspberryPi) and prefer PCs

• you don't have to let everyone in

Create an infinite amount of straightforward and readable git manual pages.

Service that generates random man pages mocking Git’s dense documentation style.

OLLOS is an experiment that organizes everything in my personal computing environment on one unified timeline.