2024-03-09 16:40:29 +00:00
|
|
|
|
- url: https://darthmall.net/weblog/2023/rss/
|
|
|
|
|
|
name: "Evan Sheehan: RSS?"
|
|
|
|
|
|
summary: >
|
|
|
|
|
|
There's a swing back to RSS right now, which I think is good. But I also think that Evan's
|
|
|
|
|
|
thoughts here are good. RSS can't be the only solution for how we take in the web. It can't
|
|
|
|
|
|
be the only solution for how we decentralize the web again.
|
|
|
|
|
|
|
|
|
|
|
|
Hat tip to [Greg Morris](https://gregmorris.co.uk/2024/01/29/visit-more-blogs) for his related
|
|
|
|
|
|
post that helped me find this one.
|
|
|
|
|
|
- url: https://ethanmarcotte.com/wrote/generative/
|
|
|
|
|
|
name: "Ethan Marcotte: Generative"
|
|
|
|
|
|
summary: >
|
|
|
|
|
|
A collection of quotes about AI from 1683 to 2024.
|
|
|
|
|
|
- url: https://seldo.com/posts/ai-ml-llms-and-the-future-of-software
|
|
|
|
|
|
name: "Laurie Voss: On AI, ML, LLMs and the future of software"
|
|
|
|
|
|
summary: >
|
|
|
|
|
|
A level-headed explanation of what exactly AI, ML, and LLMs are. "LLMs are really complex markov
|
|
|
|
|
|
chains; but the really complex part makes them qualitatively different" has been by go-to
|
|
|
|
|
|
explanation of LLMs. I disagree, however, with the idea that LLMs "understand" anything. LLMs
|
|
|
|
|
|
contain big statistical models of sentence and paragraph structure, and of the relationship
|
|
|
|
|
|
between words and phrases. This allows them to generate text that is more of a statistical match
|
|
|
|
|
|
for text written by humans. That humans see this as "understanding" is a form of pareidolia.
|
|
|
|
|
|
|
|
|
|
|
|
This distinction is narrow, but important.
|
2024-03-07 15:29:15 +00:00
|
|
|
|
- url: https://coryd.dev/posts/2024/towards-a-quieter-friendlier-web/
|
|
|
|
|
|
name: "Cory Dransfeldt: Towards a quieter, friendlier web"
|
|
|
|
|
|
summary: >
|
|
|
|
|
|
A series of great principles for a better web! Hear, hear!
|
|
|
|
|
|
|
|
|
|
|
|
Side note: thanks to Cory for inspiring me to add a link log feed to this site,
|
|
|
|
|
|
inspired by his at coryd.dev.
|
|
|
|
|
|
- url: https://www.abstractmachines.dev/posts/am013-easy-to-write-code-considered-harmful/
|
|
|
|
|
|
name: "Leandro Ostera: AM013 – Easy-to-Write Code Considered Harmful"
|
|
|
|
|
|
summary: >
|
|
|
|
|
|
Leandro argues that the key to writing readable code is taking implicit context
|
|
|
|
|
|
and making it explicit. I agree!
|
|
|
|
|
|
|
|
|
|
|
|
This is also one reason I love Elixir. Many of the design choices in the language
|
|
|
|
|
|
and standard library encourage you to explicitly write what you mean-- even if it
|
|
|
|
|
|
is more keystrokes.
|
|
|
|
|
|
- url: https://soatok.blog/2024/02/27/the-tech-industry-doesnt-understand-consent/
|
|
|
|
|
|
name: "Soatok: The Tech Industry Doesn't Understand Consent"
|
|
|
|
|
|
summary: >
|
|
|
|
|
|
A brilliant lens for thinking about our relationship with tech products, design,
|
|
|
|
|
|
and terms of use. Opt-out "consent" isn't consent at all. "Maybe Later" isn't
|
|
|
|
|
|
consent either.
|
