• Работодателю вы нужны, чтобы деньги зарабатывать

• Рот не работает, работает только трудовой договор — читайте его, там буквы на бумаге и подписи.

• Если вы поймёте как эта машина деньги зарабатывает и поможете ей делать это лучше, то и с вами даже поделятся

• Профессионализм в работе — доставка продукта в срок. Самое ценное — время.

• Мир не помнит имён великих тимлидов, но мир помнит имена великих разрабов

• Делайте пет‑проджекты, не обращая внимания на то, что там в тренде. Пет‑проджект должен так же заканчиваться работающим результатом (любого качества), как и работа, иначе вы не профессионал и не уважаете проект и свой труд.

• Уметь разбить задачу на огромное число этапов и планомерно их сделать — это супер.

• Велосипеды рулят! Делайте свои языки программирования, свои алгоритмы шифрования, свои мессенджеры, свои соцсети, свои игры, свои 3D‑движки и держите лопату в бочке кала наготове, чтобы ловким движением раскидать субстанцию по мамкиным критикунам.

• Shipping is really hard and you have to make it your main priority

• Shipping doesn’t mean deploying code, it means making your leadership team happy

• You need your leadership team to trust you in order to ship

• Most of the essential technical work is in anticipating problems and creating fallback plans

• Scale back your implementation work as you approach launch so you’re free to jump on last-minute problems

• You should constantly ask yourself “can I ship right this second?”

Being prolific forces you to take notice. Taking notice develops your taste.

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.

This is a card game for teaching kids how to combine unix commands through pipes.

TempleOS has images in comments btw.

One of my favorite tools on the internet. I love the design! The person behind it: https://pketh.org/archives/ seems cool as well. They also worked on Glitch.

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.

Very good article about how queueing works, different methods to handle high load. Super cool interactive examples with animations!

LSP-AI is an open-source language server that serves as a backend for AI-powered functionality, designed to assist and empower software engineers, not replace them

Space Explorer

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

EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readable and they work nicely with version control systems.

• In the wonderful solarpunk future, we do not use telepathy

• In the wonderful solarpunk future, we have enough time to not do two things at once

How to backup photos using Apple, lightroom, nextcloud