Advertisements

Tag Archives: SSME

quicKMemos Vol. 1 No. 2

Here’s the second issue of the KM newsletter I wrote and published for the SSME KM team. This one was for January of 2006. The middle column has a couple of decent descriptions of “Lessons Learned” and “Best Practices.” What it doesn’t address, which is something many of us came to understand later, is that we don’t actually want “Best” Practices; which implies there won’t be any room for improvement, as “best” is a superlative adjective, which means it just doesn’t get any better than best. We, therefore, preferred to talk about “Better” Practices, which also fits rather nicely into the philosophy of continuous improvement. My apologies if this is boring.

Advertisements

Another Newsletter

At the end of 2005, I was still five years away from accepting an early severance package from Pratt & Whitney Rocketdyne and then retiring a couple years early. I don’t think the Shuttle program had yet been cancelled, so everything appeared to be full steam ahead. I had been deeply involved in developing the concept of Knowledge Management (KM), primarily to the Space Shuttle Main Engine (SSME) team—for which I was the lead—as well as for the entire organization, from its ownership by Boeing to a subsequent purchase and merger with United Technologies’ Pratt & Whitney Division.

So, there were two teams I was involved with: the corporate, enterprise-wide team, and the SSME team. I had convinced my management to start the SSME team before I knew there was a corporate team, and it was my primary focus of attention at the time. Starting in December of 2005, I published a newsletter for the team; a KM newsletter, ostensibly by the SSME KM team for the entire SSME program team.

When I returned to work for a couple of years at Rocketdyne in 2015, I was able to find pdf files of every issue of that newsletter, which we called “quicKMemos.” I’m am converting these pdf files into png files so I can upload them here. I’ll post them somewhat sporadically, no doubt, as I have several duties and obligations that are always tugging at my sleeve and demanding my attention. So . . . here’s the first one; Vol. 1 No. 1, December 2005.

NB – Check out the Eleven Deadly Sins of KM. They still seem relevant to me, though it’s hard for me to tell as it’s been nearly 10 years since I’ve been in a large enterprise environment.


RAIDI

Robot and Human hands touching

I have no doubt I am a very lucky person. Although I do not have an education in any science, I was able to spend approximately two decades working on the Space Shuttle Main Engine (SSME) program at Rocketdyne (through four major aerospace corporations). I spent a lot of time working with some of the brightest rocket scientists (for realz) as well as world-class engineers and scientists in literally dozens of disciplines.

Since my retirement from (what was then) Pratt & Whitney Rocketdyne, I have worked intermittently with Quantellia, LLC, an artificial intelligence / machine learning software development firm. Needles to say, I have no formal education in any computer field, with the exception of two Visual Basic classes I took at a nearby Junior College. I was introduced to one of the co-founders of Quantellia shortly after my retirement. She showed me a tool they had been developing called “World Modeler”. It was the most exciting thing I’d seen in a long time, and I was especially impressed with how it brought a highly systemic approach to modeling and forecasting in complex situations. I ended up writing several papers and a bunch of case studies for them.

In 2015 I returned to work at what was then Aerojet Rocketdyne (still is, for now) where I worked on a small rocket engine program for a little over two years. After leaving, I started doing some selling for Quantellia and, beginning in March of 2018, I became the company’s Business Manager, a position I’m still working at.

Last year we held a summit, in conjunction with SAP Global Services, at their Labs in Palo Alto. It was called the “Responsible AI/DI Summit.” In this context AI stands for “Artificial Intelligence” and DI stands for “Decision Intelligence.” One of the main purposes of the summit was to discuss how we can develop artificial and decision intelligence such that we concentrate on using them to solve humanity’s most “wicked” problems, rather than merely work at developing apps, the main purpose of which is to make money for the developers, investors, and entrepreneurs involved in the business.

Below are some of the folks who worked on the Summit, including me (the long-haired guy in the middle of the back row). Also, here’s a link to this year’s second Summit – Responsible AI/DI Summit 2019, as well as a link to the RAIDI Blog.

