Many internal Yandex Cloud services rely on sidecar components and shared configurations to provide cross-cutting functionality such as:

• Log aggregation
• Common metrics collection
• Authorization
• Other platform-level capabilities

Managing these components can become challenging as the number of services and configurations grows. To simplify debugging, improve transparency, and make changes easier to track, the following approach was introduced.

Versioned Component Bundles

1. Individual components (sidecars, enriched configurations, and similar artifacts) are developed, released, and versioned independently.

Sometimes you need to calculate the sum of digits of an integer.

A straightforward approach is:

int sumDigits(int num) {
    int result = 0;

    while (num > 0) {
        result += num % 10;
        num /= 10;
    }

    return result;
}

This implementation performs both a modulo (%) and an integer division (/) on every iteration.

Reformulating the Problem

For simplicity, assume:

0 <= num <= 9999

Represent the number as:

An article that explains popular terms related to functional programming.

There are two typical ways to handle model state transitions:

1. state-machines (known typically from computer science)
2. behavior trees (adopted heavily by game industry)

[Here]((https://queenofsquiggles.github.io/guides/fsm-vs-bt/) is a nice article that:

1. explains high level concept
2. highlights pros and cons
3. provides simple speculative examples

The paper ‘A robust layered control system for a mobile robot’ written by Rodney Brooks that created the foundation that was adopted and generalized later by game industry to model behavior of non-player characters.

Nobody Gets Promoted for Simplicity

Some file system are case insensitive, other are not. When you try to checkout git repository, it’s possible to face this kind of error:

error: You’re on a case-insensitive filesystem, and the remote you are trying to fetch from has references that only differ in casing. It is impossible to store such references with the ‘files’ backend. You can either accept this as-is, in which case you won’t be able to store all remote references on disk. Or you can alternatively migrate your repository to use the ‘reftable’ backend with the following command:

Book

A brief and visual description of cognitive distortions.

Blog

Things that you should now about disk IO.
source

Here is a nice example how to use profile guided optimization for Go languange.