| #[derive(Clone, Debug)] | |
| pub struct GroupedKey<K: Clone> { | |
| group_key: K, | |
| item_key: usize, | |
| } | |
| impl<K> GroupedKey<K> { | |
| fn new(group_key: K, item_key: usize) -> Self { | |
| Self { | |
| group_key, |
| // = hello world in 6502 assembly with memory mapped linux syscalls | |
| // :author: wallabra | |
| // :email: gr.wallabra@proton.me | |
| // | |
| // literate 6502 assembly with asciidoc comments | |
| // | |
| // * uses Linux syscalls | |
| // | |
| // addresses exposed by 6502 VM:: |
You have a project? Cool! Do you know what you want to do next? Then don't put your hands on the keyboard yet!
Or maybe you're already halfway through one, only to realize you got lost in a big forest of what-ifs and unknowns and what-abouts and now it's gonna be a hell of a journey just to climb your way back on track.
Here's how you break down a project into tasks organically, while still affording to change directions when necessary.
by Gustavo Rehermann (wallabra) - contact: gr.wallabra@proton.me
I'm happy that we are starting to see AI safety initiatives. I understand their problem statement. But I think they are very myopic when it comes to the extent of what it means to have AI widespread in society, not just misaligned AI, but any AI.
How about we start making AI do the parts of life we actually don't want to deal with, while we get to keep the enjoyable parts like art, writing, and trust in a meaningful and real reality, for ourselves? Or rather, how about we use it once we know it can do these things, and do them sustainably?
And, ultimately, what if the problems rightfully attributed to AI actually go much, much deeper than just the AI itself? Let's dive in.