Ensō is a writing tool that helps you enter a state of flow. It does this by separating writing from editing and thus making it harder for you to edit yourself.
The text fades away as you type so you can focus on what you want to say instead of how you want to say it.
You can’t select or edit text, but you can download and review it once you’re done.

Hive the board game puzzles. A notation for games is also introduced.

via Optozorax

Wow so advanced

via Optozorax

Splits whole screen by named squares and moves cursor there.
Note: Windows and Linux support are still in development.
explanation: https://youtu.be/FYV4HbW2XCI

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

Trigger warnings for movies, TV, books, video games and more!

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.

По сути, выражение s[~i] эквивалентно выражениям s[-i - 1] и s[len(s) - i - 1], однако является более красивым и компактным вариантом записи.

I can't get the noise out of my head. People who watch the video express awe and disgust. And that is why Dutch software developer Bert Hubert's experiment is so powerful. It doesn't really uncover something that we shouldn't already know. Something we often choose to ignore. The brilliance is

merely 93% of paint splatters parse as valid Perl.

Simply do the math. If you have 180 friends on Facebook, which seems to be a low amount those days, if your friends take, on average, 10 days of vacation per year, you will have, on average, five friends on vacation every day. Add to this statistic that some people like to re-post pictures of old vacations and it means that you will be bombarded daily by pictures of sunny beaches and beautiful landscapes while you are waiting under neon light for your next boring meeting in a gray office. By design, Facebook makes you feel miserable.

Our mind, not the technology, is the bottleneck. We need to care about our minds. To dedicate time to think slowly and deeply.

Kind of controversial take on note taking systems. I can relate though, because i was lost in a burden of creating perfect knowledge management system for a long time without creating any knowledge. Simplest approach with commonplace notebook is what working for me now.
Comments are also useful.

Getting lost in your knowledge management system is a fantastic way to avoid creating things.
Most heart-stopping writing comes from synthesizing the previously unarticulated in the moment. Rather than reaching for your database, try channeling what’s in the air at this very second. These read/write errors are what we call originality.
Leonardo da Vinci kept all of his notes in one big book. If he liked something he put it down. This is known as a commonplace book, and it is about how detailed your note-taking system should be unless you plan on thinking more elaborately than Leonardo da Vinci.
Shun the useless adoption of the aesthetic of the useful. When something can be like work or like play, never make it work.

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

When perpetual avoidance is allowed, this familiarity never develops, and the kryptonite effect entrenches itself. The activity in question, however innocuous to everyone else, seems to wither your power and confidence whenever you get too close. Only by getting close despite the effect, and experiencing what dancing, algebra, or working with puff pastry is all about — rather than simply reacting to your old, scorned-outsider’s thoughts about it — can you neutralize the effect.

What is git-annex, how to set it up to store large files in Google Drive or NAS, and how I use it to seamlessly manage a git repository of 20GB (and counting)?

Blog post about very small linux distribution and small programs