Serendipity35

"Hack" sometimes has a bad reputation. But there are some good hacks.In technology and computing, it has two meanings:
1. Unauthorized Access (verb): To gain illegal or unauthorized access to data, a computer system, or a network (e.g., "My account got hacked").
2. Clever Code Solution (noun/verb): An elegant, clever, or quick fix in programming that solves a tricky problem.

We turn to space. NASA's Voyager 1 is still moving through interstellar space at over 35,000 miles per hour (56,000 kilometers per hour). It is 15 billion miles (about 24 billion km) away from Earth.

NASA's Jet Propulsion Lab wants it to keep going for just a bit longer.

There are two Voyagers, both launched in the late summer of 1977. They are wonderful relics. These older electronics give off waste heat - which is usually a bad thing - but it keeps practically every instrument onboard warm.

It will run out of power. That was expected to happen quite a while ago, but it keeps on going. So now, JPL is doing a critical power-saving hack on sister probe, Voyager 2. They’re toggling on and off Voyager 2’s key components across a coordinated sequence. It conserves energy but still keeps things from freezing.

Why Voyager 2? It was closer to Earth and had more power to test this hack. It worked and now they want to the hack on the farther-out Voyager 1.

What is their power supply? They both have modest nuclear power plants. These thermoelectric generators convert heat produced by the natural radioactive decay of plutonium-238 into electricity. That plutonium isotope is decaying toward its 88-year half-life, so less heat is being emitted.

The probes launched with 10 instruments apiece. Some have been powered down because they served their purpose when they were moving through the planets in our solar system.

I hope Voyager 1 makes it to November and hits a historic milestone. It passes one light-day’s distance from Earth. That is a fraction of one light-year, but it is also 173 times the distance between Earth and the Sun.

If it passes that point and stays online, it will take messages over 24 hours to reach it. Its 50th anniversary will be on September 5, 2027.

You may have heard the advice to speakers to open with a joke, so here we go.
A bunch of scientists created a huge machine capable of complex calculations and called it UNIVAC. Eager to test their invention, they asked it, “Is there a God?”The vacuum tubes hummed, and the tape spools spun for several minutes. Finally, the machine spat out a little card, on which was written, “THERE IS NOW.”

That's an old joke, but it seems fresh in this "Intelligence Age" of artificial intelligence and fears of a singularity. In this time of AI and having a computer in the palm of our hand, it is interesting to consider what was happening in tech history back in 1951. That was when the Remington Rand Corporation signed a contract to deliver the first UNIVAC computer to the U.S. Census Bureau.

UNIVAC I (which stands for Universal Automatic Computer) took up 350 square feet of floor space — about the size of a one-car garage — and was the first American commercial computer. It was designed for the rapid and relatively simple arithmetic calculation of numbers needed by businesses, rather than the complex calculations required by the sciences. It was intended to compete against IBM’s punch card-reading computers, but UNIVAC read magnetic tapes, not punch cards, so a special “card to tape converter” had to be designed.

Though the government contract was signed and a ceremony held on March 31, the computer wasn’t actually delivered until the following December. There was only one UNIVAC I, and Remington Rand wanted to use it for demonstration purposes. They asked for and received time to build a second computer.

The government was the first big customer of the UNIVACs, with subsequent models going to the Air Force, the Army Map Service, the Atomic Energy Commission, and the Navy.

The computer first came to the notice of the general public in 1952, when CBS used one to predict the outcome of the presidential election. UNIVAC correctly picked Eisenhower and predicted his electoral count within 1 percent, but the network didn’t release the results until after the election was called, so as not to affect the outcome.

The first commercial sale was to General Electric, for their Appliance Division, followed soon after by the Metropolitan Life Insurance Company, in 1954.

There were 46 UNIVAC I’s built and delivered, in all.

Y2K, short for “Year 2000,” was a potential computer bug caused by how dates were formatted in older software. To save memory space, early computers used two-digit years—like “97” for 1997—which in the new millennium risked misreading “00” as 1900 instead of 2000, potentially disrupting systems that depended on accurate dates (read 101).

Though a kind of panic occurred in 1999, the Y2K issue surfaced in technical literature as early as 1984. Long before it became a global concern, researchers were already flagging the two-digit date flaw. A 1984 book, "Computers in Crisis," outlined how the year 2000 rollover could break financial, governmental, and technical systems if left unaddressed.

