Wednesday, October 21, 2015

The Heart of "Rudy"

There are many films that teach us about succeeding against all odds.  "Rudy" was one of them.

Friday, September 25, 2015

Up, up, and away!

A company in California produces an amphibious aircraft that people can learn to fly in about 20 hours, it claims.

It looks enticing.

Monday, August 24, 2015

25 Steve Jobs Quotes That Will Help You

25 Steve Jobs Quotes That Will Change the Way You Work—in the Best Way Possible By Kaitlyn Russell

Reposted from The Muse.

Fact: Steve Jobs didn’t become successful overnight.
It took years of hard work, determination, and perseverance to build Apple into the company that it is today. When you take a step back from your MacBook (and put down your iPhone), and really think about all that he accomplished, it’s beyond remarkable. He changed the way we live. 
Thanks to his many lectures and speeches, we have a glimpse into his day-to-day work ethic and how he managed to do as much as he did. And, in order to help you reach your career goals, we’ve rounded up 25 of his best quotes. Read them, be inspired by them, and then get out there and make your dreams come true. 
  • My favorite things in life don’t cost any money. It’s really clear that the most precious resource we all have is time.
  • I’m as proud of many of the things we haven’t done as the things we have done. Innovation is saying no to a thousand things.
  • Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven’t found it yet, keep looking. Don’t settle. As with all matters of the heart, you’ll know when you find it.
  • Have the courage to follow your heart and intuition. They somehow know what you truly want to become.
  • I think if you do something and it turns out pretty good, then you should go do something else wonderful, not dwell on it for too long. Just figure out what’s next.
  • Sometimes when you innovate, you make mistakes. It is best to admit them quickly, and get on with improving your other innovations.
  • When you’re a carpenter making a beautiful chest of drawers, you’re not going to use a piece of plywood on the back, even though it faces the wall and nobody will see it. You’ll know it’s there, so you’re going to use a beautiful piece of wood on the back. For you to sleep well at night, the aesthetic, the quality, has to be carried all the way through.
  • That’s been one of my mantras—focus and simplicity. Simple can be harder than complex; you have to work hard to get your thinking clean to make it simple.
  • Quality is more important than quantity. One home run is much better than two doubles.
  • Being the richest man in the cemetery doesn’t matter to me. Going to bed at night saying we’ve done something wonderful...that’s what matters to me.
  • The people who are crazy enough to think they can change the world are the ones who do.
  • Your time is limited, so don’t waste it living someone else’s life. Don’t be trapped by dogma—which is living with the results of other people’s thinking. Don’t let the noise of others’ opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition.
  • We’re just enthusiastic about what we do.
  • You can’t connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something—your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.
  • Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.
  • For the past 33 years, I have looked in the mirror every morning and asked myself: ‘If today were the last day of my life, would I want to do what I am about to do today?’ And whenever the answer has been ‘No’ for too many days in a row, I know I need to change something.
  • I'm convinced that about half of what separates successful entrepreneurs from the non-successful ones is pure perseverance.
  • What is Apple, after all? Apple is about people who think ‘outside the box,’ people who want to use computers to help them change the world, to help them create things that make a difference, and not just to get a job done.
  • Things don’t have to change the world to be important.
  • Technology is nothing. What’s important is that you have a faith in people, that they’re basically good and smart, and if you give them tools, they’ll do wonderful things with them.
  • I’ve always been attracted to the more revolutionary changes. I don’t know why. Because they’re harder. They’re much more stressful emotionally. And you usually go through a period where everybody tells you that you’ve completely failed.
  • Bottom line is, I didn’t return to Apple to make a fortune. I’ve been very lucky in my life and already have one. When I was 25, my net worth was $100 million or so. I decided then that I wasn’t going to let it ruin my life. There’s no way you could ever spend it all, and I don’t view wealth as something that validates my intelligence.
  • My model for business is The Beatles: They were four guys that kept each others’ negative tendencies in check; they balanced each other. And the total was greater than the sum of the parts.
  • Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.
  • Getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again. It freed me to enter one of the most creative periods of my life.

Saturday, August 15, 2015

Monday, May 11, 2015

The Problem in California is a Shortage of Economic Understanding, Not Water

By Walter E. Williams

