I argue for wider usage of delimiter-first in the code. three friends [tic, tac, toe] becomes three friends ・tic ・tac ・toe.

Marginalia got a new design and a new domain.

ntfy is a simple HTTP-based pub-sub notification service. It allows you to send notifications to your phone or desktop via scripts from any computer, and/or using a REST API.

curl \
  -d "Backup successful 😀" \
  ntfy.sh/mytopic

Free notifications!

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.

Server racks as home furniture.

Using static analysis, it finds bugs and performance issues, offers simplifications, and enforces style rules.

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.

Reads like some sci-fi story. How is that even a thing??

Science and engineering usually create consistent results. Generally, when you figure out how to make something, you can repeat that at will to make more of something. But what if, one day, you ran the same process, and got different results? You double-checked, and triple-checked, and you kept ending up with a different end product instead?
Perhaps it wasn’t the process that changed, but the environment? Or physics itself? Enter the scary world of disappearing polymorphs.

When a player starts a session, they are the car driver, and each person that joins is seated in one of the other three passenger seats.

Players are automatically connected via voice chat.

The radios stations are real-life internet radio streams and several of them are available in the game world.

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

Very cool wiki design with backlinks, links preview etc

Personal website of Gwern Branwen (writer, self-experimenter, and programmer): topics: psychology, statistics, technology, deep learning, anime

Space Explorer

A *web site* search engine, instead of a web page centered one!

HackerNews post about Betula

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

Classic MacOS & GS/OS widget library for linux (and other?) - buserror/libmui

Я согласен с тем, что логику нужно разносить по сервисам. Но сервисы должны использовать общую шину данных: базу, очередь сообщений, файлы в S3 в конце концов. Гонять друг другу JSON выглядит хорошо в теории, но на практике — фу.

Условный Постгрес выплюнет миллион записей за доли секунды. Забрать этот же миллион из другого сервиса — приключение на неделю. Тут и метрики, лимиты, квоты, сетевые спайки, etc… А когда таких запросов несколько, сервис ложится спать.

Innovation tokens and whatnot.