I can't say enough how excellent a coding agent is at customizing Chrome with extensions. A huge productivity win. Every plugin interface you've ever blown off is now trivially usable.
But what we're seeing today with the modern models is that 5.5 and other models can think for if you scaffold them reasonably well, can think for weeks even um before having performance plateau on some of these benchmarks. And so, the point at which they plateau is simply too far out to reasonably test.
The thing that makes Kubernetes powerful, there's a data model. We gave infrastructure a type system. So instead of imperative shell scripts, you finally had types.
I think where Rust is really unique is in the combination of things. So on one hand, it it doesn't have a garbage collector and it it's usable in low-level context like the Linux kernel or firmware or whatever.
A more how-to pragmatic version of carving your own path. Includes some personal story of reinvention but more on experimentation that challenges our default scripts of success and ambition.
Accessibility has failed as a way to make computers usable for disabled users. My metrics for usable design are the same whether the user is disabled or not: whether it’s easy to learn the system, whether productivity is high when performing tasks, and whether the design is pleasant — even enjoyable — to use.
Hopefully I've convinced you that chatbots are a terrible interface for LLMs. Or, at the very least, that we can add controls, information, and affordances to our chatbot interfaces to make them more usable.
I felt like I often saw things that were good or bad design but didn't know why. Using beautiful full page pictures and simple explanations, this book goes through great principles for building simple & usable apps and sites.
Suckless offers an alternative to this continuous cycle of bloat and meaningless redesign. Suckless tools aim to keep things simple, minimal, usable and hackable by default.
A flexible enough system that can share rendering code between browser and server and provides tools for progressively loading scripts and styles will probably eliminate the colloquial distinction between websites and webapps. Both are reigned by the same UX principles. A blog and a CRM are fundamentally not that different.
I mentioned FastScripts for running quick scripts, but I also use TextExpander extensively, particularly for accelerating responses to customer support email.
I use Emacs for just a few things – browsing compressed archives, for example, and maintaining a todo list with org-mode. Evil-mode makes Emacs bearable.
I recently upgraded to the new Wacom Intuos which is wireless and has pen/capacitive touch support. The gesture support is very usable though it isn't as smooth as the glass Apple trackpads.
I write my books and comics scripts in Scrivener. Articles happen in Word, but I'm leaving it behind more and more, and just writing in Textedit to save myself all the time and energy associated with Microsoft.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.