Californians are experiencing their third year of drought. Headlines read: "Current California Drought Is Driest In State's History; Scientists Fear 'Megadroughts' On Their Way." "Global Warming Upped Heat Driving California's Drought." Then there are scientific claims such as, "There's a rapidly growing body of scientific research finding that California is in the midst of its worst drought in over a millennium (and) global warming has made the drought worse." A Stanford University study said, "Human-caused climate change helped fuel the current California drought." One news outlet summarized the conclusions of a group of environmentalists this way: "California's severe and ongoing drought is just a taste of the dry years to come, thanks to global warming."

Let's examine a few drought facts.

California experienced eight major droughts in the 20th century, according to the U.S. Geological Survey. They ranged from two years to as long as nine years, such as that which occurred from 1928 to 1937. In the previous century, there was the bitter drought of 1862-65, which was a catastrophe for the state of California — made worse by a smallpox epidemic. Scott Stine — professor of geography and environmental studies at California State University, East Bay — said that all of these modern droughts were minor compared with California's ancient droughts of 850 to 1090 and 1140 to 1320. One wonders whether California Gov. Jerry Brown and his cadre of environmental extremists would attribute those ancient droughts to man-made global warming.

A large part of California's water problem has economic roots. Whenever there's a shortage of anything — whether it's water or seats at a baseball stadium — our first suspicion should be that the price is too low. California agriculture consumes about 80 percent of the state's delivered water, and it has been exempted from many of California's new restrictions. On top of that, agricultural water users pay a much lower price than residential users. In other words, California's farmers are being heavily subsidized.

The Imperial Valley, located in the southeastern part of the state, is geologically a desert. Nonetheless, its farmers grow large quantities of potatoes, cauliflower, sweet corn, broccoli and onions. These crops would not be produced without there being subsidized irrigation and other state and federal subsidies. I need someone to show me that there is such a desperate need for somewhere to grow potatoes, corn and other crops that we need to subsidize making a desert bloom.

Western water is mostly controlled by the U.S. Congress and its Bureau of Reclamation. Through lobbying efforts, the Bureau of Reclamation is controlled by growers and other special interests. Water is distributed in California and other Western states not by market prices but by the political process. Agricultural interests have disproportionate political power. That means that agricultural interests receive taxpayer-financed handouts.

California farmers argue that without federal and state government subsidies, crops could not be grown in desert areas. That's a foolish, self-serving argument. If I were an Alaskan wanting to use government subsidies to build hothouses to grow navel oranges, I could use the same argument: Without government subsidies, I couldn't grow navel oranges in Alaska.

Some of California's water conservation regulations are mindless. It is illegal for servers in bars, restaurants and cafeterias to serve water unless customers ask. The amount of water that people drink per day is a trivial part of total water consumption. Estimates vary, but each person consumes 80 to 100 gallons of water per day flushing toilets, bathing and for other residential purposes.

Another California water conservation effort is "drought shaming." That's when vigilantes call water utility hotlines to snitch on their neighbors who are watering lawns, washing cars or filling pools. One wonders whether there might arise an anti-vigilante movement to punish the vigilantes.

The bottom line for solving California's water problem is that there needs to be a move toward a market-oriented method for the distribution of water. Government management has been a failure.

Walter E. Williams is a professor of economics at George Mason University and author of Race & Economics: How Much Can Be Blamed on Discrimination?

Thursday, May 7, 2015

The Power Brothers by Max McNabb

Old man Power didn’t want his sons to be cannon fodder in the First World War. Jeff Power told his boys, John and Tom, not to register for the draft. The rich man’s war had nothing to do with them. In 1918, the Power family, originally from West Texas, had a gold mine to work in Arizona’s Gila Valley.

“They reacted the way Texans would react,” historian Jeff Robenalt says in the documentary Power’s War. “They didn’t cause the war… they didn’t make the draft. Why should they register for it?”

The young brothers planned to remain in the Galiuro Mountains until the war ended, then everything would blow over. But the US government had other plans. On February 9, 1918, Deputy US Marshal Haynes, Sheriff McBride, and Deputy Kempton met with volunteer Deputy Kane Wootan. The lawmen rode up into the mountains to arrest John and Tom Power for failing to register for the selective draft.

All four of the lawmen were members of the Mormon Church. Writer Roderick Roberts notes the Gila Valley was heavily Mormon and the Power family’s status as non-Mormon newcomers caused some of their neighbors to view them with hostility. The Powers claimed the Wootans wanted their gold mine and were willing to use the WWI conscription to take it. Sheriff McBride served as chairman of the county draft board. If John and Tom were drafted, their father couldn’t work the mine alone and would have to sell.

