Хоттабыч

About compound interest

Avoid these things:

• Asking the developer how things should work: It’s your responsibility to know how a feature should work; if you don’t, how can you test it?

• Reporting bugs outside of the ticket: Avoid informal bug discussions, as they waste time for you and your team.

• Using vague phrases like “This does not work properly”: ‘Properly’ is unclear—specify exactly what’s wrong.

Instead of trying to shorten the time that our builds take, we order and chain them by complexity, thus gradually reducing the risk.

Johnny.Decimal is designed to help you find things quickly, with more confidence, and less stress.

Trying to make the case for permanent irrevocable digital identities, which unfortunately today, by de-facto, are email addresses.

A linter for Go that finds nil panics. It found several potential nil panic in Betula and Mycorrhiza codebases that I didn't bother fixing.

• https://github.com/uber-go/nilaway/

Minimizing your keyboard layout is a slippery slope.
34-keys has been reasonably comfortable to use, for both prose and program. My palms do not move across the desk at all, as I reach for keys. I mostly write Rust and Bash, and my layout has evolved to accomodate special characters from their grammars (angled brackets and hyphens, specifically). If you are on a similar journey, I would suggest focusing on accuracy and comfort over speed. Speed comes with time.

Статистика по беженцам из Украины

Никита собирает оплошности дизайна