Quantellia and SAP folks who worked on putting it all together

As I learn more about machine learning, artificial intelligence, and decision intelligence, I will work at sharing my knowledge and understanding of these tools, and the issues they raise. I know the people I’m working with are dedicated to serving humanity, not merely milking it for profit. That pleases me and I hope we’ll be able to prove we’re doing the right things to ensure such service continues to exist and grow.


Random Memorabilia

I found this piece of historical info about the—shall we call it “first half”—of the Shuttle program in one of my collections of “stuff.” Note that it ends with the Challenger disaster, which happened almost a year to the day before I was hired in (initially as a temp) at Rockwell International’s Rocketdyne division, working on the document that would prepare the SSME (Space Shuttle Main Engine) for the return to flight on September 29, 1988. Note also, as engineers are wont to do, the word “Incident” is misspelled at the bottom of the sheet. Color me unsurprised. OV-105 (Orbiter Endeavour) is also not on the list at the very bottom of the page.

I don’t imagine this will be terribly interesting to anyone who isn’t a bit of a human space flight geek like me but, as I have said recently, I need to memorialize some of the things I’ve kept over the years. They may not be of value to anyone but me—hell . . . they may not even be of value to me—but I want to get them scanned or reproduced and put out into the aether, for my sanity and possible future use.


Nu? So Where’s My PhD?

Here’s an award I received when I was working on the Space Shuttle Main Engine (SSME) program back in the day. NB – This was a few years after I hired in and Rocketdyne was then owned by Rockwell International, before it was purchased by Boeing, then United Technologies, then Aerojet (current owner).

It’s entirely possible I awarded this to myself. If only there was a way to be sure.

Actually, when I first hired in (after being a “job shopper”, a temp, for a little over a year), I did take a great class on how the SSME operated . . . still operates as today’s slightly modified RS-25, four of which will power NASA’s Orion spacecraft, providing 2 million pounds of thrust and working with a pair of solid rocket motors to generate a total of 8 million pounds of thrust. Orion—also known as SLS (Space Launch System)—is being built to return humans to deep space destinations, including the Moon and Mars.


Sport of . . . Old Farts?

My father took up golf late in life and he wanted me to golf with him. I was 15 years old, which means he had to be about 38. He wanted me to golf right-handed, but I was a dominant southpaw and I refused to do it. Reluctantly, he got me a left-handed beginner’s set of clubs. I even took lessons—if memory serves, I took one lesson from Cary “Doc” Middlecoff at what was then called The Joe Kirkwood Jr. Golf Center . It was on Whitsett Ave., just North of Ventura Blvd. It’s now called Weddington Golf & Tennis. Read the second paragraph at their website’s home page for a little history on the site.

Cary “Doc” Middlecoff, somewhere near his heyday

My golfing did not last long. At 15 I had started to surf, which seemed so much more challenging at the time. Besides, golf was for old men and surfing was a young person’s sport. I gave up golf, though I hung on to the left-handed beginner’s set of clubs the old man had purchased for me. I even used them once-in-a-while to hit a bucket o’ balls.

Fast forward 31 years. I had been working at Rocketdyne for maybe three years. My first year I was a “job shopper”—a temp—working on the FMEA/CIL* document for the Space Shuttle Main Engine program, in anticipation of a return to flight after the Challenger disaster. I then was hired in as a full-time employee, working in the Fight Ops team. I was fortunate enough to be in the Rocketdyne Operational Support Center (ROSC) when Discovery lifted off from Kennedy’s Launch Complex 39 on September 29, 1988.

I had helped design the layout and overall configuration of the ROSC, and being there for that launch was my reward. I didn’t know enough about the operational parameters of our engines at that time to understand exactly what I was looking at that morning, but the room was filled with displays showing engine performance as Discovery lifted off and ascended on its approximately 525 second flight to LEO.

