
Certainly everyone who is over sixty has experience becoming invisible. This is especially true in the world of technology where the default assumption is that you start losing your technological edge when you reach forty-five. By fifty most tech companies will start thinking that maybe they should find an excuse to move you out of the company. If you are not gone by sixty, the hope is that you will fade into the wall like someone in a science fiction time travel movie.
I worked at a startup when I was fifty-seven. As I remember, there were two employees besides myself that were over thirty in our staff of around forty. I was hired for my management expertise. I was an Apple manager for over a decade. Since it was the first company for many of them, they mostly missed the extraordinary productivity that comes from the fluid roles that more mature organizations strive to make happen.
I felt like I was in a strait jacket and my opinion was not wanted except when it flowed from my job title. I eventually decided that there was a lot of corporate wisdom that could not be transferred. Many of the situations they faced, I had already faced in my career sometimes more than once. Yet they were convinced that their approach was bound to be right. There was little satisfaction in seeing them learn the hard way and never figure out they could have gotten there a lot easier with some advice.
Everyone who has worked in a large organization knows that there are employees, often unheraled, that know how to keep things running sometimes with duck tape and magic. There is another kind of employee who is so focused on their one task job that they rarely calculate the risk of their actions.
In the early days of the computer age in the late eighties a few years before the Internet, we were living in Roanoke, Virginia. I was the higher education account representative for Apple for the state of Virginia which meant that I spent most of my time in nearby Blacksburg. During the rare times one of the system engineers would come down from our Columbia, Maryland office, I would invite him to stay with us. We had lots of space and a pretty nice network with a LaserWriter and a few Macs that let him work if he needed. It was well before laptops. If you know system engineers, they live to tinker with computers to make sure everything is humming. This particular engineer would always do some upgrade to my network or computers that broke the relative simple world of computers that I used to accomplish my work. He never meant to break anything, he was simply fixing something that looked like it needed fixing.
Fast forward thirty-six years, I have a pretty sophisticated nework with thirty devices hooked to a 2 GB fiber connection to the Internet. I have a sixteen port Cisco Gigabit Ethernet switch and a Synology DS1812+ 10.8 TB (Network Attached Storage) using a RAID (Redundant Array of Independent Disks) configuration on its eight 2TB drives. A couple of weeks ago a drive went bad in my NAS. I had to switch it out, order and install a new one, then let the drive rebuild itself.
I am seventy-seven. Asking for help would have been like a root canal, I had to do it myself because my son who lives with us is uninterested in helping on anything technology related. He thinks I should ditch the NAS which he gave to me and switch everything to the cloud. My guess is he thought I couldnโt do it and the frustration would drive me to move everything to the cloud. Much of the stuff is already backed up to the cloud but I like having my lifetime of files in my house.
While my network which has Macs, Windows, Linux computers and three printers on it along with the garage door opener, appliances and a bunch of other devices is pretty sophisticated for a home network, but it doesnโt even register on the scale of the commercial networks and the software that controls so much of our lives.
Even so when I brought my NAS back up after the drive replacement, I could only see the fileserver running on the NAS with my Windows computer. I did some searching on the Internet and came up with a solution that worked. Because of years of experience, I had an idea of what was wrong and resolving it was easy. Since then the network has been up and running for 14 day(s) 2 hour(s) 56 minute(s) 57 second(s). In over a decade of use, I have managed to fill up 1.8 TB or 17% of the drive’s 10.8 TB.
Had I been the IT guy in a small business and managing their network, I think they would have been happy unless they had fired me a decade ago after setting up the network because I was getting too old. They might or might not have found someone younger who understood the network like the guy who built it. Not only did I build it, I built it once at our coastal home, tore it down, and recreated it a second time when we moved to the Piedmont nearly six years ago.
The world of big networks running everything from air traffic control to our banking, shopping, social media connections, email, and photo storage is many orders of magnitude more complex than my little network. Yet somewhere in each company are people who built their network and actually understand how it works and what parts can be changed without bringing down the whole enterprise. My son was a worldwide network designer for a large company until his job got outsourced to India. His whole division was outsourced. It was an industry trend because it maximized profit.
Maybe it is time we start maximizing service and protecting that local expertise before it really disappears. Profits only grow if service is reasonable and reliable. Profits disappear when reliability goes looking for the missing experts.

























