https://www.kobo.com/gb/en/ebook/tracts-n-50-antidote-to-the...
659 karma · joined August 20, 2009
https://www.kobo.com/gb/en/ebook/tracts-n-50-antidote-to-the...
...and that's it! Turns out the hard part is not riding a bike but riding a bike in a straight line. Once you've got the hang of riding wherever the bike seems to want to go, you can gradually learn to get it under control. Surprisingly easy!
I think Alan Kay said it best - what we’ve done with these things is hacked our own language processing. Their behaviour has enough in common with something they are not, we can’t tell the difference.
Ideally voices that don’t have a vested interest.
For example, give a superintelligence some money, tell it to start a company. Surely it’s going to quickly understand it needs to manipulate people to get them to do the things it wants, in the same way a kindergarten teacher has to “manipulate” the kids sometimes. Personally I can’t see how we’re not going to find ourselves in a power struggle with these things.
Does that make me an AI doomer party pooper? So far I haven’t found a coherent optimistic analysis. Just lots of very superficial “it will solve hard problems for us! Cure disease!”
It certainly could be that I haven’t looked hard enough. That’s why I’m asking.
It is.
https://books.google.co.uk/books/about/Tracts_N_50_Antidote_...
The interesting kind of programming is the kind where I'm figuring out what I'm building as part of the process.
Maybe AI will soon be superhuman in all the situations where we know exactly what we want (win the game), but not in the areas we don't. I find that kind of cool.
For the former you want (as mentioned) good presence info and undo. For the latter you (sometimes) want explicitly flagged conflicts and manual resolution, like we have in git etc.
With the Replicache/Reflect model, you could actually handle both approaches. Might not be easy but the model can support it.
The local-first/realtime space is getting busy these days. Replicache/Reflect is well worth checking out for the beautifully simple data model / coding model. I'm very happy with it.
One plus point compared to CRDTs is that you get to decide how you want to deal with conflicts yourself, with simple, sequential code. I'm not up to date with the latest in CRDT-land but I believe it can be complicated to add application specific conflict resolution if the built-in rules don't fit your needs.
I am well aware that others are having a different experience with it.
No, I meant apps that don't use deep learning, LLMs etc internally.
https://www.realclearscience.com/quick_and_clear_science/201...
Genuine question.