20 random bookmarks
stuff me collect
stuff me collect
Very long, detailed, thorough guide on how to make Windows 11 less annoying, more productive and more ergonomic, with numerous changes and tweaks focused on privacy, security and usability, including reasons not to use Windows 11, pros and cons compared to earlier versions of Windows, tools needed before installation, USB media creation, how to skip online account creation, post-install questions, autoplay configuration, personalization, Firefox as default browser, app startup, offline maps, account sign-in options, time and language, gaming, entire privacy & security section in Settings - general, diagnostics and feedback, inking and typing, activity history, search permissions, and resource access, unnecessary services, cloud search, use of Winaero Tweaker to remove various options and features, Copilot, unnecessary apps, use of winget and Powershell to remove apps, Microsoft Edge removal, Open-Shell start menu alternative, autostart entries via Autoruns, optional removal of Windows Defender, optional configuration of Windows Update, Windows Explorer and taskbar tweaks, some other recommendations, and more
If I ever end up using Windows on a personal machine, I'll follow this guide
How exactly does sakura help you?
- Just drop it in, even on existing HTML content, to get a pretty-looking website (everything “just works”)
- Quick prototyping, especially when working on backend sites and can’t yet be bothered to fidget with CSS/HTML
- Building a quick (but pretty) site/blog for your best friend or aunt!
- No need to remember tons of different class names for every other CSS framework
- Works amazingly with markdown-generated HTML pages (eliminates the need for hacks like including .img img-responsive in <img></img> tags generated from markdown-parser
- Wonderful for people who aren’t really good or interested in design as sakura is nothing but a set of reasonable defaults
Author proposes to replace modern browsers with the following architecture. You make HTTP requests, server return you WASM blobs, they get executed. No built-in DOM.
DOM and its three languages are among the best technologies ever made, despite being so misused. It not being the default way will probably be disastrous. Think about accessibility!
But the idea is cool 🤔
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.
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.
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.
Отмена любого действия.
Поддерживает чтение и запись в Git remote
Легко переписывать историю коммитов, rebase становится тривиальным, коммиты (патчи) можно спокойно перемещать между ветками, конфликтов меньше
Сборник различных сценариев автоматизации и справочных материалов
Есть инструкция для почтового сервиса в кластере
Paced web reader (pwr) - an esoteric feed reader and workflow for keeping up to date online.
У скобочной записи есть преимущество: каждое выражение имеет начало и конец. Не обязательно писать на Лиспе, но нужно знать эту его сторону. Чтобы не выглядеть глупо, не хихикать и не прыскать в кулачок, когда случится увидеть Лисп.
Space Explorer
A *web site* search engine, instead of a web page centered one!
Similarly, one might begin to talk instead of watching talk-shows and to play instead of watching game shows — To value the entire spectrum of sensations as necessary members of the whole that is the deliberate existence, with its potential for failure, awkwardness, loneliness, harm and death included.
This is a book about building applications using hypermedia systems.
#1 Locally hosted web application that allows you to perform various operations on PDF files - Stirling-Tools/Stirling-PDF
Another perspective is that talent is closely tied to passion and motivation. People who are deeply interested and motivated in a specific area are often seen as having a natural talent for it. This perspective suggests that talent is nurtured through genuine enthusiasm and dedication.
TL;DR В статье рассказывается о том, как мне удалось перевести чтение лент в ВКонтакте, Telegram, Facebook, Instagram, Reddit и почтовых рассылок в единый сервис InoReader. Причем почти без написания своих велосипедов