2026-02-11 23:00:41
Today, we take office software suites for granted. But in the 1970s, you were lucky to have a typewriter and access to a photocopier. But in the early 1980s, IBM rolled out PROFS — the Professional Office System — to try to revolutionize the office. It was an offshoot of an earlier internal system. The system would hardly qualify as an office suite today, but for the time it was very advanced.
The key component was an editor you could use to input notes and e-mail messages. PROFS also kept your calendar and could provide databases like phonebooks. There were several key features of PROFS that would make it hard to recognize as productivity software today. For one thing, IBM terminals were screen-oriented. The central computer would load a form into your terminal, which you could fill out. Then you’d press send to transmit it back to the mainframe. That makes text editing, for example, a very different proposition since you work on a screen of data at any one time. In addition, while you could coordinate calendars and send e-mail, you could only do that with certain people.
In general, PROFS connected everyone using your mainframe or, perhaps, a group of mainframes. In some cases, there might be gateways to other systems, but it wasn’t universal. However, it did have most of the major functions you’d expect from an e-mail system that was text-only, as you can see in the screenshot from a 1986 manual. PF keys, by the way, are what we would now call function keys.
The calendar was good, too. You could grant different users different access to your calendar. It was possible to just let people see when you were busy or mark events as confidential or personal.
You could actually operate PROFS using a command-line interface, and the PF keys were simply shorthand. That was a good thing, too. If you wanted to erase a file named Hackaday, for example, you had to type: ERASE Hackaday AUT$PROF.
PROFS messages were short and were essentially ephemeral chat messages. Of course, because of the block-mode terminals, you could only get messages after you sent something to the mainframe, or you were idle in a menu. A note was different. Notes were what we could call e-mail. They went into your inbox, and you could file them in “logs”, which were similar to folders.
If you wanted something with more gravitas, you could create documents. Documents could have templates and be merged with profiles to get information for a particular author. For example, a secretary might prepare a letter to print and mail using different profiles for different senders that had unique addresses, titles, and phone numbers.
Documents could be marked draft or final. You had your own personal data storage area, and there was also a shared storage. Draft documents could be automatically versioned. Documents also received unique ID numbers and were encoded with their creation date. Of course, you could also restrict certain documents to certain users or make them read-only for particular users.
PROFS could remind you of things or calendar appointments. It could also let you look up things like phone numbers or work with other databases. The calendar could help you find times when all participants were available. PROFS could tie into DisplayWrite (at least, by version 2) so it could spell check using custom or stock dictionaries. It also looked for problematic words such as effect vs. affect and wordy phrases or clichés.
The real game changer, though, was the ability to find documents without searching through a physical filing cabinet. The amount of time spent maintaining and searching files in a typical pre-automation business was staggering.
You could ask PROFS to suggest rewrites for a certain grade level or access a thesaurus. This all sounds ordinary now, but it was a big innovation in the 1980s.
Of course, in those days, documents were likely to be printed on a computer-controlled typewriter or, perhaps, an ordinary line printer. But how could you format using text? This all hinged on IBM’s DisplayWriter word processor.
Today we use HTML or Markdown to give hints about rendering our text. PROFS and DisplayWriter wasn’t much different, although it had its own language. The :p. tag started a paragraph. You could set off a quotation between :q. and :eq. Unnumbered lists would start with :ul., continue with :li., and end with :eul. Sounds almost familiar, right? Of course, programs like roff and WordStar had similar kinds of commands, and, truthfully, the markup is almost like strange HTML.
IBM wanted to show people that this wasn’t just wordprocessing for the secretarial pool. Advanced users could customize templates and profiles. Administrators could tailor menus and add features. There were applications you could add to provide a spreadsheet capability, access different databases, and gateway to other systems like TWX or Telex.
It is hard to find any demonstrations of PROFs, but a few years ago, someone documented their adventure in trying to get PROFS running. Check out [HS Tech Channel’s] video below.
Supposedly, the original system was built in the late 1970s in conjunction with Amoco Research. However, we’re a little suspicious of that claim. We know of at least three other companies that were very proud of “helping IBM design PROFS.” As far as we could ever tell, that was a line IBM sales fed people when they helped them design a sign-in screen with their company name on it, and that was about it.
The system would go through several releases until it morphed into OfficeVision. As PCs started to take over, OfficeVision/2 and OS/2 were the IBM answer that few wanted. Eventually, IBM would suggest using Lotus Notes or Domino and would eventually buy Lotus in 1995 to own the products.
One place that PROFS got a lot of public attention was during the Iran-Contra affair. Oliver North and others exchanged PROFS notes about their activities and deleted them. However, deleting a note in PROFS isn’t always a true deletion. If you send a note to several people, they all have to delete it before the system may delete it. If you send a document, deleting the message only deletes the notification that the document is ready, not the document.
Investigators recovered many “deleted” e-mails from PROFS that provided key details about the case. Oddly, around the same time, IBM offered an add-on to PROFS to ensure things you wanted to delete were really gone. Maybe a coincidence. Maybe not.
If you want to try to build up a new PROFS system, we suggest starting with a virtual machine. If anyone suggests that wordprocessing can’t get worse than DisplayWriter, they are very wrong.
2026-02-11 20:00:32
Luna 9 was the first spacecraft to soft-land on the moon. In 1966, the main spacecraft ejected a 99-kg lander module that used a landing bag to survive impact. The problem is, given the technology limitations of 1966, no one is exactly sure where it is now. But it looks like that’s about to change.
We know that the lander bounced a few times and came to rest somewhere in Oceanus Procellarum, in the area of the Reiner and Marius craters. The craft deployed four stabilizing petals and sent back dramatic panoramas of the lunar surface. The Soviets were not keen to share, but Western radio astronomers noticed the pictures were in the standard Radiofax format, so the world got a glimpse of the moon, and journalists speculated that the use of a standard might have been a deliberate choice of the designers to end run against the government’s unwillingness to share data.
Several scientists have been looking for the remains of the historic mission, but with limited success. But there are a few promising theories, and the Indian Chandrayaan-2 orbiter may soon confirm which theory is correct. Interestingly, Pravda published exact landing coordinates, but given the state of the art in 1966, those coordinates are unlikely to be completely correct. The Lunar Reconnaissance Orbiter couldn’t find it at that location. The leading candidates are within 5 to 25 km of the presumed site.
The Luna series had a number of firsts, including — probably — the distinction of being the first spacecraft stolen by a foreign government. Don’t worry, though. They returned it. Since the Russians didn’t talk much about plans or failures, you can wonder what they wanted to build but didn’t. There were plenty of unbuilt dreams on the American side.
Featured Art – 1:1 model of the Luna 9, Public Domain.
2026-02-11 17:00:51
Sometimes you’re looking for a component for a project that you know should exist, but you just cannot find it. Something like a 14-segment LED display, but not just one with a fixed color, instead you want some of that sweet addressable RGB-ness. Unfortunately for [EastMakes], this particular display was nowhere to be found, so he decided to try making his own.
Using addressable SK6805 RGB LEDs with a mere 1.5 x 1.5 footprint as the basis, the layout for these individual LEDs on the PCBs was determined, and a layout created in KiCad. The PCB manufacturing and assembly were straightforward enough — the thing that really makes these displays is the diffuser. Here a few different approaches were tried, including FR4 with translucent segments in the soldermask, and a 3D printed version in both white and black PLA filament.
The FR4 approach using 0.8 mm thin PCBs looked quite all right, with the addition of through vias in the 1 mm version showing how these help to boost overall brightness. The 3D printed version prototypes didn’t look too shabby either, but it would probably help a lot if this diffuser panel also fit around the LEDs to prevent light bleeding between segments.
We’d love to see this type of RGB display being experimented with, as it seems to hold a lot of promise while also definitely being something that ought to exist.
2026-02-11 14:00:01
Sometimes the simplest objects need some overthinking. This is exactly what [Chris Borge] realized when using his 3D scanner and finding that the included rotation table left quite a bit to be desired — providing him the perfect excuse to build a new one.
One of the main features of a rotation stage is the, well, rotation. This was done in [Chris]’s case with a NEMA 17 stepper motor, perfect for precise rotation of scanning. Hooking up the motor to a basic perf board with an Arduino Nano allows for on the fly adjustments to rotation speed. To really solidify the over-engineering, [Chris] applies his obligatory concrete mix to add some heft to the stage.
While the previous features could be removed/downgraded without much loss, the adjustable grid built into the top adds significant functionality. The grid is based on [Chris]’s past projects, which allows cross compatibility.
We love over-engineering here at Hackaday, especially when adding something new. For more prime overthought design, check out this over engineered egg cracker!
2026-02-11 11:00:04
Airport runways seem pretty simple, just another strip of asphalt or concrete not unlike the roads that our cars drive upon every day. We can even use these same highways as landing strips in a pinch, so you’d assume that the engineering for either isn’t that dissimilar. Of course, you can use a highway for an occasional emergency, but a runway that sees the largest and heaviest airplanes taxi, take off and land on a constant basis is a whole other challenge, as detailed in a recent [Practical Engineering] video and its transcript.
When you consider that an Airbus A380 the take-off weight is up to 550 ton, it’s quite clear what the challenge is for larger airports. Another major issue is that of friction, or lack thereof, as the speeds and kinetic energy behind it are so much higher. One only has to look at not only runway overruns but also when one skids off sideways due issues like hydroplaning and uneven friction. Keeping the surface of a runway as high-friction as possible and intact after hundreds of take-offs, tail-strikes and other events is no small feat.
Of course, the other part of runway engineering is for when things do go wrong and an airplane enters the runway safety areas, or overrun zones. This usually provides some flat and clear space where an airplane can safely bleed off its kinetic energy, with the collapsing surface of the EMAS technology being one of the best demonstrations of how this can be safely and dramatically shortened.
Another aspect not covered here that is part of these overrun zones are frangible structures, such as any localizer antennae of ILS, lighting, etc. Frangible here means that the structure easily collapses when a heavy airplane crashes into it without causing significant damage to the airplane.
It was the failure of such a design process that doomed the crew and passengers of Jeju Air Flight 2216 in December of 2024, when the airplane during an emergency belly landing skidded over the end of the runway. Although there was a lot of open space after the ILS localizer array with just a flimsy wall and further level fields, the ILS array’s base contained a poured concrete base on which the airplane effectively pulverized.
2026-02-11 08:00:20
A common sight in ‘smart homes’, door sensors allow you to detect whether a door is closed or open, enabling the triggering of specific events. Unfortunately, most solutions for these sensors are relatively bulky and hard to miss, making them a bit of a eyesore. This was the case for [Dillan Stock] as well, who decided that he could definitely have a smart home, yet not have warts sticking out on every single doorframe and door. There’s also a video version of the linked blog post.
These door sensors tend to be very simple devices, usually just a magnet and a reed relay, the latter signaling a status change to the wireless transmitter or transceiver. Although [Dillan] had come across recessed door sensors before, like a Z-wave-based unit from Aeotec, this was a very poorly designed product with serious reliability issues.
That’s when [Dillan] realized that he could simply take the PCB from one of the Aqara T1 door sensors that he already had and stuff them into a similar 20 mm diameter form factor as that dodgy sensor unit. Basically this just stuffs the magnet and PCB from an existing wart-style sensor into a recessed form factor, making it a very straightforward hack, that only requires printing the housings for the Aqara T1 sensor and some intimate time between the door and a drill.