Flight Patch for STS-26 | Return to Flight after Challenger | Space Shuttle Orbiter “Discovery” | OV-103

That evening a bunch of us went to celebrate the successful launch and our nation’s return to space flight. We were elated . . . to say the least. We went across Victory Blvd. to a restaurant called Yankee Doodles. Somehow, I got into a conversation with the person who turned out to be the Manager of the SSME’s Program Office and, once he found out what my role had been (and that I had a Juris Doctorate; a Law degree) he offered me a job. After some discussion with my current management, I decided to take it.

It wasn’t long before the team I was now on decided to have a golf tournament, and they of course wanted me to play. Not because they knew anything about my golf game (how could they?) but because they needed warm bodies to show up on the course, as well as pay for the round, prizes, and food. I was reluctant; after all it had been over 30 years since I’d actually played and, in fact, I don’t believe I had ever played on a full-size course.

I decided to give it a try. I don’t remember what I did for clubs because, by then, I had rid myself of that old beginner’s set. I remember going to Simi Hills Golf Course and hitting some balls. Honestly, I can’t quite remember where that first tournament was played, but I know I got hooked . . . bad. I had my uncle’s friend make me a set of golf clubs and I began practicing with a vengeance. I cobbled together a newsletter for the course, filling it with ridiculous and comedic stories. I showed it to the General Manager and told him I could do that for them every month.

The 18th Green at Simi Hills Golf Course

He told me to go ahead and, shortly after, I was hitting as many balls as I wanted on the range and, a bit later, going out on the course with the GM and the Head Pro – getting tips and playing lessons for free. I eventually was able to play for free as well, as long as I didn’t try to abuse the privilege by playing during peak hours. Within a fairly short time I had my index (similar to handicap) down to 12. I was well on my way to becoming a single-digit handicapper, but it was not to be.

I started having back and hip pain and, even with going to a Chiropractor and seeing my doctor about it, nothing was helping. Little did I know what was coming. Just before New Year’s Eve, December 31, 1999, I had an attack of sciatica that had my wife calling 911 to have me transported to the nearest hospital. I was on crutches for a month, and a cane for two months after that. I still experience numbness/tenderness in my left foot and don’t expect it will ever entirely heal.

Fortunately, I eventually found Robin McKenzie’s wonderful book, “Treat Your Own Back” and, after religiously doing the stretching he recommends, for weeks, I was back on the course and healing rather nicely.

Now, I don’t remember if it was before or after my back problems, but I became good friends with one of the professional golfers at Simi Hills, and he was involved with a company called Golden Tee. They had opened up a practice facility at Moorpark College and were planning on building a new golf course in the hills just below the Ronald Reagan Presidential Library here in Simi Valley.

Me and good ol’ Paul What’s-his-name practicing our putting

