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.

Really intresting comments

This question reminds me of the first time I met a blind programmer. I asked him how he managed to code, and he replied with something that stayed with me: a good programmer should organize software in such a way that every piece of code has a clear and logical place. The organization should be so intuitive that anyone could build a mental model of the structure and navigate it easily, even without seeing it.

A few basic rules for buying and using computers can save anyone significant amounts of money and produce the confidence required to try new things with computers.

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

I’ve completely eliminated the alarm clock from my morning routine for about six months. The biggest impacts it's had on my life are: I’ve become a morning person. I wake up feeling great and feel less sleepy during the day.

The best components are those that provide powerful functionality yet have simple interface.

Do not add layers of abstractions for the sake of an architecture. Add them whenever you need an extension point that is justified for practical reasons.

Want to read and reflect somewhere on every chapter one day...
How to remember that i want it?

27 conflicting answers and one weird conclusion. Many books believe they know how you should live. But each book disagrees with the next. In “How to Live”, each chapter believes it knows how you should live. And each chapter disagrees with the next.

Yon is a little UI for knowledge designed to be used every day. Add your notes, write your diary, and connect thoughts with bidirectional links. Explore your text through an acme-inspired interface to dive deep or go wide and always find your way back. Yon code and your notes are contained in a single standalone html file with no dependency, so that you can open the lid and tweak any part of it and make it your own.

История о том, как наше Бюро проектировало лучшую тележку для торговых сетей группы X5

Прекрасная статья о выборе человечества - покинуть планету с её проблемами или остаться и решать их? Обратиться к корням - природе, ручному труду или отвергнуть прошлое и адаптироваться к жестокому космосу?
Как сказал Курт Воннегут: "What makes you think you’re going anywhere?"
Подобные Дайсонам, в моей душе борются отец и сын, правда скорее поменявшись ролями. Тянуться к недостижимому космосу, к неизведанным и от того прекрасным технологиям с их бесконечными проблемами? Или обратить внимание на верную спутницу человека - прекрасную Землю и, возможно, обрести покой в отказе от амбиций?

Personal web site of Rek Bell - one of 100 rabbits.

How to backup photos using Apple, lightroom, nextcloud