The Right Place at the Right Time

 

Saturday evening, my wife and I were in our usual position – rocking chairs on the porch overlooking our neighbor’s hayfield and watching the lengthening shadows. Although we are nominally reading, we mostly look out at the waves across the hay. I happened to look up and saw a large bird high up in the air. It wasn’t flying like a vulture (which is a pretty common occurrence here). Then, I saw the white head and tail feathers – it was a bald eagle. We stood up and watched as it soared higher and higher until it flew west over Short Hill Mountain. It was only visible for about 30 seconds and if I hadn’t seen it in the 15 seconds it was visible from our chairs on the porch, we would have missed it.

We were in the right place at the right time.

We have had other bald eagles fly by – maybe twice a year. One time a couple of years ago, as I was walking back to the house, one flew over so low that I could hear the “swish” of its wings. It was only visible for about 10 seconds. Once again, the right place at the right time.

This is often the case with wildlife sightings around here. Except for the deer and groundhogs, most animals pass through pretty quickly. From our kitchen table, we have seen wild turkeys, weasels, foxes, and many non-native birds go by. Again, we had to be in the right place at the right time to see them.

The sighting yesterday struck me because I had just been thinking about how my career had been a case of being “at the right place at the right time.” That morning, I had gone to a monthly Linux meeting where the topic was “Artificial Intelligence and Machine Learning – AI/ML.” The presenter worked for Red Hat – a large software company which among other things has a lot of support for those who are migrating large projects to “The Cloud” (i.e., someone else’s big computer located somewhere else). She gave a good overview of the various types of AI/ML algorithms and what various Red Hat customers were doing with them, but it was clear that her feet had “never touched the ground.”

The final slide was all of the ways that Red Hat could support someone developing this type of application. The chart was like a multi-layer cake with maybe six levels of abstraction and each layer had maybe four or five sets of libraries. It was clear that with this sort of environment, it would be “Libraries all the way down.” No wonder she wasn’t real clear on the actual implementation details. After the presentation, someone asked if he could play with the techniques on his laptop or if he had to go onto “The Cloud.” The consensus was that the Cloud was necessary.

I am retired now, but most of my career has been in Embedded Systems. That is where there is a computer chip involved, but it doesn’t look like a computer. (did you know that there is a computer inside the removable LIon battery in your laptop? That was what I did in my last job).

When I started working, Embedded Systems didn’t exist as a “thing” and I was there at the start. I happened to start working at a smallish company which did mostly military signal processing and pattern recognition systems. Over the next 11 years, I worked on a large variety of projects from Radar signal processing ( to identify the type of plane targeted), sonar signal processing, translation of hand-sent Morse code – including the identity of the sender from his ‘Fist’ used in sending the code. We also developed one of the first speech recognition systems and I was responsible for developing an Operating System that allowed 4 simultaneous speakers to speak and be recognized,* potentially translated and output in a desired format which could be text or a speech synthesizer. There were several other classified projects, but I would have to kill you if I told you about them.

Now all of this was done on the minicomputers at the time with 32-64k bytes of memory, no real mass storage, and slow processors. That is, each was done on systems with much less capability than a modern laptop.

On each project, I had the overall responsibility for the data analysis, algorithm design, and coding/testing. If there was a problem, it was in something I had done and it was my responsibility to find it. I loved it.

The company was small enough that my contributions were recognized and I went through 11 title changes and promotions in 11 years. Again, the right place at the right time.

These days, programmers are doing much more with systems which are orders of magnitude more powerful than back then, but they seem to do them as parts of large teams – often distributed over several locations. And they are depending on libraries which have been developed by other large teams. In such large teams, it is very difficult for an individual contributor to get noticed.

I am not sure if I would thrive in the current environment and really do feel that I was in “The right place at the right time.”

I am not sure about other professions, but I have a feeling that medicine has hit the same sort of transition. We live near a small town where our Doctor had an office. It was basically him and a couple of nurses. When I went to see him, he spent a lot of time with me and was willing to answer all my questions. He retired not long after his practice was acquired by a large multi-office multi-state company. He started spending more time typing into a computer than actually examining me. Now when we call the ‘office’, the phone is answered at a switchboard in a city about 30 miles away and everything is even more computerized. I think the ‘sweet spot’ for medicine as a career – at least for a GP – is over.

What about you? Did you hit the “sweet spot” in your career? If not, what happened?

*Early speech systems like this required a limited vocabulary, trained to the speaker and with separation between words. Things have gotten much better in the last 50 years.

