Saved (Public Feed)

Neuroscientists find that interpreting code activates a general-purpose brain network, but not language-processing centers --- The findings suggest there isn't a definitive answer to whether coding should be taught as a math-based skill or a language-based skill. In part, that's because learning to program may draw on both language and multiple demand systems, even if -- once learned -- programming doesn't rely on the language regions, the researchers say. […] While the programmers lay in a functional magnetic resonance (fMRI) scanner, the researchers showed them snippets of code and asked them to predict what action the code would produce. The researchers saw little to no response to code in the language regions of the brain. Instead, they found that the coding task mainly activated the so-called multiple demand network. This network, whose activity is spread throughout the frontal and parietal lobes of the brain, is typically recruited for tasks that require holding many pieces of information in mind at once, and is responsible for our ability to perform a wide variety of mental tasks.

Viewed from one angle, the rise of get-girls-to-code initiatives is progressive and feminist. Many people involved in the movement are certainly progressive feminists themselves, and many women have benefited from these initiatives. But there are other ways to look at it too. Women are generally cheaper, to other workers’ dismay. “Introducing women into a discipline can be seen as empowerment for women,” says Ensmenger. “But it is often seen by men as a reduction of their status. Because, historically speaking, the more women in a profession, the lower-paid it is.” Hicks, the computing historian, can’t stand it when people tout coding camps as a solution to technology’s gender problem. “I think these initiatives are well-meaning, but they totally misunderstand the problem. The pipeline is not the problem; the meritocracy is the problem. The idea that we’ll just stuff people into the pipeline assumes a meritocracy that does not exist.” Ironically, says Hicks, these coding initiatives are, consciously or not, betting on their graduates’ failure. If boot camp graduates succeed, they’ll flood the market, devaluing the entire profession. “If you can be the exception who becomes successful, then you can take advantage of all the gatekeeping mechanisms,” says Hicks. “But if you aren’t the exception, and the gatekeeping starts to fall away, then the profession becomes less prestigious.”

The computers we have today are not bicycles. Instead we’ve got something more like a car for the mind. Which, you know, does get you around and is easier and more comfortable than a bike. But at what cost? When we decided that America would be a place for cars, we signed ourselves up for urban sprawl, air pollution, car crashes, and oil wars. And even on a human scale, cars are as much liabilities as they are assets — I’m sure we’ve all known people working terrible jobs to keep their junker running so they can get to their terrible job.

The experimental pioneer's groundbreaking work with computers in the 70s and 80s helped lay the foundation for many of today's electronic noise makers.

It’s true, there’s not necessarily a business case to do this, but that is not the only thing Apple will be judged on in the decades to come. And that’s what I’m talking about here: how will future generations look back at Apple, and by extension its customers? Did we all live our lives by more than just the bottom line? Or were the late twentieth and early twenty-first century the decades in which we irrevocably decided that everything should be disposable (or even recyclable) after just two or three years?

Mixed into a story about the author trying to learn to program.

This guy seems to have some family issues that his addiction to incoming data via screens is severely aggravating. I experience, on a smaller scale, some of the problems outlined in this article, and, though none of this is particularly new to me, it's frightening to see these habits taken down the slippery slope. Should all of us, and especially people like Kord, make a concerted effort to make screens less a part of our lives, lest we lose our humanity? Or is trying to avoid technology's increasing integration with our every second just being traditionally biased and counter-progressive? I think there is a middle ground where one can be hooked in and focused on doing work while still not ignoring ones' children. Food for thought.

"what software developers do best is learn. Employers should be loooking for passionate, driven, flexible self-educators who have a proven ability to code in whatever language -- and serving them up interesting projects they can engage with."

"Steve Jobs gives a legendary keynote at Macworld SF every January, launching products and giving a state of the union view of things at Apple. What if you invested $10,000 the day before the keynote, then sold at the end of the keynote day?"

"My research interests include electronic textiles and wearable computing, tangible interfaces, education, and human computer interaction. I am also interested in art and design, particularly in interactive sculpture."