Just before dawn, the sound of startled horses woke Jeff Power in the family cabin. He stepped to the door and opened it. A voice in the darkness shouted, “Throw up your hands!”

Jeff Power raised his hands. Three shots cracked and the old man fell, shot down in his own doorway.

The gunfight that followed was the deadliest in Arizona history. The posse fired into the cabin. John and Tom Power grabbed Winchesters and fought back. The family’s hired hand, an ex-Army scout named Tom Sisson, took cover. When the smoke cleared, Jeff Power and three lawmen were dead, a fourth escaped, and the Power brothers had suffered wounded eyes from flying splinters and glass. The attackers never identified themselves as lawmen. Only after standing over the bodies did the Powers realize the dead men wore badges.

Read the rest at Max McNabb's website.

Sunday, March 15, 2015

Water Rationing: The Bureaucrat's Solution

A crisis is a terrible thing to waste if you're a statist.  So, the drought in California presents a great opportunity for more bureaucracy, corruption, and waste.  It also presents an opportunity for the free market pricing system, but that of course is not on the table.

Water Rationing: The Bureaucrat's Solution

Oil Industry Bailout

The government plans to buy oil to drive up its price.  Capitalism serves the consumer.  The consumer is not being served, oil companies are.

Oil Industry Bailout

Tuesday, March 10, 2015

How central banking works

The Mises Institute has a link to a site where you can find an out-of-print booklet called Modern Money Mechanics: A Workbook on Bank Reserves and Deposit Expansion, published originally by the federal reserve bank of Chicago.  For those interested in how the current monetary system works, it is not completely unreadable and is consistent with my understanding, though it refers occasionally to M3, an outdated money supply measure.  Here is an excerpt:

Let us assume that expansion in the money stock is desired by the Federal Reserve to achieve its policy objectives. One way the central bank can initiate such an expansion is through purchases of securities in the open market. Payment for the securities adds to bank reserves. Such purchases (and sales) are called "open market operations."

How do open market purchases add to bank reserves and deposits? Suppose the Federal Reserve System, through its trading desk at the Federal Reserve Bank of New York, buys $10,000 of Treasury bills from a dealer in U. S. government securities.(3)  In today's world of computerized financial transactions, the Federal Reserve Bank pays for the securities with an "telectronic" check drawn on itself.(4) Via its "Fedwire" transfer network, the Federal Reserve notifies the dealer's designated bank (Bank A) that payment for the securities should be credited to (deposited in) the dealer's account at Bank A. At the same time, Bank A's reserve account at the Federal Reserve is credited for the amount of the securities purchase. The Federal Reserve System has added $10,000 of securities to its assets, which it has paid for, in effect, by creating a liability on itself in the form of bank reserve balances. These reserves on Bank A's books are matched by $10,000 of the dealer's deposits that did not exist before.

If the prose in the above gets too thick to be digested, try Murray Rothbard's The Mystery of Banking (PDF), especially Chapter XI.  CENTRAL BANKING: THE PROCESS OF BANK CREDIT EXPANSION, beginning on page 161.

Rothbard also explains in detail (pp. 47-55) the counterfeiting process, beginning with a monetary system based on gold coin and extended to one based on irredeemable paper money.  

Oddly enough, the FRB of Chicago doesn't mention counterfeiting in its explanation.

Sunday, March 8, 2015

Snowden is not the story

John Naughton at The Guardian writes:

His was not some opportunistic smash-and-grab data heist, but a considered, informed selection of cases where he thought that the National Security Agency was violating the US constitution and/or circumventing its laws. Snowden was clearly no stereotypical left-wing dissident; he seemed closer to what US constitutional lawyers called an “originalist” – someone who regards the constitution as a sacred, inviolable document that citizens – and their governments – must continue to respect and adhere to. If Snowden were in the US today, I suspect he would be a supporter of Rand Paul.


The U.S. government responded to Snowden's revelations exactly as a gangster organization would. And a big chunk of the propagandized public went along with their supreme leaders.

Read the full story.

Don’t trust your phone, don’t trust your laptop – this is the reality that Snowden has shown us

Stop the Gas Tax Hike

Here is what I sent my representatives in D.C.  I encourage you to do something similar by going here.

