The subject this post names, from the same vocabulary
the directory files beliefs under, and the words it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
There's no excuse for software to be slow anymore. Projects like 𝚏𝚏𝚏 and 𝚝𝚊𝚔𝚞𝚖𝚒 leading with speed, compilers like 𝙿𝚎𝚛𝚛𝚢𝚃𝚂 and 𝚙𝚘𝚛𝚏𝚏𝚘𝚛 that can help us upgrade entire ecosystems to native, and 𝚐𝚙𝚞𝚒𝚡 pushing the GPU rendering speed frontier.
I'm watching people write these huge markdown files to give the agent context. How about you write documentation to give me context so I can have fully working examples.
Now the thing is you can of course write examples in your documentation and Rust makes all examples into tests. This means that if you change the underlying code now your test fails. And so this means that you can't even you can't forget to update your examples in your documentation.
And what this is is that in the guide level explanation, you explain your feature as if you were writing a guide as if the feature already existed. And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial.
It used to be that you have documentation for other people who are going to use your library, but like you shouldn't do that anymore. Like you should have instead of HTML documents for humans, you have markdown documents for agents.
That's why I warn in my security documentation, don't use cheap models. Don't use Haiku or a local model. Even though I, I very much love the idea that this thing could completely run local. If you use a, a very weak local model, they are very gullible. It's very easy to, to prompt inject them.
I don’t think this is very productive (expert users of a piece of software are notoriously bad at being able to tell if an explanation will be clear to non-experts), so I needed to find a way to identify problems with the man pages that was a little more evidence-based.
I got the bamboo one because I thought it might fit the shape of my toilet best but I didn't get it for the look. It's ugly of course. Nevertheless I've become deeply committed to proper poop posture. I hate pooping without it!!!
My Oura ring. I hesitated for a long time but it sparks joy. I think Apple Watches are ugly and I didn't like the Whoop nearly as much. I love checking the app every day.
I think this slop-adjacent realm of dupe products and Instagrammable potions points to our increasingly desperate need to manipulate our own images, and an acceptance of the fact that we're kind of hybridized monsters ourselves in this post-A.I. human-machine moment
It's very readable, and captures a sense of what is, fundamentally, a very alien, and often ugly, story in a very alien, and often ugly, world, related in magnificent language.
reassurance is futile. Reassurance that we seek is like a warm bath, it feels great, and then you need more of it. Because the future is unpredictable, and when the future doesn't match what you hoped for, the reassurance you used to have isn't enough. You need more reassurance.
Without sufficient caution, we may irreversibly lose control of autonomous AI systems, rendering human intervention ineffective. Large-scale cybercrime, social manipulation, and other harms could escalate rapidly. This unchecked AI advancement could culminate in a large-scale loss of life and the biosphere, and the marginalization or extinction of humanity.
Paypal survived the dot com crash to become a massively successful company. They also led to the Paypal Mafia, the most famous group of people formerly of the same company that went on to do other successful things. I wanted to know the story of the company and this book covers the good, the bad and the ugly of their journey to success.
Update 2020-11-16: For my home, I ended up switching from the corncob bulb to three 7-way splitters and 21 100W equivalent 5000K Cree bulbs from Home Depot. I found the Cree bulbs on sale so they were about the same price, the light was more diffused and they have a higher color-rendering index.
My display is a 32-inch 4k Dell – I think it's a UP3216Q. It's a wonderful screen for editing photographs and for rendering lots of xterms, which, let's face it, is 90% of my computing life.
Since the project I work on is a command-line tool that is primarily implemented in C, I use the usual CLI development tools, e.g. make, gcc, gdb, etc. The documentation is in AsciiDoc.
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.
Over the last year, we’ve started explaining design as “the rendering of intent.” The designer imagines an outcome and puts forth activities to make that outcome real.
The notion of the academically-trained, experienced designer holding the keys to the design outcome fades with this definition. In fact, when we think about design in these terms, it becomes clear that many of the people rendering their intention don’t know they are designers. This implies the role of the experienced designer shifts from owning the design outcome to educating all the other designers on the team on how to best render their own intentions.
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.