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

Splits whole screen by named squares and moves cursor there.
Note: Windows and Linux support are still in development.
explanation: https://youtu.be/FYV4HbW2XCI

What git config settings should be defaults by now? Here are some settings that even the core developers change.

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.

So true

How to use different git identities for different projects

• Отмена любого действия.

• Поддерживает чтение и запись в Git remote

• Легко переписывать историю коммитов, rebase становится тривиальным, коммиты (патчи) можно спокойно перемещать между ветками, конфликтов меньше

Сборник различных сценариев автоматизации и справочных материалов

Есть инструкция для почтового сервиса в кластере

Desktop-приложение с настоящим интерфейсом, с учетом реалий Windows

Why you should use and write man pages.

Local documentation that is easy to find is so much better. And man pages are powerful.

Эту статью я пишу во многом для нескольких друзей, которые решили приобщиться к этому тренду, и здесь будет обзор моего личного self hosted - про всякие разные штуки, которые показались полезны лично мне, и плотно заняли своё место на моём домашнем сервере.

• https://v5.chriskrycho.com/essays/jj-init/
• https://steveklabnik.github.io/jujutsu-tutorial/advanced/simultaneous-edits.html

The emerging golden age of home-cooked software, barefoot developers, and why the local-first community should help build it

По сути, выражение s[~i] эквивалентно выражениям s[-i - 1] и s[len(s) - i - 1], однако является более красивым и компактным вариантом записи.