robotelvis
Joined 5 years ago
Joined 5 years ago
My 11 year old son seemed to get it all, so I think it should be pretty approachable, but I'm sure there is stuff I can improve.
The trick is to find ways to carry it with you less.
But I have buried it on the third page of a sub-folder, so I'm not tempted to randomly open it.
I think the most important thing is to just not /usually/ have the phone in your pocket, so you break the habit of reaching for it.
There are definitely lots of things you need a smartphone for today, but fortunately few enough that it's practical to not have a smartphone with you most of the time, even if you own one.
Hopefully if enough people go phoneless, society will adapt to require smartphones less often.
We are working with a consortium of public broadcasters around the world to create a publicly-owned public-interest online space that helps people with different viewpoints understand each other and relate to each other. This project has a lot of momentum behind it, particularly as recent political changes in the US are getting countries interested in the idea of digital sovereignty.
Our partners have a combined regular audience that collectively includes a substantial fraction of the western world, so if we get the product to a good enough state that they can promote it aggressively, it has the potential to be one of the biggest and most important platforms in the world.
The New Public dev team currently consists of me, Rob Ennals (ex Google, Meta, Quora), Blaine Cook (created Twitter), and Daniel Bachhuber (ran Wordpress.com), so it's a fun team to be on. We also have very strong experienced Designers and PMs.
Particularly interested in people with experience working on social products, experience being a core developer of a large product with lots of external contributors, or a deep interest in helping people with different viewpoints relate to each other.
Codex works best when you have a really clean code base, with thorough tests, and well documented best practices. Getting your code base into that kind of shape might seem like a lot of work, but Codex is already great at the kind of mundane tasks needed to get your code into a state where Codex can work well.
Codex has also changed how I think about software engineering. With previous AI tools, I used them to help me write the code, but now my job is to mentor a team of AI agents as they write the code.
Even if you don't write code, it's important to understand what it's like to use Codex, because this kind of "manage a team of AI agents to do your job" is likely the future of all human work.
This was on hacker news a while back, but it now has 4 new chapters - taking the reader from next token prediction to a real AI agent with post-training, conversations, reasoning, and tool use.