HN user

typhonic

140 karma

It's not the destination that matters. It's the gurney.

Posts5
Comments58
View on HN

In the 1960's, my brother and I would walk about three miles (over Red Mountain in Birmingham AL) to the closest Radio Shack. We would each get a free battery using our cards and usually we didn't buy anything. Eventually we became pretty good customers.

I got my third MRI after having a titanium plate put in my neck, and wow was I more nervous that time than the earlier two times. I made the tech let me test the panic button to prove it worked. Of course there was no problem with the MRI.

Twenty years is a mighty short time period for expecting a huge paradigm shift in industry. In 1973 I was touring industrial plants and got to see an automated retrieval and delivery system operating in a plant warehouse. (It might have been the Copolymer plant in Baton Rouge - hard to remember.) So even 50 years may be a bit too short.

Looking back a few hundred years it is easy to see that we have made progress. In the mining industry, for example, the need for large haul trucks is reduced by long conveyors. The longest I have seen is two miles. Those conveyors are barely attended to by operators and their operation is monitored by control systems connected wirelessly and reliably.

The real leap will come, not from increased automated operation, but from automated maintenance. That won't happen until well after IOT is more fully implemented. By that, I don't mean more devices connected to the Internet. In my opinion, IOT's potential lies in the future of the "Things" making decisions based on information from the connected devices.

Coming from the Controls Systems Industry, I have seen a few flavors of the SRS. Sometimes we call them Functional Requirements Specifications (FRS). The IEEE has a decent standard for how to put one together, although they call it Software Design Description, "IEEE 1016-2009 IEEE Standard for Information Technology--Systems Design--Software Design Descriptions."

The two industries where I worked where these are well recognized and their use enforced are Nuclear Power and Pharmaceuticals.

Some personal wisdom that I picked up is "If it can't be verified, it isn't a requirement." As an example, I was one told to change the tagnames in a program to "something meaningful." I went through several iterations before I realized that, with this particular customer, that was unachievable. None of the tagnames I built had meaning to him, and he would not give me guidance as to what would be better.

We have pet chickens that we close up every night. I built a door to let us open and close the chicken run from a web page. The door slides horizontally and is driven by a cheap electric drill motor with an all thread rod, which acts as a worm gear, and is controlled by a rpi.

I learned this technique in the mid 70s, but I didn't attend MIT. I still remember a math class in 1973 that was sort of rowdy. One of the students was presenting. He wanted to draw a circle on the board, but there were actual, occasional, spitballs. If he took his eyes off of the class he would have been a sitting duck. Not to be deterred, this student, Kem, stood at the chalkboard facing the class with a piece of chalk behind his back, touching the board near the bottom. He swung his arm out and up and, at the same time, began to pivot around. His chalk went up to the top of the board, all the way around, and back to the bottom just as he turned to face the class again. The circle was elegant, no one had time to launch a spitball, and he gained another level of respect in the class - he already had a lot.

There are plenty of technical comments here, but I have to say I got a great laugh from this post. I have dealt with many of the absurdities state side, so I can relate to your experience. By the time I got to the words Windows XP Screensaver, I was laughing so hard I couldn't read anymore. After finishing, I bookmarked you. Looking forward to more. Thanks.

In 1973 I visited the office of a chemistry professor. He and his research partner seemed to be on somewhat of a downhill slide. For years they had dreams of discovering a catalyst that would let water break into hydrogen and oxygen from exposure to direct sunlight. They never found that catalyst, and after nearly fifty years, I never even hear the concept any more.

I am now 66 and continuing to work as an engineer in a field not too far removed from a programming career. I have had the same inclination as your father and I hope he is successful. Pre-pandemic I would attend meetups in town, specifically Python related. We often had in attendance recruiters from companies with open positions. I talked to them and often they openly invited me join, even though I would have been entry level. It appears to me that there are more programming jobs than there are programmers and that some companies will take the chance on my age group. There are also companies where programmers are valued not just for their programming experience, but also for other skills they bring to the table. So, even though I have not made the transition, I think it can be done.

In 1973, a high school student from another state told me that he became interested in astronomy because of a newsletter and activity he participated in. It seems there was a grad student somewhere trying to crowdsource astronomical observations. Periodically, he would identify a time and place where it was expected that one could observe a particular star as it was blocked from view and then reappeared from behind the moon. Participants would go to those locations in groups of three, one on the spot, one some distance to the East and another the same distance to the West. The teams of three would then send in the timing of their observations so the project leader could make corrections to astronomical data. The grad student, if I remember correctly, used the mailing list to continue the newsletter for some time after the project end date. I always liked that story and I imagined it was not the only effort of its kind.

Once, while working at a large grocery store, we lost power. The emergency lights came on, but all the cash registers stopped working. One of the managers ran to the back of the store and returned with hand cranks that fit into the side of the cash registers. It was darker, but sales did not stop. The time required to re-train the cashiers was negligible.

This cyber attack will probably result in a doubling down of the same technology that put them into this position. Perhaps, in addition, they should look for a lower tech fall back approach.

> Having an advocate There aren’t enough upvotes in the world to highlight this!

My experience exactly, and repeatedly. I am old enough now to have spent many hours in the hospital next to family members. I don't say this to increase anyone's anxiety about hospital stays, but the care is better when close allies are there throughout stay.

In the 1980s I was impressed with LapLink software which I used to move files between computers. The copy I bought came with cables to connect the computers, both serial and parallel cables. The serial cable had 25 pin and 9 pin connectors on both ends. If one PC did not have a disk drive, they gave you instructions to write a short command to re-direct the serial input. LapLink would then transfer itself across the serial link and begin running.