Published in General
This post was promoted to the Main Feed by a Ricochet Editor at the recommendation of Ricochet members. Like this post? Want to comment? Join Ricochet’s growing community of conservatives and be part of the conversation. Get your first month free.

There are 6 comments.

  1. Susan Quinn Contributor

    I was an independent consultant for many years, so there was no “up” movement, but I was in charge! I did want to say, willow, that it wasn’t just right place, right time in your case. You obviously were very talented, too, and that had as much to do, if not more to do, with your success. I’m so glad you loved doing it, too.

    • #1
    • August 13, 2019, at 11:31 AM PDT
    • 3 likes
  2. WillowSpring Member
    WillowSpring Post author

    Susan Quinn (View Comment):
    I’m so glad you loved doing it, too.

    Thanks – I can’t imagine being good at something you didn’t love to do. I’m blessed that I never had to find out.

    • #2
    • August 13, 2019, at 11:56 AM PDT
    • 4 likes
  3. JimGoneWild Coolidge

    I work in an Embedded environment right now. We use QNX, a Linux knock off, which I’ve used before. The company is doing new systems from the ground up and I started near the beginning — just about the right time.

    I too worked in the cloud at one time! It was large mainframe computer made by Amdahl. It was a knock off of the IBM 360, I think. And it ran UTX which was an AT&T licensed Unix OS. We logged in using terminals. The actual data center was 50 miles away and had 8 or 10 Amdahls. Each had Memorex 1 Gig memory drive and had more speed than off-the-shelf Cray computers at that time. We’re talking 1988. Compiling was pretty much blink of an eye and done. Its funny how much things change and then return to the same way.

    I think, with computers, we’ve all been at-the-right-time.

    • #3
    • August 13, 2019, at 1:35 PM PDT
    • 2 likes
  4. EODmom Coolidge

    What a graceful, thoughtful note. Thank you.

    • #4
    • August 13, 2019, at 1:39 PM PDT
    • 2 likes
  5. Mark Camp Member

    I was a computer repairman at the right place and time, back in the 70’s. In that age, before you were assigned to repair logic machines you learned how they worked, when they were working. This was often in a book called the Theory of Operations, written by the people who knew how the machines worked.

    You learned partly by looking at something called a Logic Diagram. It gave all of the logic that made the theory of operations a reality. (This is the reason I have no sympathy, only infinite patience now that I’m one of them, with my fellow Trumpists when they curse and whine about Theory, saying it has no connection with Reality. In my ancient job, you couldn’t fix Reality unless you knew the Theory that makes Reality happen.)

    Fixing a broken computer just involved understanding what was supposed to happen, observing what was actually happening, thinking logically, and reading. Reading a logic diagram to figure out what to read using the oscilloscope or the voltmeter or the continuity meter or the ohmeter.

    Or reading by smelling capacitors.

    I finally got back to that something like that kind of job a couple weeks ago: All you have to do is understand what people want the machines (or the paint, or the PVC coupler) to do, and the theory of how the machines to work.

    Also, the aisle. You have to know the aisle where things are.

    Piece of cake, aisles.

    We have all ages at my new place of employment. Today I met a guy on his first day on the job. He’s studying at the county technical center, guess what? Welding?? BXXXXZZZZ! Right. Robotics.

    We old guys understand the young guy’s job of being in tech school today. You’re studying one of two things: welding, or robotics.

    They don’t understand what our jobs were, though.

    He asked what I’d done before I retired. I gave him the easy answer, the one that satisfied everyone my whole life long, the answer that allowed me to avoid explaining exactly what my job title meant, which I myself never understood, and yet gave me a respectable social rank.

    “I worked for IBM.”

    “What’s that?”

    Write it down, 13-Aug-2019. Saying you worked for IBM, from this day forward, is like saying you worked for the Fremfernix Corp. What is that, an “IBM”?

    His buddy, another young, but slightly less damp around the ears colt, said, “Come on, Cody,” or Caleb or whatever, “you know what IBM was!”

    Helpfully, I nudged, “it was like, Apple nowadays, you know?” “Oh, yeah, IBM, I remember now,” recovered Caleb.

    By quitting time, we all connected, generationally, as clumsy as it may have been. We’re good now, the young and me.

    • #5
    • August 13, 2019, at 6:19 PM PDT
    • 4 likes
  6. WillowSpring Member
    WillowSpring Post author

    Mark Camp (View Comment):
    Reading a logic diagram to figure out what to read using the oscilloscope or the voltmeter or the continuity meter or the ohmeter.

    I wonder how many of today’s Computer Science graduates know what any of these things are.

    • #6
    • August 13, 2019, at 7:36 PM PDT
    • 2 likes