I know you're under a lot of pressure, but consider that any proposed tax increase, no matter how it's labeled or what alleged need it fulfills, is a catalyst for activism -- as you're now witnessing.  Your job is to represent the people in your district.  They don't want a tax increase.  They don't like taxes, period -- it's an American tradition.  Can we agree on that?  A tax, any tax, is an act of theft, and Americans don't like to be robbed.  Government schooling has convinced them that a good citizen must accept some taxation, but they will only tolerate so much.

No amount of political lipstick will make a gas tax hike attractive.  The money people are currently "saving" from low gas prices belongs to them, not government bureaucrats.  A gas tax hike amounts to nothing less than one more armed hold-up.  To repeat: No one likes to be robbed.

Make it clear to your big donors that their money will not replace a large majority of voters.

Monday, March 2, 2015

The programmer who wasn't



Officially, he was not a programmer, though programming the IBM mainframes was all he did.  There was no contract money for hiring a programmer, but there was money to hire something else.  What that else was, he never found out.  But he was hired.

The programming staff that supported the DoD (Department of Defense) Anti-Ballistic Missile development project took orders from the engineers and scientists who analyzed the data.  He was not part of that programming staff.  The individuals on the staff wrote FORTRAN programs mostly from scratch in response to the analysts’ orders.  It worked but it was costly.  There was a time lag between generation of the missile test data and its analysis, due almost entirely to the time it took to write and debug the programs.  

What was needed was a software tool that would allow the analysts to massage the data themselves, without the aid of the FORTRAN programmers. 

A big meeting was held that brought in IT professionals and management from system support, the FORTRAN programming staff, and the data analysis section.  The purpose: could such a tool be developed in a reasonable timeframe at an affordable price?  The answer: No.  It would take programmers — plural — with the ability to write a specialized compiler, and such people were both rare and expensive.  And even if complier writers were available at an affordable price, it would take far too long to create a tool that would serve a broad range of analytical requirements.  

The program they wanted was a program that couldn’t be written.


So the great minds that left the meeting — and a few truly were great — found themselves with no better solution than the one they had been using all along.  The PhD analysts would continue feeding data reduction requirements to the FORTRAN staff and wait for the results.  

Some people were quite unsettled about this and couldn’t leave it alone.  Several weeks later, two managers approached the programmer-who-wasn’t and asked him to think about the possibility of a software tool for non-programmers —  the analysts — that would give them the power of a programmer but without the excruciating delays inherent in developing and debugging a program. 

In other words, could the programmer-who-wasn’t write the program that couldn’t be written?


He thought about it in his noisy cubicle and came up with a design.  He and the two managers plus a crack programmer deeply familiar with the project met for three hours examining his proposal.  He had the right approach but the wrong specifics.  Every part of it was changed, on paper.  And on paper, they now had the specifics they needed.  The only thing missing was the impossible part, the program to make it all work.

The programmer-who-wasn’t went back to his noisy cubicle and thought about how he might implement the specifics into an easy-to-use program that didn’t gobble up expensive computer resources such as execution time and memory.  He had been programming for over four years, much of it spent writing programs for transonic wind tunnel tests.  Writing a program that couldn’t be written was his first major challenge since changing departments.  

After two weeks of working on little else, he reported to one of the managers, his supervisor, that he saw no way to do it, short of writing a compiler, a task he was wholly unqualified to undertake.

The supervisor was at least sympathetic.  How could he not be?  The best brains in the company had not found a solution either. 


One afternoon after the close of business he talked with a friend who was working on his PhD in electrical engineering.  The programmer-who-wasn’t explained the wall he had run into, and his friend offered him encouragement along with two thick textbooks on compiler design to study. 

He thanked him and took the books back to his cubicle which was no longer noisy at this late hour.  He understood only a smattering of what he read, but something about it opened up his thinking.  A compiler was a new approach to programming for him.  A compiler took a series of statements a programmer wrote in a language the programmer understood and translated it into machine executable code.  A compiler was a program that ran in stages, passing its results from one stage to the other, before producing the final product the computer could execute, what smartphone users today call an app.  

But was it not possible for any program to compute in stages, not just compilers?  The answer was obviously yes, provided the programmer knew how to design and use data structures.  A program that did this was usually called an interpreter, not a compiler.  Unlike compilers, interpreters didn’t generate stand-alone executable code.  A program that ran under an interpreter needed the interpreter in memory during execution, which in this case was perfectly acceptable.