As you may surmise from the graphic I’m including in this post, I had a really sweet deal with Golden Tee. Unfortunately, the guy on the left of this picture (his first name was Paul; I don’t remember his last name, and I think he’s moved on to that 19th hole in the sky. Suffice it to say, things got real ugly. I found the record of a court case where Golden Tee sued the Ventura County Community College Board . . . and lost. Actually, I think it was right around this time I experienced my bout of sciatica and, shortly thereafter, decided (along with my wife, of course) to adopt our first child . . . but that’s another story.

* Failure Mode and Effects Analysis/Critical Items List


Preserving My Past

The time has come for me to simplify . . . to apply some feng shui to my collection of old (ancient?) paperwork, some of which is more than several decades old. Paper is the one thing I seem to be a bit of a hoarder with; that and old clothing, I guess.

I am coming across papers, letters, and notes I’ve written over the years, many of them from my over two decades of service at Rocketdyne, where I was privileged to work on the Space Shuttle Main Engine program. In that time I worked for (without changing desks) Rockwell International, The Boeing Company, and the Pratt & Whitney Division of United Technologies. After I accepted an early retirement package in 2010, I returned as a contractor to work for Aerojet Rocketdyne in 2015, where I worked for a bit over two years.

Recently, I purchased a small, portable Brother scanner and I am slowly scanning old papers I’m finding. Inasmuch as I’m now publishing far more frequently to this blog, I’ve decided to save some of these things so I can throw the paper away and still have a record. It’s been over nine years since I retired and I find I’m forgetting what working in a large organization was like. Reading some of the documents I created helps me to remember what I did, as well as to feel reasonably confident I wasn’t just spinning my wheels.

What follows should be somewhat self-evident. It’s a letter I wrote to my manager in 1994, now over 25 years ago. I think I sound pretty reasonable, and I’m gratified to know I was pushing—pretty hard, I think—for positive change back then. I’m not an IT person; never went to undergrad and, besides, the earliest PCs didn’t come into existence until I was nearing my thirties. However, I did recognize the value such tools brought to managing and operating a business and I have always been a big promoter of technology in the office. At any rate, this is more for me than my readers, but some may find it “amusing.”

PS – I scanned the original “memo” in .jpg format and the accompanying Lotus presentation materials in .pdf, which you’ll have to click on if you’re interested in what Lotus was doing 25 years ago, before its acquisition by IBM.


They’re Finally Catching Up To Me

The last few years I was employed at Rocketdyne, my job – which I essentially created – was to research social media for the purpose of bringing it inside the firewall for internal communication and collaboration.

As a result, I became both well educated in the use of numerous apps and platforms, and excited about the possibilities they represented. When the Space Shuttle program was nearing it’s end, everyone over sixty was offered an early severance package.

After some research I decided to accept the offer, which I characterized as a “gold-leafed handshake.” I was pretty excited about going out on my own and offering social media marketing services to local small businesses. Unfortunately, very few people knew what I was talking about and most businesses remained content to spend $200/month on a Yellow Pages ad that likely got thrown in a recycle bin the moment it arrived.

I’m not entirely certain, but it does seem like things have changed and many more businesses understand the value in promoting via Facebook, Twitter, Pinterest, etc. As a result in finding it easier to get clients to help and supplement my retirement income.

This year promises to be very interesting.


Why You Don’t Want to Retire

When I joined the Space Shuttle Main Engine program at what was then Rockwell International’s Rocketdyne division, I had never heard the men in my life use the word “retirement.” The reason; they were mostly small businessmen who expected to work until they dropped dead. And that’s exactly what happened to every one of them.

At Rocketdyne, however, it seemed everyone I worked with talked incessantly about retirement. They also talked a lot about what they’d do if they won the lottery, but that’s another story.

A year later, I secured a position as a regular employee (I had been a temp; what they called a “job shopper”) and had to make decisions regarding my future retirement. Most notable of those decisions was whether or not to participate in the company’s 401K program. At the time, the decision was a no-brainer. The company matched employee contributions dollar for dollar, up to 8% of one’s gross income. It was a way to save up a fair amount of money as a nest egg.

Even so, I never saw myself as retiring; I felt I needed to work at something until I either died or was so infirm or incapacitated I wouldn’t be capable of anything useful. I fully expected to work at Rocketdyne until I was at least eighty, despite the fact I had little reason to believe I would live that long.

I ended up leaving what by that time was United Technologies’ Pratt & Whitney Rocketdyne division. That was over seven years ago and I’m still not retired. I don’t expect I ever will retire and, frankly, the concept still means little to me. I do, however, enjoy some retirement income from that original 401K, as well as a small pension and social security. It’s not enough for me to stop working, but I really don’t want to stop. Here’s why.

Yesterday, Jeremiah Owyang posted a graphic on Facebook that caught my eye. It depicts a Japanese concept called Ikigai, which the people who live in Okinawa, Japan live — and live long — by. The concept translates roughly into “the reason you get out of bed in the morning.” It makes an interesting Venn diagram, as you can see below.

Ikigai

The “Sweet Spot” Most All of us Would Like to Achieve

I shared his post with the following comment:

I believe I’ve hit this sweet spot a couple of times in my life, most notably when I worked on the Space Shuttle Main Engine program. I’m pretty close to it now as well, working with Quantellia and machine learning. How about you?

A few of my former colleagues chimed in and one of them actually found the original article in which the graphic had appeared. It’s short and not that old. The title is “Why North Americans should consider dumping age-old retirement.” You can find it here if you’d care to read it.

This is what I think we should all strive for. This is the kind of balance that brings peace of mind and contentment. I’m lucky to have experienced Ikigai in much of my work life. In explanation of how I felt I was working on “What the world needs,” I later commented:

I should point out, especially, I believe we need to establish not merely a scientific outpost off-planet, but a cultural outpost as well. I have no doubt Earth will experience an ELE someday and we need to get established elsewhere, if for no other reason than to repopulate the Earth after such an event, and have a leg up recalling all that we’d accomplished until that unfortunate event. Perhaps we’ll be able to divert any asteroids or comets we discover heading our way, and such a place won’t be necessary, but there’s no way to be completely sure of our ability to avoid catastrophe. I, therefore, felt it was somewhat of a sacred duty to play whatever small role I could to get humans into space. It’s why the cancellation of the Shuttle program – when there was nothing in the pipeline to replace it – was so disconcerting to me. It was a big reason I accepted an early severance package offered to all employees over 60 (I was almost 63 when they made it).

Now, over seven years since my “retirement”, I’m still fortunate to be working on something I believe the world needs (though there’s considerable dispute over whether it will destroy us in the long run). The only place I fall short is in the area of doing what I’m good at. This is because I’m not a data scientist or a designer or programmer. I am, however, a reasonably good salesman and have other skills I’m bringing to bear on my work with Quantellia. I expect my studies and experiences will fill up this hole reasonably soon.

I do believe everyone should be able to approach Ikigai. There is much the world needs and, despite the predicted crisis expected when the machines take over the world and millions of jobs disappear, there will still be lots we can do to lead fulfilling lives. I am a supporter of universal basic income (UBI) and find Jeremiah’s closing words from his Facebook post instructive:

Soon, automation will disrupt Ikigai, in the looming Autonomous World, and we’ll need to reset what our “reason for being” is.

I’m betting that we’ll accept the imperfect arts, humanities, and engage in wellness and fitness for longevity.

I happen to go along with those who believe UBI will unleash creativity and entrepreneurship, though I recognize the pitfalls it may present as well. Regardless, there is a looming crisis and, frankly, my current efforts in selling machine learning services and products, is accelerating it. I doubt we can step back from the cliff, so it may be time to give everyone a kind of “golden parachute”; at least one sufficient to allow them a soft landing when that crisis arrives.


A Career Change at 70

When I was in High School (1962 – 1966) it took me three and a half years to escape) there were no computer classes. Although there seems to be some disagreement on when the first personal computer was invented, even the earliest claim puts the date six years after I graduated. There was no such thing as a computer, let alone a programming or coding, class. Also, I did not attend university and, to my recollection, nobody I knew at the time was interested in computers or information technology. Actually, I was a terrible student and wasn’t interested in much of anything by the time I finished High School.