In the late 1990s, many feared this glitch could cause widespread failures in banking systems, power grids, transportation networks, and other critical infrastructure. This idea took hold of the public imagination, spawning doomsday predictions, a booming survivalist market, and a massive global push to audit and repair vulnerable systems before the deadline—work that cost an estimated $300B-$500B. 

Because of the extensive preparations, Y2K passed without significant disruptions, however, its legacy endures. The crisis helped modernize global IT systems, accelerated the outsourcing of programming jobs, and exposed society’s dependence on digital infrastructure—prompting long-term shifts in cybersecurity and software maintenance.

The Year 2038 problem is the next potential computer time rollover bug. Many older systems store time as a signed 32-bit integer counting seconds since Jan. 1, 1970. That counter maxes out on Jan. 19, 2038—overflowing into negative time and sending clocks back to 1901, potentially crashing any older software that depends on accurate dates. The Y2K38 bug is also known as the end of 32-bit Unix time and the year 2038 problem.

 

I found a reference this past week to the original Apple II AppleWorks and it got me thinking about how amazing the program was for its time. The software was light and efficient, and it ran on limited hardware.

The "light architecture" of AppleWorks (developed by Rupert Lissner and released in 1984 for the Apple II) was impressive for several reasons. It was an Integrated Suite that combined a word processor, database, and spreadsheet into a single application. On the 8-bit Apple II's limited resources (often starting with just 128K RAM), this level of seamless integration was no less than revolutionary. You could easily share data (via a "clipboard") between the modules.

AppleWorks was written almost entirely in assembly language for the 6502 processor. This gave it incredible speed and efficiency, allowing it to perform complex tasks much faster than programs written in higher-level languages like Pascal.

Its memory management system was highly flexible and sophisticated, allowing it to utilize not just the 128K of the Apple IIe/IIc but also various third-party memory cards. It effectively made up to two megabytes of memory appear as one contiguous space on an 8-bit machine, which was a remarkable technical feat.

It became the "killer application" that extended the life of the Apple II platform well into the late 80s and early 90s. That is when I was using it in my middle school classroom, and as the computer coordinator in my building, I worked with every teacher because they all had at least one Apple IIe in their room.

Although AppleWorks was thought of as something teachers would use most of the time, the user experience was very good, and students would use at least the word processing portion. All three modules shared a consistent, menu-bar-driven user interface with simple text-based controls (often utilizing the Apple II's "MouseText" characters for visual elements like folders and separators). This was highly intuitive and much easier to learn than many contemporary command-line programs. The design prioritized ease of use, making personal computing accessible to a much broader audience, especially in homes and schools.

AppleWorks, compared to other productivity suites of the time, such as Microsoft Works or the original Mac software, demonstrates a fundamental shift in design philosophy that prioritized integration and efficiency over raw power. Earlier Apple II programs were often monolithic (like stand-alone VisiCalc for spreadsheets) or required users to switch between separate, disparate programs with different interfaces to move data. This efficiency was its competitive edge, keeping the Apple II relevant years after more powerful Macs and PCs emerged.

In the AppleWorks vs. Microsoft Works (for Mac/PC) battle (Works eventually became Apple's main competitor in the integrated suite market) Apple demonstrated a different design approach. But Apple was constrained by the 8-bit Apple II. Microsoft Works and later versions of AppleWorks/ClarisWorks (for Mac and Windows) were developed for 16-bit and 32-bit systems (Macintosh, Windows PC), and these platforms had more abundant memory, faster processors, and graphical user interfaces (GUIs).

The last time I sat down at an Apple IIe was at a tech conference, it was in a "museum "display. As crude as it might seem to users almost 50 years later, I still marveled at what it could do. I was one of those people who found so many later programs, such as Microsoft Office, bloated memory hogs with more horsepower and features than most users would ever need.

Despite the technical differences, both AppleWorks and Microsoft Works shared the goal to provide an all-in-one, cost-effective, and easy-to-use suite for casual users, students, and small businesses who didn't need the complexity or expense of full-blown professional packages like Microsoft Office or Lotus Symphony. The key difference was that AppleWorks achieved this integration on an extremely limited architecture, which is why its design is often cited as a more remarkable technical feat.