I like thinking of newsletters as a potential source of data. Not entirely public, not private either. Suitable for some local context, perhaps. Newsletters are also generally nice: Low tech, easy, distributed, basic sense of the audience, etc.
I saw a travel expert on the TV this morning interviewed on this. He said the only way to make it fair is for hotel bookings to include a lounger in the same way you book seats in the theatre. Obviously for extra money :)
Yeah this is key, a lot of people are still just looking at the number of params and thinking these models are toys. What Qwen 3.6 has shown is that reasoning and tool calling are just as important if not more.
Sorry, humans cannot hear up to 23kHz. Our hearing ends at 20kHz. Point.
After a decade on earth your loss is already at 18kHz or less. (Loss means not: you hear nothing but you do not hear as good as when you where born).
I still use the original steam controller, and I can tell you this is not true. If steam is not launched, the controller runs in a keyboard/mouse emulation mode and is not detected as a controller. This behavior is hardcoded in the firmware and cannot be changed.
> Btw - have you ever seen a UFO? I saw an orange orb once or twice.
When I was in high school (decades ago) I had “cartoonish” dreams in the back of my mind which later during my real life experiences came true! I only remembered and was able to interpret those childhood fantasies after they did.
Do you remember that “storm Area 51” meme? Approximately the same time there were sightings? That was when all of the remaining specimens were “terminated.”
They were not held at Area 51. They (most) were held in a nuclear launch facility under a mountain near San Diego.
“Thank you” seems to be similarly versatile in London. You can’t go 30 minutes without hearing it. Once when I was in a bookshop and approached the counter with a couple books to buy, the shopkeeper opened with “thank you”. To this day I don’t understand what that was about.
36 years in, solo founder now, and this matches what I'm living. The code stopped being the bottleneck a while ago — Codex and Claude ship features faster than I can decide which features are worth shipping. The Jevons Paradox point lands hard: I have to actively resist building things just because I now can in an afternoon. Solo doesn't escape the coherence problem either, it just turns it into a fight with my past self about what this product actually is.
The pop-up only appears if it detects a bias. If no bias is detected, your prompt sends instantly.
You can test the extension by entering an "isn't x better than y" prompt as an example, just to see the pop-up. I am working on an indicator that shows "all clear - no bias detected" in the next update.
The worst of it is GitHub issues. Half the bug reports I triage now are AI-generated perfect grammar, zero reproduction steps, and a stack trace from a hallucinated version of the library. You can't even tell people to RTFM because the FM was what the LLM hallucinated to them in the first place
using C was 100 times as productive as assembly. what happened was not that we finished software 100 times faster, but that we did projects 100 times bigger in the same time
same thing with smol local LLMs versus the big ones in the sky. your smol local LLM will only be able to tackle projects which are not comercially valuable anymore, because people expect 100x scope and features. which is fine as a hobby/art project
yes, we'll do amazing things with local LLMs in 2 years, but the big LLMs will do things beyond imagination (assembly vs C)
Great idea but you have to stick to your design language throughout the pages. The pill buttons become boxy on the feed page. The whole nav changes as well that damages user experience.
It could be complemented by a "Create" page for starting a new article, filtering bad titles and using a captcha to limit the vandals.
And another captcha for comment posting, which is already spammed, unfortunately.
I think a flagging mechanism will not be able to keep up with mass defacement.
Another suggestion: a daily dump of article titles, their connectivity and creation dates. I would love to visualize the underlying graph and its growth.
As someone who's been an engineer for 36 years and is now solo, you have a genuinely interesting perspective on performative productivity vs. actual output.
I've built a little plugin for Calibre (the E-book manager) that mimics the old but not forgotten X-Ray feature. Curie generates spoiler-free hints of characters and places and injects these as footnotes into your EPUBs. You can just press a characters name and be reminded who the heck they are. Very early version – would love to hear your feedback!
Notable that in each step, there’s an added abstraction; specifically, an authentication abstraction is the hardest one to reverse.
Using a passwordless login from scratch (magic link + Google OAuth2, sessions stored in Postgres without an external auth vendor) gets us around that altogether. The fears about why one would avoid it are generally not justified. Deliverability is the only true problem. Address that, with a proper provider for transactions, and we’re in boring territory – which is the most delightful kind.
To move from Clerk to Better Auth is logical if the choice is between sovereignty and convenience. It’s the core problem that any group doesn’t want to confront right away: “How much of this am I truly willing to own?”
Hi, Katie from Star Labs here. Yes, that's a totally fair comment, the
StarFighter took way longer to produce than we expected. It was a combination
of component supply problems, being a small manufacturer so understandably
lower priority at the factory, and then firmware development.
Also completely reasonable to want reviews. We have sent out a StarFighter for review and I know he is currently testing it before publishing on YouTube, so we are hoping it will be out soon.
There are also some completely independent reviews on Reddit if they are of interest to anyone:
The condensation argument is totally true.... Strikes me though the other metric Id look at is how long code survives before being re-written. Feels like for that one a bit early to tell...
By running my newsletters through local AI I could get a decent event calendar for myself:
https://joelsnewsletters.com/
Project: http://nowsletter.org/
Self host: https://github.com/joelgalvez/nowsletter
I like thinking of newsletters as a potential source of data. Not entirely public, not private either. Suitable for some local context, perhaps. Newsletters are also generally nice: Low tech, easy, distributed, basic sense of the audience, etc.