We backed up Spotify (metadata and music files). It’s distributed in bulk torrents (~300TB). It’s the world’s first “preservation archive” for music which is fully open (meaning it can easily be mirrored by anyone with enough disk space), with 86 million music files, representing around 99.6% of listens.

Some of Stephen Wolfram’s “productivity hacks” to make his days and projects more productive. Daily life, desk environment, outside the office, presentation setup, filesystem organization, Wolfram Notebook systems, databases, personal analytics.

I especially like the treadmill.

A - The task requirements and goals might not be clear enough. If you are trying to get yourself to “plan for a project” or “write a book” then it’s hard to identify the next actionable items. Put some time aside to figure out what physical things you can do to move the project forward. Try break down the larger tasks into the smallest pieces possible. The goal of the project might need identifying, or the requirements fleshed out from a supervisor.

B - The task might exceed your current competency. Sometimes we know what we have to do, but don’t know how to do it, and then we become avoidant rather than admitting this. In this case, it’s worth figuring out what you do know how to do and what you don’t know how to do, and be honest with that. Then slowly ask for help or read up on the things you don’t know.

C - The tasks might really not be worth it. Sometimes you are assigned tasks that don’t actually help you achieve your long-term goals, and so your brain demotivate you from doing them. Maybe the payoff is low, maybe you don’t learn anything new from them, or maybe a colleague you don’t like will gain credit for the tasks, or maybe you just wont be rewarded or appreciated for getting the tasks done.

How do you know what hourly rate you are worth? What factors should be taken into account? Here are my criteria.

A source-control branching model, where developers collaborate on code in a single branch called ‘trunk’ *,
resist any pressure to create other long-lived development branches by employing documented techniques. They
therefore avoid merge hell, do not break the build, and live happily ever after.

By wrapping errors and building well-formatted error messages, we can keep better track of where errors are happening. I often just add the name of the function being called to my error messages, but we can make the message say whatever we want. For example, I’ll often include parameter information in the error so I know which inputs caused the error.

The author doesn't like how modern UI:s are designed. Gives good examples.

Reduce friction in facial upkeep, build a healthy habit, and potentially save thousands on dental bills by chronologically ordering your toiletries.

an email-based bookmarking service

Выступление про текст, кодировки, шрифты, эмодзи, лигатуры, диакритику итп.

Хорошее

Пришло время рассказать о том, как устроена геополитика. Как и почему страны конкурируют между собой, строят и разрушают союзы, захватывают соседей или сами исчезают с карты. Для удобства и наглядности объяснять будем на простейших примерах — на кружочках.

Интерактивная карта, которая показывает изохроны пути от выбранной станции Нью-Йоркского метрополитена, используя данные GTFS из Управления городского транспорта Нью-Йорка