# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 12
# self = https://watcher.sour.is/conv/4fkqpga
I've also found that, at least here, Computer Science or (Management of) Information Tecnologies are not related to creating or architecturing software, but on understanding and maintaining current ones.

Which is not that bad, you cannot create something if you don't know previous solutions or implementations... 🤔
Again, there is simply not enough time in 3-5 years of intense education to learn to 'program'
@eaplmx I'm reminded of that saying that goes something like:

> In order to be an expert at something, you have to spend at least 10,000 hours on it

Or something like that 😅
@eaplmx I'm reminded of that saying that goes something like:

> In order to be an expert at something, you have to spend at least 10,000 hours on it

Or something like that 😅
@eaplmx I'm reminded of that saying that goes something like:

> In order to be an expert at something, you have to spend at least 10,000 hours on it

Or something like that 😅
@eaplmx I'm reminded of that saying that goes something like:

> In order to be an expert at something, you have to spend at least 10,000 hours on it

Or something like that 😅
@prologic my wife and I wrote a paper together about a class we designed, and some of the background research I did for that turned up strong evidence that really "getting" a programming language takes about as much time as it takes to become fluent in a natural language: about 730 hours of practice for a language similar to your native one, closer to 1,200 for a language that's quite different from your native one. I imagine with programming languages it's faster to pick up another one in the same "family" as one you're already used to, but if you're jumping paradigms (e.g., learning Haskell after a lifetime of imperative programming) it'll take longer.

Expertise requires quite a bit more time!
@abucci sounds like a really interesting research! By any chance is that paper publicly available?

Not wanting to criticize anything on your paper or your numbers, and based on a book I'm reading, Factfulness, I'd like to know an average and also the standard deviation or a distribution graph on _time to learn to program from scratch_. Usually the average hides the diversity on the sample.
@prologic hehe, yeah!

There are a lot of books on the subject such as https://www.goodreads.com/book/show/4983932-10-000-hours

Now I think 10,000 is saying something like "more time that you'd expect of intended practice, multiplied by talent"

An interesting discussion I heard in a podcast, was that the expertise level grows _"logarithmically"_ (I think that's the right word). Learning from 0 to, let's say, 50% takes a year. 50-75% another year, and so. The last 95-99% takes decades of intense and purposeful practice.
@eaplmx Sure! You should be able to download the paper from ResearchGate. If that doesn't work let me know and I can get it to you some other way. Note that the link is to a workshop proceedings so you'll have to flip through that to find our paper (the other papers are interesting too!)

Reading over it again, I'm realizing that my memory of what we included is pretty skewed, oops 😕 We did survey some CS education literature to get a sense for how long it took to learn to program according to educators, but it looks like we left out that survey (for lack of space I think? but also because of the audience). The guesstimate about how long it takes to learn a natural language is sourced from the US Department of State. I'll have to dig through my notes to find where I got the corresponding guesstimate about learning to program.

I totally agree with you about diversity being a very important factor. I definitely have not paid this due attention in the writings I've done about CS education. Two links that might be of interest to you that I stumbled on recently:

- A blog post suggesting there's really no such thing as "learning to code". People learn how to program in a specific domain, and a good fraction of what they learn is not transfearbale to another domain. So learning programming is a much more nuanced pursuit
- Amy J. Ko, a CS education researcher at the University of Washington in the US whose interests and work includes the relationship between diversity issues and computing.

Wish I had a better answer for you!
@eaplmx Sure! You should be able to download the paper from ResearchGate. If that doesn't work let me know and I can get it to you some other way. Note that the link is to a workshop proceedings so you'll have to flip through that to find our paper (the other papers are interesting too!)

Reading over it again, I'm realizing that my memory of what we included is pretty skewed, oops 😕 We did survey some CS education literature to get a sense for how long it took to learn to program according to educators, but it looks like we left out that survey (for lack of space I think? but also because of the audience). The guesstimate about how long it takes to learn a natural language is sourced from the US Department of State. I'll have to dig through my notes to find where I got the corresponding guesstimate about learning to program.

I totally agree with you about diversity being a very important factor. I definitely have not paid this due attention in the writings I've done about CS education. Two links that might be of interest to you that I stumbled on recently:

- A blog post suggesting there's really no such thing as "learning to code". People learn how to program in a specific domain, and a good fraction of what they learn is not transferable to another domain (the blog posts goes a bit into why that might be). So learning programming is a much more nuanced pursuit
- Amy J. Ko, a CS education researcher at the University of Washington in the US whose interests and work includes the relationship between diversity issues and computing.

Wish I had a better answer for you!
@abucci amazing links! 😀

And I got the paper, thanks for sharing! It's about 200 pages. Wow, that's a lot of knowledge.
@eaplmx oh good. The paper my wife and I wrote is only one of many in that book. I found the conference interesting and maybe some of the other articles will catch your attention too.

I hope the other links are helpful!