svg logos gallery

It doesn’t matter what the project is; it matters that it is.

You don’t need to know where it’s going to lead. For that matter, it doesn’t have to lead anywhere. Nothing ever has to come of it. It’s ok if this project never even exists, as far as anyone else is concerned. Failure isn’t failure; it’s part of the process. It’s done when you’re done with it.

So whatever your side project is: I encourage you to pick it up, and let that part of you exist (again).

Do this full body split 3 times a week. The goal is to get your form down pat on the most basic and most important exercises in the gym.

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.

Статьи предназначены для максимально легкого вкатывания в плагинописание для Obsidian.
Официально документация Obsidian настоятельно рекомендует использовать TypeScript и npm и использует только такой подход в своем GitHub с примерами. Я же в свою очередь утверждаю, что если вы хотите просто сесть и написать малюсенький плагин, у вас нет необходимости даже в этом стеке.

Server racks as home furniture.

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

• Linux Memory Management at Scale (Arch Conf 2020)

Development Platform for building event-driven and distributed systems. Move faster with purpose-built local dev tools and DevOps automation for AWS/GCP.

Умерь жажду книжного знания, чтобы не роптать, когда придет смерть

A single-user “wiki” engine powering the ThoughtStorms wiki.

Author with cool visual style
Main page - https://johv.dk
He also uses Betula - https://links.johv.dk

For better or worse, I sometimes think. I have heard that I therefore am, but I’m unconvinced. Nevertheless, sometimes I write my thoughts down. Mostly just in my diary, but other times I publish them on the Web. This notebook contains those of my writings that are in a state somewhere between published and private.

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

Кажется уже не получится "улучшить" эл. почту. Нужна новая децентрализованная технология. Как сделать её простой для обычных пользователей? Как убедиться, что никто не сможет украсть или заблокировать твою личность? Идентификации просто по публичному адресу уже давно не достаточно.
Мессенджеры полностью заменили почту в плане общения, возможно их надо доработать?

Кстати, бетулу можно использовать как твиттер Х микроблог

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.

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