IBM Memory 50

The IBM Memory 50 Typewriter

Fast forward to 1974. Despite having no undergraduate education, I was able to secure admission to an accredited Law School, located not far from my home in the San Fernando Valley. I began in the fall of 1973 and the following year I managed to get a job in the law office of a sole practitioner in Beverly Hills as a legal secretary/law clerk. Shortly after I began, the lawyer I worked for purchased an IBM Memory 50 Typewriter. I attended a one-day class where I learned how to use it. This was my first introduction to anything resembling “computing.”

The office later upgraded to an Artec Display 2000, which had an LED readout of approximately 30 characters. There was no CRT display. It used two 8″ floppy disks and had a document/data merge capability that made it perfect for boilerplate documents, e.g. Pleadings, Interrogatories, Summonses, etc. It was a great leap forward in word processing.

Edward Ladd & Sons

The Family’s Wholesale Food Business

Shortly after graduating from law school I had, for numerous reasons, decided spending the rest of my work life around the judicial system was not something I really had my heart in and, after much gnashing of teeth and going over my alternatives, I decided to join my family’s wholesale food distribution business. One large factor in making this determination was my father suffering his second major heart attack. The business was supporting my mother and my sister, who was only 10 years old at the time. I felt the need to help the business grow, ensuring they would be taken care of if my father were to die . . . which he did eight years later.

