Этот документ содержит список (roadmap) навыков, которые часто требуются backend разработчику web-приложений. Документ разделён на этапы (темы). Каждый этап разделён на пункты. Каждый пункт, в документе, подразумевает что:

• бекендер знает что это и какую проблему решает.

• бекендер знает для чего и когда следует применить.

• бекендер знает как с этим работать или знает где подсмотреть.

• при разработке или проектировании бекендер помнит про них и учитывает в приложении.

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

• Shipping is really hard and you have to make it your main priority

• Shipping doesn’t mean deploying code, it means making your leadership team happy

• You need your leadership team to trust you in order to ship

• Most of the essential technical work is in anticipating problems and creating fallback plans

• Scale back your implementation work as you approach launch so you’re free to jump on last-minute problems

• You should constantly ask yourself “can I ship right this second?”

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.

Some users have expressed discomfort when a knife is plunged into their chest, and this header allows those users to express their personal preferences.

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

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

• https://www.ultratechnology.com/1xforth.htm

Don't leave openings in which you are going to insert code at some future date when the problem changes because inevitably the problem will change in a way that you didn't anticipate. Whatever the cost it's wasted. Don't anticipate, solve the problem you've got.

Fast, modern and advanced photo management suite. Free and open source Nextcloud app.

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

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

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

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

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

• Заведи блог

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

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

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

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

Did you ever wake up in the middle of the night wondering what would happen if you applied JPEG-style lossy compression to text?

• In the wonderful solarpunk future, we do not use telepathy

• In the wonderful solarpunk future, we have enough time to not do two things at once

Using a single init.lua or vimrc configuration file for (Neo)Vim file is better than a multi folder/file layout approach.

you can save stuff and it will auto label it. single page with all links, quotes, etc. smart search, tags