Skip to main content

Born in the Sixties and my first taste of digital


No alt text provided for this image

I was born in the sixties, 1966 to be exact. We lived in a dusty farmhouse in a valley in the KwaZulu Natal Midlands.

The main form of communications was an old black Bakerlite telephone, that operated on a party line which meant the whole neighbourhood could hear your conversation. The telephone lines used to hum, and flocks of birds used to use them to perch. The exchange in town was manual and was operated by Miss Bentfinger, so named as she always dialled the last digit incorrectly.

Our life was different. We would play. No Lego, no Steam for games, paintball, zilch! We would build go-carts to race downhill using the wheels from old farm implements. Our go-carts would take three kids and we would all climb on board to race down the steepest hill in the area. On one occasion, my brother persuaded me to climb into a tractor tyre which he then proceeded to roll down the hill. It was as awesome as bungi jumping. It went down the hill just as my dad was driving up the hill. He was not impressed and we were given a hiding. My brother was like that, a maniac. One year, we had a flood in the river. His idea of fun was that we climb into a tractor tube and ride the flood waters down the river. In those days we would be disciplined by a whip fashioned out of melted down plastic fertilizer bags. It worked better than detention, or being grounded.

The farm had a large guava orchard and we arranged armies to have fruit fights.A whole day could be taken on one battle. My dad allowed me to use weapons. Trusting me with a shotgun and later with a 7mm Magnum Sako, a highly powerful and accurate rifle manufactured in Finland. All before I was 10 years old. No ways would I allow my ten year old, or even the twelve old near a weapon of any similar abilities.

No alt text provided for this image

While I was five years old I received my first tractor driving lesson On a Massey Ferguson. Soon I was ploughing fields. This was followed by riding motorcycles and other vehicles. Even though I was unlicensed, my dad would allow me to drive to school.

Being born in the sixties, there was no digital life. We would listen to vinyl. Read about it here. The first digital device that I saw was a TI-2500 Datamath in 1973. I would sit and help my dad work out the wages each week, and then we would sit on the stoep at a table and pay the labourers who worked on our vegetable farm. The picture above is of that same calculator. It's price tag is R78.90. I found it in a cupboard today. Today you might persuade me to sell you that calculator, but there is something you can't buy, the memories! Priceless.

No alt text provided for this image

Ronald Bartels provides SDWAN solutions via Fusion Broadband.

This article was published over at LinkedIn:  Born in the Sixties and my first taste of digital


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

A checklist for troubleshooting network problems (22 things to catch)

  Assumptions! What is really wrong? Is it the network that is being blamed for something else? Fully describe and detail the issue . The mere act of writing it down, often clarifies matters. Kick the tyres and do a visual inspection. With Smartphones being readily available, take pictures. I once went to a factory where there was a problem. Upon inspection, the network equipment was covered in pigeon pooh! The chassis had rusted and the PCB boards were being affected by the stuff. No wonder there was a problem. In another example, which involved radio links. It is difficult with radio links to remotely troubleshoot alignment errors. (I can recall when a heavy storm blew some radio links out of alignment. Until we climbed onto the roof we never realised how strong the wind really was that day!) Cabling. Is the cable actually plugged in? Is it plugged into the correct location. Wear and tear on cabling can also not b