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

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

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

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

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

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.

A markdown-like journal language for plainly writing logs , gantt charts , blogs , feeds , notes , journals , diaries , todos , timelines , calendars or anything that happens over time .

It has aesthetics associated with 90s and 2000s internet.

Testcontainers is an open source library for providing throwaway, lightweight instances of databases, message brokers, web browsers, or just about anything that can run in a Docker container.

Using static analysis, it finds bugs and performance issues, offers simplifications, and enforces style rules.

Generate an RSS feed from Telegram chats. You digital minimalism friend. - aigoncharov/telegram-to-rss

TempleOS has images in comments btw.

When a player starts a session, they are the car driver, and each person that joins is seated in one of the other three passenger seats.

Players are automatically connected via voice chat.

The radios stations are real-life internet radio streams and several of them are available in the game world.

LSP-AI is an open-source language server that serves as a backend for AI-powered functionality, designed to assist and empower software engineers, not replace them

if you are unfortunate enough to browse a fandom wiki without an ad blocker, you will experience what i like to call "attention assault"

if you are a fandom wiki owner & you would like to move your wiki content elsewhere, i will offer you my expertise at $0/hour. i know lots about servers, software, and maintenance. just email me - let's get you out of fandom's ecosystem.

This is a book about building applications using hypermedia systems.

If you had the choice to sculpt a leg chair out of wood or write a full-fledged audio engine, complete with kernel drivers and whatnot, inside an app for controlling monitor brightness, what wou… Wait, no, that's not a question, you would do the leg chair for sure. There's no way that other thing makes sense.

In many other languages, you have to not only evaluate testing libraries, but also write your tests in a style that complies with that library’s expectations. Gophers are blessed to have a thoroughly adequate solution out-of-the-box, and even further blessed to have an active ecosystem where folks are making in-depth testing a walk in the park.

Автор обсуждает использование git для управления проектами и проблемы с ним, а так же рассматривает альтернативы.

Constantly updating collection of beautiful workspaces. There is short description of items and software from an author, some ideas about creativity.

• 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

TL;DR В статье рассказывается о том, как мне удалось перевести чтение лент в ВКонтакте, Telegram, Facebook, Instagram, Reddit и почтовых рассылок в единый сервис InoReader. Причем почти без написания своих велосипедов