Edward Ladd & Sons Jacket

Our company jackets. Logo design by me, jackets created by Cat’s Pyjamas.

After a couple of years, the business had grown substantially and, given my desire for another type of challenge, I once again struck off on my own. I dabbled in a few things, then joined forces with a couple of CPAs and formed a royalty auditing business, serving some very high-end artists. The company first purchased an Apple computer (I can’t recall if it was a II or a IIe but, based on the release dates of the two, I’m inclined to think it was a II). We later purchased a Northstar Advantage, which used the CP/M OS and two 160 KB, 5.25″ floppy disks. We also purchased a dot matrix printer and, in anticipation of taking the system out on the road, we had Anvil make a hardened case for the two, with room for cabling, paper, and instructions to be packed inside.

At that point our audits required us to visit the artists’ recording companies, and my first visit was to RCA records in the Meadowlands of New Jersey. Standard procedure for the record company was to stick us somewhere that was relatively uncomfortable, then bring us stacks of paper, which we then transferred to ledger pages. Upon returning to our office in Playa del Rey, we would then have to transfer all the data to a spreadsheet; we were using SuperCalc on the Northstar Advantage, though we had started with VisiCalc on the Apple.

I suggested taking the computer with us when we performed audits, so the people who went out on the road could enter the numbers they received directly into an electronic spreadsheet, thereby saving a huge amount of time and stress. We were also using WordStar at the time for writing the narratives that would accompany our audit analysis.

My first experience with programming came when we were contemplating taking the system out on a European tour with Neil Young. I sat with my friend and partner, who had performed many a box office reconciliation, and we sketched out the different scenarios that were used to close out the night’s receipts. Doing so required the use of nested “if” statements, which determined the precise equation to use for each venue. Unfortunately, that same friend who had worked so diligently with me to create the formulae that would power the spreadsheet never felt comfortable with using it by himself and it never went out on the road.

Sinclair ZX81

My Very First Computer, the Sinclair ZX81

It was also around this time I purchased a Sinclair ZX81, which was a small computer that had a membrane keyboard and used a cassette recorder to save programs on. It also had its own OS, as well as its own version of Basic, which I endeavored to learn. The first program I wrote, which took me all night to complete, counted down from 10 to 0, in the center of the screen. It then plotted a single pixel (resolution was 64 x 48) at a time, starting from the bottom and, after reaching a height of six pixels, began plotting another pixel above the previous six and erasing a pixel from the bottom of the stack, until it left the screen at the top. This required me to learn how to use either (I don’t recall the exact commands; it’s only been a little over thirty-five years) nested “if” statements or “do while” commands.

Fast forward to 1984, the year my father died. Shortly afterward, I returned to help my brother keep the business going. We purchased a more advanced Northstar Advantage, which had a huge hard disk that could store 5MB of data! At the time, we also purchased a copy of dBase II, which was one of the first database systems written for microcomputers. I taught myself how to write systems using their programming language, which I wrote using WordStar. I wrote an entire accounting system for the business. My favorite component was the preparation of a deposit ticket, where I laboriously emulated the workings of a calculator in allowing for numerous methods of inputting dollars and cents (whether or not a decimal point was included) was the real differentiator and sticking point for me but, after much trial and error, I figured it out.

