Are You Monitoring Your Automated Systems?

It is hard to anticipate the real world. I’m sure the wet concrete on the road in Japan looked just like solid ground to the delivery robot. Consequently, it happily trundled into the urban swamp and got stuck. The story does not report whether the delivery company managed to get their robot out before the concrete hardened…

This is why you need careful monitoring of all the fully automated systems you are deploying. The first line of defense is automated metrics and their normal interval. For a delivery robot, the distance covered over a minute should be greater than zero and less than 270 (if you have limited the robot to e.g. 10 mph). The second line of defense consists of humans who will evaluate the alarms and take appropriate action. The third line of defense are developers who will fix the software and the alarms.

Too many automated systems are simply unleashed and depend on customers to detect that something is wrong and complain. You want to figure out you have a problem before the image of your robot encased in concrete starts trending on Twitter.

Save Energy Using Boxes

Every item in your field of vision costs you energy. Brain scans show that the automatic effort of filtering out irrelevant objects takes power, and the more items you look at, the worse your focus becomes.

You need to see fewer objects. You don’t have to throw anything out (though that is probably good, too). Simply take a number of items that have some relation to each other and put them in a box. 12 USB cables and 7 memory sticks become one object when they go into a box.

Throwing random objects into a box doesn’t trick your brain, however. Looking at a box you know contains random junk actually costs more energy, because now your brain is also thinking about the task of getting the stuff out of the box and sorting it.

Get out a box and remove some clutter from your field of vision. You’ll find that your energy increases. You just might even get around to that task you have been putting off for weeks.

Do You Let Convenience Trump Security?

Personal data on anyone is available from all the large U.S. social media platforms and ISPs to anyone who cares to ask. The mechanism is an Emergency Data Request (EDR). When law enforcement doesn’t have time to wait for a court order because someone’s life is in imminent danger, they send an EDR. This is simply an email from a law enforcement mail address. To send a fake EDR, you simply purchase a legitimate government email address from a hacker who has breached one of the more than 15,000 police forces in the U.S.

You would never divulge information on your customers based on just a plausible-looking email. But how do you ensure that expediency has not trumped security somewhere in your organization?

Stop Speaking While You Think

Do you, like, use too many, like, filler words? Sitting in a coffee shop in New York a few weeks back, I noticed that every fifth word in New York English is “like.”

Research shows that people who use more filler words are considered less intelligent, and their arguments are considered weaker. So it’s a good idea to get rid of your filler words. Here is an exercise: Record yourself on your phone speaking on any topic for one minute. Listen to the recording and count how many filler words you use per minute. Like, uh, ah, um, er, well. If you use more than one, you should improve.

Now record yourself again for one minute, this time making an effort to simply say nothing when you need to think. Pause and think instead of just babbling a filler word. People who pause while speaking are considered more intelligent. Listen to your recording and count your filler words. Hopefully, you have fewer. Also, notice that a pause of one second – the time normally filled with a useless word – is not a problem at all for the listener.

What Happens Then?

There is an easy way to avoid making stupid decisions: Asking “what happens then?” A decision is exposed as stupid when it turns out that the decision-maker did not carefully think through the consequences. Bad decisions occur when someone only looks at the immediate result.

New York City dodged a bullet when they started implementing bike lanes in the narrow streets of Manhattan. They could easily have made the stupid decision of simply marking a part of the street as a bike lane. Fortunately, someone clever at City Hall asked herself: What happens then? If you had simply painted bike lanes on streets, thoughtless New Yorkers would have wiped out bicyclists by the thousands with their car doors. So New York decided to paint a separation area between the car parking area and the bike lane. Clever.

Next time you are faced with a decision, try asking “what happens then?” several times. You might find this saves you from doing something stupid.

Don’t be Like FSB and Tesla

There are two ways to handle product problems: The right way and the Tesla way. A now-ex Tesla employee had the temerity to post videos on YouTube showing their vaunted self-driving feature in action. Unfortunately, one of his videos showed his supposedly self-driving car running down a bollard before he manages to react. He was fired by Tesla immediately after posting the video.

If you have a problem, acknowledge it and fix it. Getting rid of everyone bringing bad news is what made Putin think he could easily conquer Ukraine. Don’t be like FSB and Tesla. 

Play the Minimalism Game with Me

You have too much stuff. The average American household contains 300,000 items plus whatever is in their storage unit. You might think that having too much stuff is harmless, but it isn’t. Every item you own is taking up a little working memory in your brain. Each item has to be stored, repaired, charged, cleaned.

If you want to make a change in your life, getting rid of some stuff is a good place to start. If you are up to the challenge, join me for a 30-day challenge invented by The Minimalists. The rules are simple: The first day you get rid of one item. You can throw it away, recycle it, sell it, or give it away. On the second day, you get rid of two items. On the third day, three items. You don’t have to do the math in your head – if you stick with the challenge for all 30 days, you’ll end up 465 items lighter. Who’s with me?

Improve Internal IT

If you think it hard to retain IT talent, spare a thought for the leader of customer service. 83% of customer service agents feel overworked and 62% consider quitting. IT cannot give them a pay rise or remove obnoxious customers, but we can give them useful IT systems.

28% of customer service workers agree completely or somewhat that their IT systems help them do their job. That leaves 7 out of 10 who feel their IT is working against them. When was the last time you sent an expedition out into the trenches of your organization to find out what was bothering your users the most? Sometimes, there are little things that IT can easily do to dramatically improve the effectiveness of internal IT.

Fight for Your Hiring Process

In the war for talent, are you like the Ukranians or the Russians? Canonical, the publisher of Ubuntu Linux obviously hasn’t heard that the labor market is tight. One candidate published the email describing their hiring process, and it has gone viral on the internet.

In addition to to a 40 bullet point written interview, there is an aptitude assessment, personality assessment, culture assessment, HR assessment, peer interview, tech assessment, hiring manager interview and senior lead interview. The candidate withdrew their application.

If you have a hard time attracting the talent you need, examine what your hiring process looks like from the application side. Unless you actively fight to keep it simple, it will insidiously accumulate additional steps and bullet points until it degenerates into a ridiculous CYA-box-checking-exercise. You should be able to decide whether to hire someone based on their resume and two interviews.

How are you Vetting New Packages?

Some of the code you depend on was written by Ukrainians, Russians, and hacktivists. Deep in the dependency tree of NPM packages your software depends on, you will find node-ipc. That package was recently drafted into the ongoing war in Ukraine. If you are in Russia or Belarus, it will delete your files. Otherwise, it will only write an anti-war message to stdout and put it on your desktop.

As a professional organization, you are surely not just getting the latest software packages directly from a repository on the internet. But what is your procedure for vetting new versions you incorporate into your blessed repository? With the current threat level, having a single overworked developer do this in addition to his normal development tasks is not a good idea.