Follow
Yesterday I listened to the first episode of the "Change, Technically" #podcast by @grimalkina and @analog_ashley and (unsurprisingly) really liked it. I think it had a lot of interesting things to say about how we think about who can code or do science as illustrated in part by their own paths into these fields. If you're interested in #STEM, #coding, #softwareEngineering, etc. I think it's well worth a listen.
To say a bit more about why this podcast is interesting:
Software engineers talk a lot about processes that will produce better code, more productivity, less frustration for coders, etc., but the problem is that these are not questions of computer science, they're questions of social and behavioral science! Software engineers and computer scientists are ill-equipped to study these questions effectively. But @grimalkina is a psychologist who specializes in studying issues like these in software teams and has the right knowledge of methodology and statistics to actually do it!
Coders also talk a lot about getting new people into coding. I don't know too much about @analog_ashley yet, but I gather they're a neuroscientist who works a lot with code and hardware and teaches coding in the context of biological scientists. So this is a non-CS person teaching coding to other non-CS people in a very different context than your usual coding bootcamp; I expect this to lead to a lot of insights that I wouldn't get elsewhere.