Read on the website: I updated my website menu to be prettier on mobile, and I did not sacrifice accessibility and noJS folks! Go check it out and adopt it!
Read on the website: I dedicated this July to not using my laptop (and definitely not watching YouTube!) It’s a tentative win!
Read on the website: I have decided to go low-tech with my life lately. Here’s the low-tech know-how I use.
Read on the website: So I was considering starting a wiki. But it seems there are some unsurmountable value mismatches with me and wikis. So here’s a small reflection piece engaging Wittgenstein, literary theory, and a straw man idea of wikis.
Read on the website: It turns out, Armenian has at least one stenography system. The one designed in 1888 by a monastic order from Venice! Althought it’s imperfect, it’s a nice historic rarity.
Read on the website: Internet learned to speak gibberish that doesn’t always coincide with literary text. But it can be converted back to that. Here’s my experiment along these lines.
Read on the website: We need resilient systems that fall back to sanity when broken / discriminating. And not whatever.
Read on the website: There’s a bunch of guiding principles I follow when blogging to ensure what I do is kind to others. Here are some.
Read on the website: ed is a stupid simple text editor. sed is a nice streaming text processing tool. Why would one even want to use ed for anything, let alone for text processing if there's sed?
Read on the website: GESS is a Soviet / Russian standard for stenography (fast handwriting.) I want to use it for both Russian and English. And I dare say it works!
Read on the website: Atlas Engineer was a perfect Open Source Lispy team to work in. I was not the best teammate, though. Here’s how it worked in Atlas and what I’m worried about lately.
Read on the website: Binary Lambda Calculus is a really alluring idea. But it’s also hard to grasp and use! Here’s my list of complaints and obstacles to using BLC.
Read on the website: Kaktovik numerals are a surprisingly good counting system. It allows many arithmetic operations to be done visually and effortlessly. Though it takes some getting used to. Thus this page!
Read on the its own page: We all love READMEs. We also love websites. Why not have both in one file?
Read on the website: Package-inferred systems follow a useful one-file-per-package convention structure. But package-inferred systems themselves are harmful and should not be used. rss.xml:z15n
Read on the website: Markdown seems to have taken root. But it’s not really a good choice of markup language, because it’s incomplete, non-semantic, and tool-specific.
Read on the website: HTML is flexible and was shaped by generations of web practitioners. It has enough tricks up its sleeve to actually be nice to author. Here are some.
Read on the website: There are narrow screen CSS problems I often email people because of. These three fixes should be enough for most.
Read on the website: This was a hard year, filled with Lisp hacking, ed(1) editing and meta-programming, escapist writing, and heavy feeling. A good K-pop soundtrack tho.
Read on the website: Submodules give you the flexibility to fetch the dependencies, or not. And they enable more granular reproducible builds. Use submodules!
Frontend
Tutorial
Web Development
Culture
Entertainment
Programming
Web
Writing
AI
DevOps
Open Source
Data Visualization
HTML
Security
CSS