Unfortunately, my brother and I didn’t see eye-to-eye on the direction the business should go in and, after a while I left again, this time taking temporary jobs to keep me afloat. It was during this time I worked for a while at a litigation support firm that used a DEC minicomputer and several of the earliest versions of the Macintosh. All of my work with computers was novel for me, as I never took any classes — with the exception of that class I took to learn how to use the IBM Memory 50 typewriter. I taught myself how to program through reading and doing, sometimes taking dozens of iterations to get a bit of code correct.

In 1987, I had been working for a company that made hard drives (Micropolis). Their business was highly seasonal and, on one particular Friday, all the temps got summarily laid off. I was using Apple One at the time to send me out on engagements and, thanks to my willingness to show up wherever, and whenever, they would offer me a job, I got a call from them on that very Friday, telling me to report to Rocketdyne the following Monday.

By this time I had been shifting my focus from working under the hood, to figuring out how to best use the systems and tools that were rapidly evolving as business tools. I was beginning to focus more on business results with whatever was available. My first responsibility at Rocketdyne was to enter text I received from Engineers into a document called a Failure Modes and Effects Analysis / Critical Items List (FMEA/CIL). It was in direct support of recertifying the Space Shuttle Main Engine (SSME) for eventual return to flight after the Challenger disaster.

SSME

SSME Hotfire Test

It was a strange task, as the document was clearly text-based, yet we were using a spreadsheet to create it. I suppose it made some sort of sense, as the company was an engineering company and that’s kind of how engineers see the world; in numbers, rather than words.

I also worked with a stress engineer on creating an app (we didn’t use the term back then, but that’s what it was) that could be used to predict crack propagation and its effects. I was unfamiliar with the equations behind the program, but my job was to use dBase II to create an interface that allowed for data input and crunched the numbers. It was fun and was successfully used for some time after that.

One year after joining as a temp (referred to as a “job shopper”) I hired in full-time and began working with the Flight Ops team. It was exciting and I spent much of my time massaging telemetry data from hot fire tests of the SSME. I received flat files from a Perkin-Elmer mainframe and eventually ported the data to Microsoft Access, which allowed for further massaging and reporting.

In October of 1988, a little over eight months after hiring in, the U.S. Space Program returned to flight with the successful launch of Discovery. At a celebratory event that evening I met one of the managers of the Program Office. As we talked and he discovered my background, he offered me a job. I did some research and talked to my current managers, who advised me to take it, which I did. As time went on, I moved further away from anything resembling coding and, eventually, wound up concentrating on the use of software and computing tools to increase the effectiveness of me and my colleagues.

Not quite 22 years later, I took an early severance package (which was offered to everyone over 60) and retired. I would turn 63 less than a month after leaving the company. In 2015, I returned as a contractor doing something I had done nearly 20 years previously. I spent the next two years (until February 17 of 2017, to be exact) providing program scheduling for two small rocket engine programs.

Last month I turned 70. I recently signed a referral partnership agreement with an organization I worked with a few years ago. They specialize in machine learning (ML) though I was unaware of that back then. My primary responsibility will be selling their services and, when possible, any product they may create. In order to be effective, I am now studying statistics and ML, partly to better understand what it is I’m selling and partly because I’m fascinated by the algorithms that power these efforts.

I do worry that my comprehension is somewhat hampered by, if not the years, the considerable mileage I’ve managed to accumulate. There’s also a minor problem with my “just don’t give a shit” attitude about a lot of things. Nevertheless, I will persist. I intend to share what I’m learning but, as with most things these days, it may be sporadic and somewhat unfocused.

I do believe machine learning is going to drastically change just about everything humans do and I’m well aware of the disruption it might entail. I don’t however, believe that to be a show stopper. We’ve opened Pandora’s box and there is no closing it. Let’s roll!


%d bloggers like this: