The undocumented instructions in the 8085 were described in detail in Dr Dobb's Journal shortly after announcement of the 8085 (with no mention of the "new" instructions).
The 6600 was not a superscalar machine but simply a pipelined processor. Superscalar machines first appeared in the floating point processor of the IBM 360/91 and may well be due to John Cocke (IBM) who generalized the notion. Yale Patt (UC Berkeley, U Michigan, U Texas at Austin) refined the ideas. Most processors designed today have superscalar features.
The People's Computer Company published many BASIC games in its publications (PCC Newspaper, People's Computers, Dr. Dobbs Journal, Recreational Computing) and in the book, What to Do After You Hit Return: Or, P.C.C.'s First Book of Computer Games. Many of the games were reprinted elsewhere, often without attribution.
I worked on the MUMPS Standard when I taught in the Medical Informatics Committee at UC San Francisco. When I first encountered the language, I was appalled. For example, in pre-standard MUMPS, lines with no trailing blanks and lines with one trailing blank had a different interpretation. For those interested, https://nvlpubs.nist.gov/nistpubs/Legacy/hb/nbshandbook118.p.... At one of the standardization meetings, I embarrassed myself by called MUMPS a "viral disease" because of the pathology of the programming language as defined to an audience of people who saw it as a practical tool they used every day. The standard helped stabilize the language. I acquired an appreciation for the incredible skill application programmers can adapt a general purpose extensible language to do their bidding.
Wait. We are exploring boundaries and understanding and not necessarily maintaining the present system. Money? Lend? Ownership? Business? Protecting money? Payments? Privilege? Banking? These are all up for rethinking.
Why do we even need banks? What does the financial industry provide? If we were to restructure everything, what would make sense? What are the invariant properties of a viable financial system?
Everyone should read this summary/review of the "debate".
More important, everyone should read the paper being debated: Social Processes and Proofs of Theorems and Programs, Richard A. De Millo (Georgia Institute of Technology) and Richard J. Lipton and Alan J. Perlis
(Yale University). This is one of my favorite CS papers because it exposes a lot of the mechanism behind making proofs that are convincing. What does it mean to say you have proven something.
Eric Mitchell will discuss the problem of detecting machine-generated text followed by an open forum Q&A.
Part of EE380, Stanford EE Computer Systems Forum.
Don't believe this article. If adding automation and robots to the mix does not decrease cost, it is not going to happen. Labor is the only free variable.
It is a real loss, Gumby. Carl and I were friends and spent hours on the telephone solving the problems of the world and playing polymath math. Hardly a day would go by without an hour or so chat with Carl.
Most of what passes for crypto isn't. The hard problem is not providing an encrypted channel, it's doing the rest, particularly key exchange. When you can construct an encrypted channel, then you need to look at maintaining the end points secure and ensuring the local data is appropriately secured and encrypted. Then, .... Crypto provides a few tools, but secure systems require careful design, analysis, and knowledge and a fascile command of some arcane mathematics.
It is unlikely that there is a way to avoid obsession and addiction Supply an ipad with a reliable high bandwidth "works anywhere" network connection, lots of memory, lots of processor performance, and Minecraft. Sign her/him up for home schooling. Stockpile food and drink that can be consumed while working on Minecraft. Setup sleeping bag and mattress near the Minecraft site.
Cut a deal with the child that they will check-in once a week and set them free.
The 1979 HP APL\3000 compiler was pretty cool. As I remember, the project was led by John Walters who led the IBM 360 assembler development and was unique in how it managed data references.
An earlier compiler/interpreter in the same vein was written in 1971 for the Burroughs B6700 by Jim Ryan and described in the 3rd APL Conference.
No, I do not believe engineer founders have problems getting hired. They are "experienced" and "know the ropes". Startups rarely fail because of a boffo in engineering.
I second this choice. Be sure to get the second edition and to read the various fascicles for Knuth's Volume 4 of Art of Computer Programming. Volume 2 has some useful content as well.
If you become one of the best programmers in the world, what will you have achieved? What is there about programming that captures your passion? Will that be sustainable for the brief moment you are alive. What do you want as a legacy after 80 years of work?
One example: The Hacker's Conference ["Hackers"]. It is populated by a diverse group of people, . Attendees program, but I doubt that anyone of the attendees would call themselves a programmer except in jest.
Hackers do what they do. Some are mathematicians, some are musicians. At least one plays the organ. Others are into sex, drugs, and rock and roll. Some are spiritual, some agnostic. Some climb mountains. Others worry about how to planet-form the earth to recover from an over-abundance of CO2. Some have families and kids, some do not. Everyone is interested in everything. Hackers know things, observe, and learn things. They delight in sharing knowledge, particularly arcane knowledge. They are compassionate, ethical, and loving (although there are occasional exceptions).
If you are good at programming you are likely to be good at living an exploratory life. Be fearless and brash. Always wonder why and learn how.