Skip to main content

A Comment on The NY Time's A Surge in Learning the Language of the Internet

My father worked with computers in the military during the Korean War in the 50's and with corporations in the 60's. He died prematurely, but his brother saw the industry growth and got involved, programming for major corporations through the 70's and 80's. For much of my young adult life I heard "go into computers, it's the wave of the future." I find it amusing, in that it still is. The 'nerds' are a bit less nerdy, but still considered odd and of lower status than other professions.

As for myself, I avoided the 'wave of the future' for quite some time, but with half a CS degree, finishing a BA in Psych and half an MBA, I work as a software developer. Other than the basics I learned in 80's college, i.e., BASIC, PL/I, COBOL, loops, etc., most of my knowledge is self-taught, with books covering algorithms, patterns, data, databases, and software architecture.

Original article:

A Surge in Learning Language on the Internet

Comments

Popular posts from this blog

Behave: The Biology of Humans at Our Best and Worst by Robert M. Sapolsky My rating: 5 of 5 stars I finished reading this crying. It is a work of neurobiology, social science, anthropology, and history, but ultimately it is a work of great humanity, suggesting ways that humans, our groups, our systems, and our societies can be made better. View all my reviews

A Journey — if You Dare — Into the Minds of Silicon Valley Programmers

My responses in a NY Times comment section for the book, Coders: The Making of a New Tribe and the Remaking of the World by Clive Thompson : #1 - Link Although I've been a software developer for 15 years, and for longer alternating between a project manager, team lead, or analyst, mostly in finance, and now with a cancer center, I found it funny that you blame the people doing the coding for not seeing the harm it could cause. First, most scientific advancement has dark elements, and it is usually not the science but how it is used and sold by business people that is the problem. This leads to the second problem, in that it is not coding that is in itself problematic, but specifically how technology is harnessed to sell. It is normal and desirable to track users, to log actions, to collect telemetry, so as to monitor systems, respond to errors, and to develop new features, but that normal engineering practice has been used to surveil users for the purpose of selling. Blaming

Don't learn to code. Learn to think.

A response to  Don't learn to code. Learn to think. : Below is is my usual response when I see an article stating that everyone should learn to code:  Rather than programming, it is more important to impart the thinking of computer science (CS) than a specific implementation. Programming can be an end point for some students, but it is likely that programming itself will be increasingly automated, so that one needs more the general concepts common in CS. Even then, programming itself is to some degree a grunt task that one progresses beyond:  The following are typical components of a CS degree: algorithms & flowcharting systems thinking logical systems and set theory object-orientation & patterns probability, statistics, mathematics All of the above can be useful in an increasingly automated and data-driven world.