Question

What are the benefits of writing one article per day?

Answer

The main benefit I get from writing at least one article per day is that it forces me to spend time to think about a single question and to write down and express my thoughts clearly.

It allows me to practice my writing abilities, even though I use them daily to write down notes. It forces me to ask myself whether my grammar is correct and whether what I wrote makes sense, which is something I care a lot less about when I write down notes.

It lets me get into the habit of writing daily, so that writing and communicating doesn't feel like it requires a lot of energy.

I see writing one article per day as a habit to acquire in order to be able to write more effectively and communicate better. It is like exercising regularly. The purpose is to keep the muscle of writing alive and strengthening it slowly over time. By writing a lot we slowly acquire a voice that we can work to change and improve. Just like processes that are made explicit can be improved, so can communication be improved by spending time to write down what you want to share with others.

Question

What are the benefits of reading one Wikipedia article per day?

Answer

From my experience so far with reading one Wikipedia article per day, I've enjoyed learning about topics I had not looked into for a long time.

I find biology, and more specifically genetics, highly interesting from a programmer's perspective because I see DNA as code and it makes me wonder how Nature developed this code.

I also find astronomy and everything related with space (space travel, planets, organization of space) also deeply interesting because I rarely spend any time thinking about it, yet I used to watch a lot of TV shows on parallel universes, string theory, etc. which I found fascinating.

I've spent some time reading on statistics as well since it is a tool I use daily at work and I think it is important that I master it as much as possible. Wikipedia allows me to explore and discover new topics that are related to statistics, something which might be a lot more difficult to do by simply reading books.

I think that as long as you add variety in what you read, Wikipedia will provide you with a lot of information and additional references that might be interesting to investigate.

Question

Why do I track how much time I read and how many pages I've read?

Answer

It allows me to have an idea of how long a book will take me to read. It also allows me to determine over time if I'm getting slower or faster reading books by using a website like How Long to Read. While the website says that reading a book such as Liu Cixin's Death's End should take 10h to read to the average reader at 300 WPM, it took me more than 20h to read it, which means I'm a very slow reader and that I read at less than 150 WPM.

The benefit of knowing how long a book will take me to read is that I can decide if I want to actually spend that time finishing the book or not. When a book is good, this question is not considered, but when it is bad, it is important to decide whether spending more time is a worthwhile use of my time.

Question

How do I write my questions and problems articles?

Answer

The process I use to write both my questions articles and my problems articles is quite similar, so I will summarize both in this article.

The process is as follows:

• Find the question or problem to cover.
  • To find questions, I will look at the notes I have taken in the past and search for question marks. I answer those questions as a way to stimulate my brain to think about questions I may rarely have the time to answer.
  • To find problems, I will look at my GitHub repositories. When I encounter a problem at work, I try to write it down so I can describe the issue in more details, which may hopefully help someone in a similar situation in the future.
• Think about the question or problem for a little while, to see what I can come up with.
• Write a list of items that I want to cover, this acts as my plan.
• Describe the items in the list in more details.
• Reference articles I've already written on the same topic.
• Review the article using Grammarly for grammatical mistakes and typos.

Question

How would you lead an AGI company with 100,000 employees?

Answer

I would separate the employees into multiple smaller companies, as large companies are difficult to wield. Furthermore, I think that it is useful for different companies to work on the same problem using different approaches, which is something I would promote. I see the need for a variety of positions:

• (30%) Tooling and core technologies: Building tools that are used by other employees to make progress (visualization, compilation, hardware, database, network). (Bachelor/Master/PhD)
• (25%) Applied research: Put the results of fundamental research into application in a variety of products. (Master/PhD)
• (15%) Fundamental research: Work on scientific theories in order to improve our understanding of intelligence, learning, doing science, solving problems, programming, etc. (Master/PhD)
• (15%) IT: Deal with infrastructure management and scaling. (Bachelor/Master/PhD)
• (5%) Management: Ensuring that work is going in a specific direction and is not a random walk. (Bachelor/Master/PhD)
• (5%) Data collector: Acquire data necessary for experiments done by fundamental researchers and applied research scientists. (Bachelor)
• (5%) Administrative/HR/Facility management: Deal with business related tasks such as people management, facility management/maintenance, etc. (Bachelor)

Reference

• https://www.reddit.com/r/agi/comments/aa18gn/thought_experiment_how_would_you_lead_an_agi/