He saw an opening he hadn’t seen before.  That apparently no one in the company had seen.  He went for it.


Almost immediately he saw the impossibility of his task.  His work area was almost never quiet.  He needed quiet.  He found it impossible to concentrate.  How was he to write this program that couldn’t be written if the noise around him interrupted his thinking?

An unusual task needed an unusual approach.

He walked cold turkey into the office of the project engineer, a short-bearded man in his early 40s with sparkly blue eyes and a sense of humor.  The engineer listened carefully while the programmer-who-wasn’t spoke.  He said there was too much noise in his office but if he could do his designing and coding at home and come in during the evenings to test his program he could get the job done.  Coming into the data center after hours meant he would be testing his program at reduced computer rates while getting almost immediate turnaround. 

On the face of it, his proposal was outrageous.  It had never been done before, not at this company.  People came to work in the morning, spent the day in their offices, then went home to be with their families.  Your cubicle is too noisy?  Get used to it, pal.  Who are you to get away with something like this?

But the project engineer dearly wanted the job done.  At this point it was not a nice-to-have.  It was essential for getting follow-up work on the DoD contract.  He had a prestigious office with a window, with little or no noise infiltrating its sanctum.  He could sympathize.

It took him little more than two seconds to reach a decision.

Saying nothing, the project engineer raised his hand and waved him godspeed. 

The programmer-who-wasn’t drove home and got to work.


He spent the next three months without a day off doing what he promised, working at home during the day and testing his progress on the mainframe in the evening — sometimes the late evening that carried over into the late morning.  His desk was a corner of a wrap-around counter in the bedroom of a mobile home he shared with his wife.  They had no kids, though this programming project might be considered an attempt to produce an offspring.  It had become a labor of love.

Snow fell frequently during this period.  It made his bedroom work area peaceful because it kept neighbors inside.  And most people were driving home from work when he drove into work in the evening, making traffic a light burden.

Co-workers wondered about him.  What was this special program he was working on?  Was he really working or just goofing off?  Suspicion about his work life grew stronger the more he worked at home.  One morning, just before leaving the office after a 24-hour stint, he fell into conversation with a friend, a research physicist.  He was an older man named Jack.

“People are worried about you.  They think you’d be better off working normal hours,” Jack told him with a faint note of warning in his tone.  

What Jack left unsaid ordinarily would’ve bothered him.  He wasn’t worried.  He knew the hand he was holding.

The day soon arrived when he could show the project engineer the results, and they far exceeded expectations.  The project engineer was blown away.  

He installed the program and trained users at several locations, including a coral island in the remote western Pacific ocean.  He presented a detailed explanation of its design to the five-person committee that judged such matters.  The project engineer was on the committee.  So was the PhD candidate in electrical engineering.  The committee members liked it.  Most analysts loved it, even if it didn’t solve every problem they had.  There was always version 2.0.  They loved it because it allowed them to process their data themselves almost immediately after a mission.  That feature alone made it a godsend.


So how could the programmer-who-wasn’t write the program that couldn’t be written?

Was he smarter than the rest?  Wouldn’t it be logical that he was?  He had solved a problem they couldn’t.  Didn't that prove it?

There was no question who was smarter.  His success did not reflect a superior IQ, and no one thought it did.  So what was the answer?  How was he able to turn out a program the smart guys said couldn’t be written?


To the project engineer the answer was obvious and he announced it thusly: 
He succeeded because he was too dumb to know it couldn’t be done.
To the extent anyone cared, this became the accepted explanation.  It felt right.

He was also too dumb to finish his formal education.  

Lacking a degree, he was paid considerably less than those who had one, even though most of the degree holders thought the program he had written had been only a pipe dream — even though, had he taken the time to finish his degree, the program would have remained only a pipe dream.

The FORTRAN programmers mostly ignored his achievement.  Managers, from supervisors to executives, loved it and praised him for it publicly, to the point of making him feel uneasy.  Lavish praise — but little else.

On the day raises were handed out his increase was token.  Reason given: no degree.  The FORTRAN programmers could take comfort in knowing his salary was well beneath theirs.

His dream of moving to a real house, funded by a real job, had been shattered.

So he picked up the pieces of his broken dream and went home.  


A day later he did what any dumb guy would do: He quit.  The programmer-who-wasn’t, was no more.  He had passed voluntarily from employed hero to unemployed bum.

But the bum had a problem.  He had to earn a living. What could a burned-out programmer do to make a buck?  He had no skills other than programming.

Meanwhile, the project engineer received a big promotion.  Other degreed individuals received generous raises, if not promotions themselves.  

The bum tried different things.  He wrote ad copy for ad agencies.  He wrote a Hollywood screenplay that didn’t sell and a film script about the life-cycle of utility poles that did.  He went back to school and got a meaningless degree.  Money trickled in.

The frustration peaked, and eventually he and his wife split.

Monday, January 19, 2015

Will the future be for elites only?

In April, 2000 Bill Joy, cofounder of Sun Microsystems, wrote a piece for Wired titled Why the future doesn't need us.  If technology trends continue, he said, the mass of humanity will become an endangered species.

In late 1998 Joy had heard Ray Kurzweil speak on technological trends and was frightened by Kurzweil's predictions.  Joy concluded humans would soon be overwhelmed by machine intelligence.
As society and the problems that face it become more and more complex and machines become more and more intelligent, people will let machines make more of their decisions for them, simply because machine-made decisions will bring better results than man-made ones. Eventually a stage may be reached at which the decisions necessary to keep the system running will be so complex that human beings will be incapable of making them intelligently. At that stage the machines will be in effective control. People won't be able to just turn the machines off, because they will be so dependent on them that turning them off would amount to suicide.
As machines continue to take over jobs, the mass of humanity will not need to work, Joy suggests.  Humans will be a "useless burden on the system."  A fiendish elite may decide to exterminate their underlings and rely exclsuively on machines for economic growth.

But there are problems with Joy's argument. If Kurzweil is prescient, and he has been, nanotechnology will make people much smarter (and healthier) than they are today.  Augmented intelligence could save us from tyrants.  Computer aided brains would do a better job of dealing with every kind of problem, including exponentially expanding technology.

In his landmark essay of 2001, Kurzweil explains how this might happen.  First, we will use tiny robots to scan the brain.
By 2030, “nanobot” (i.e., nano robot) technology will be viable and brain scanning will be a prominent application. Nanobots are robots that are the size of human blood cells, or even smaller. Billions of them could travel through every brain capillary and scan every relevant feature from up close. Using high speed wireless communication, the nanobots would communicate with each other, and with other computers that are compiling the brain scan data base (in other words, the nanobots will all be on a wireless local area network).
Nanobots will help scientists understand the functioning of the brain.  Nanobots will also "expand our experiences and our capabilities."
Nanobot technology will provide fully immersive, totally convincing virtual reality in the following way. The nanobots take up positions in close physical proximity to every interneuronal connection coming from all of our senses (e.g., eyes, ears, skin).  We already have the technology for electronic devices to communicate with neurons in both directions that requires no direct physical contact with the neurons.
These "neuron transistors," forerunners of nanobots, can detect the firing of a nearby neuron, cause it to fire, or suppress it from firing.

When nanobots are developed they will provide the link between biological and nonbiological thinking.
Our brains today are relatively fixed in design. Although we do add patterns of interneuronal connections and neurotransmitter concentrations as a normal part of the learning process, the current overall capacity of the human brain is highly constrained, restricted to a mere hundred trillion connections. Brain implants based on massively distributed intelligent nanobots will ultimately expand our memories a trillion fold, and otherwise vastly improve all of our sensory, pattern recognition, and cognitive abilities.  (emphasis added)
How will we get these nanobots into our brains?  The way we take cough syrup.
Nanobots will be introduced without surgery, essentially just by injecting or even swallowing them. They can all be directed to leave, so the process is easily reversible. They are programmable, in that they can provide virtual reality one minute, and a variety of brain extensions the next. They can change their configuration, and clearly can alter their software. Perhaps most importantly, they are massively distributed and therefore can take up billions or trillions of positions throughout the brain . . .
There are many questions about nanobots that remain to be answered, including their price, but they are seen by researchers as a plausible means of dealing with an exponentially advancing future.  People will be far less susceptible to all kinds of ills, including misanthropic elites, if they have nanobots working for them.  

An early George Gershwin song from the musical "Miss 1917"

  Today, February 12,2024, marks the 100th anniversary of the debut of George Gershwin's "Rhapsody in Blue" in Aeolian Hall in...