Chemistry

Some time back (lol) someone asked me if I was “time-blind”. Lovely pejorative, huh? I thought first about how ridiculous of a question that was, and then thought about it for a while more and realized that there is more than one way to perceive time, and neuro-diverse (ND) people seem to be prone to it.

Let’s go there.

The traditional perception of time is based on the clock or calendar. I will call this clock-based time or calendar-based time. It is focused on units of duration – how long something takes to happen or do or whatever. A meeting is one hour long. A week is seven days long. A car trip is seven hours. Going to college is four years. And so on. The world basically runs this way. Neurotypical (NT) people generally run this way.

ND people are often found to be less focused on duration – we can become engaged in topics and lose track of clock-based time, frustrating those around us. This does not mean we are “time blind”, it means that we perceive time differently than those who perceive clock-based time and the durations that characterize it. Time either happens or does not happen for us. That’s why an ND person may tell you something is happening “tomorrow” and mean next month. “Tomorrow” in this case is the next time that whatever is going on will happen again.

This standard thinking of time as limited to standard units of duration such as hours and months is insufficient and inconsistent for people like myself. Instead of perceiving time in units of duration, we perceive it in units of events. Each event has a start and finish. I have three event states – not started, in progress, and finished. For example, when someone asks me how long a task will take, it is hard for me to estimate. Instead of hours, I see the task in terms of steps that have to be linked up and completed. I call this type of time event-based time to differentiate it from calendar-based time or clock-based time. Keeping event-based time is part of the systemizing skill group.

The value of event-based time is best demonstrated when laying out a Gantt chart. Durations are important, but without the correct linking of task starts and finishes, the chart is meaningless and adds no value to the project plan. This is the area where event-based time people excel – lining up things so the work gets done in the correct order and the overall task completes on time.

Next time you want to call someone “time-blind”, please take a step back and ask yourself if they instead run on event-based time. Once the architecture of event-based time is established, the event-based person can start to plan for better recognizing clock-based time and the clock-based time person can start to recognize the value the event-based time thinker brings to the table.

Hopefully, we can retire the pejorative “time-blind” in the near future.

Last week, I posted a photo of an IKEA Lyster curtain rod end. This morning, battling an epic headache of no known origin, I remembered to take some more pics and a video to explain the whole thing. Remember, this was done at least twelve years ago (likely closer to fifteen), and that I have no shame whatsoever.

I wanted a glass doorknob for a shifter in the B5. Kind of boring, but functional. I didn’t like the shifter on the car as it was delivered. It was even more boring. I never did find a cool glass doorknob, but wandering through IKEA, I found the Lyster bit, and a short call to my dad later netted me a threaded-to-fit stainless steel adapter. This happened.

Then, because nothing entertains me like a bunch of glowing LEDs, this happened.

…and this…

Yup, I wired it into the dash dimmer properly. Unfortunately, the acrylic Lyster bits are a bit fragile and I get about a year out of each one before the base cracks off. Now, I run the rubber shifter knob out of my old Rabbit Convertible. It’s a bit more cold-weather friendly. Reverse is in the wrong place, but that is a topic for another post.

The whole shebang kept the denizens of ClubB5.com entertained for a while, because no car is sacred and this was good for April Fool’s if nothing else.

Anyway, about four or five years later, I was wandering around a Murray’s looking for something, and discovered that my utterly fabulous knob was now a thing. Battery LEDs, but a thing.

Reminds me of the old book “MBO Can Work!” Um, not really, but that is out of scope for today.

Tech Push is a business practice where technological innovation is pushed from the lab into the market. If you ask the question “can Tech Push work?” to an assortment of people working in new product introduction, you will get a variety of answers. A smaller segment will extol the virtues of one or another projects that they sent to market, while others will vigorously swear up and down that the lab has never developed anything that was actually necessary. The truth, as usual, is somewhere in between.

The opposite side of Tech Push is Market Pull, when the market demands a change and tries to pry it out of the lab. Often, the laws of physics come into play – as far as I know, no one has defeated them and lived. If the state of the art in technology hasn’t progressed to what the market wants, the market is stuck waiting for technology to catch up. It’s the proverbial better mousetrap problem.

The great middle requires redefining Tech Push into two different tacks: Blind Tech Push and Informed Tech Push. Blind Tech Push is the classic version. Think of the Apple Newton. An answer to a question no one asked. AT THE TIME. In 1993, no one had any idea what to do with the thing. In 2003, when RIM released the first BlackBerry device, email had taken over as a primary communication means and the role of a personal multi-mode communication device was much more obvious. In fact, the history of devices of all types is littered with things that were released too early into the market and for that reason alone, failed. These Blind Tech Pushes are the ones people think of when they say that they view Tech Push as a failure.

The second aspect of Tech Push is Informed Tech Push. My favorite quote to illustrate this point is from Henry Ford – “if I’d asked the people what they wanted, they’d have asked for a faster horse.” In this case, the market was pulling for a faster horse, and Ford knew that that wasn’t going to happen. But he could replace the horse with something faster, more fuel efficient, and lower maintenance. The Model T (in fact, all of Ford’s work and before his, Karl Benz’) was dependent on an understanding of the market demands and production of new technology to meet them. Hr Benz, however, was actually nearly a victim of Blind Tech Push – without his wife Bertha’s intervention, the Benz Patent Motorwagen would have been a footnote of history. Bertha Benz’ willingness to reach out to the market and tap a vein of desire (go off to visit family for a quick, safe jaunt!) allowed Benz to reach the market successfully and paved the way for the rest of the auto industry.

More recent examples of Informed Tech Push include the Nespresso coffee machine (you didn’t see that coming) and the FitBit, both of which carved markets seemingly out of the air. I’m ignoring the iPod here, because the market for mobile music players already existed, and the iPod was evolutionary in meeting market demand for smaller, faster, cheaper. In the case of Nespresso, the concept of single cup brewing was not new. Neither was hermetic packaging of foods. What was missing was the market for a $4 cup of high quality coffee. Up until good coffee became desirable in the US, it was virtually impossible to move the rather expensive single cup brewers that existed. Packaging issues with small volumes of ground coffee were too expensive to overcome, and the quality of coffee brewed in existing systems was actually dismal. However, by watching the market closely and following the price points of in-cafe coffee purchases, Nestle was able to introduce the (for the market) completely novel concept of long-term storable high-quality coffee in capsules combined with a brewing mechanism that looked like art and produced a very high quality cup of coffee, all at the newly accessible price point. If this sounds like market timing, it is. Informed Tech Push is all about market timing.

In the case of FitBit, micro accelerometer technology was available and recently deployed by Nintendo in the Wii. America had gotten the hang being measured with games like DanceDanceRevolution (in gym class, no less) and GuitarHero. The staff at FitBit saw the opportunity to move this technology into the world of personal health. Rather than languishing in the fitness world where only the hardcore participated, they looked to a chronically underserved market – people sitting on their butts. Of which there are significantly more. By reading the market and understanding the goals of the larger personal health target audience, they were able to do what Nike and Garmin had failed at – capture the attention of the non-gym rat crowd.

In all cases, a careful dance with the left foot of the lab and the right foot of marketing allowed new technology to carve out a solid market and succeed.

When you think about Tech Push and Market Pull, remember that they rarely work independently. They work best when the tech is ready before the market is, but never without a clear understanding of what the market actually needs and wants.

© 2015 www.atomicalex.com

I’ve been unable to track down the origin of the phrase “a job so simple a monkey can do it”, so I’ll make do here with a few other monkey aphorisms. All to set up for a useful post, I promise.

Some years (or eons) ago, it was posited that if you gave a million monkeys each a typewriter, eventually one would hack out some Shakespeare. Actually, it’s called the infinite monkey theorem, and it says (per Wikipedia) that a monkey hitting keys at random on a typewriter keyboard for an infinite amount of time will almost surely type a given text, such as the complete works of William Shakespeare. In truth, the monkeys did not type anything useful at all, and destroyed the typewriters in the process.

A monkey wrench is a wrench that is make-do, can be arranged to work in a given situation. It turns out to have a nautical origin in name, and a horsedrawn carriage origin in function. It is actually not a pipe wrench, being that the jaws are perpendicular to the handle instead of angled as in a pipe wrench. They are also often flat instead of toothed. But they can be monkeyed around with until they work, for sure.

Throwing the monkey wrench into something is another name for sabotage.

CareerBuilder.com’s monkey advertisements reinforced the idea the monkeys are not anyone’s choice of top recruits for jobs that might provide a decent paycheck.

Monkeys are a metaphor for small, unreliable operations and operators that can go wrongly, often with spectacularly bad (ok, hilarious) results.

Let’s head back to the monkeys on the job.

During work on a large, game-changing software installation that I recently participated it, a healthy debate set up between some of the stakeholders, one group of which wanted a process that “a monkey could operate”, and one group who wanted an expert process. Middle ground was, as usual, scarce. The process in question was a stage and gate process and one of the complexities was the processing of gates – should it be automated or should it require intervention from humans skilled in the art?

This posed two rather fundamental process governance questions – how complex should the process be, and how much knowledge should be required to operate it?

The governance issue was the subject of much debate within the chartering organization, and both sides made compelling arguments. The monkey side wanted a process that could not be perverted for individual gain and that would not place additional burden on the already thin staff. The expert side wanted to know that the right decisions were being made regardless of a number, that no opportunities were being missed, and that common sense would always prevail. Both agreed that the governance of the process was critical to its success and turned back to the team for an answer.

Out of this challenge, my team, the team in charge of implementation, threw up our hands in frustration and exclaimed “if the process is so simple that it only requires monkeys to operate, then why do we need (to pay) senior managers?” We christened this “the monkey rule”.

We created a paradox in the process: the only people who could specify a monkey-enabled process were the senior managers, who then would become irrelevant in doing so. At the same time, the managers demanding as expert process were committing to the work required, because it could not be delegated to monkeys by virtue of its expert content.

Both arguments hold water – some processes are suitable for “monkey-enabling” and others will never make it out of the C-suite. The middle ground is where application of the monkey rule is required. For example, simple invoice checking for completeness is a relatively straightforward process – are all of the pieces of information there? Ok, move it on to the next step. Choosing a vendor is much more complex and not all of the useful information has a numeric value or can be converted to one. How do you rate the sole proprietor’s chances of a heart attack in the next ten months? Well, it probably starts with a phone call and might proceed to a face-to-face meeting over lunch. Things that are often handled by managers of some level with some amount of gut expertise. An expert, if you will.

In the end, the team and the chartering organization went the route of the expert process requiring the senior managers to actively participate. It’s mostly working, and it’s generating accountability that was previously unheard of in the organization. It’s also revealing some opportunities for improvement and a non-trivial number of missing experts.

Most importantly, the monkey rule served its purpose – to differentiate between the truly monkey-level tasks and those that do require a well-funded paycheck. Our managers are still being paid.

Where are you going to deploy the monkey rule?

© 2015

The bike runs now. Actually, it ran last week. The magic ingredient? The fuel tank.

I tested out my newly refreshed CDI box on a second bike, and it ran fine. The CDI refresh was done by Carmo in the Netherlands, seemingly the only place in the world doing this work. Came home and no luck. So… What was different? The only difference between the two bikes was that the other one had the tank mounted and hooked up. Something so simple……

This is important because attached to the fuel tank is a vacuum petcock, and the hoses that operate it.

While I’d been careful to close off the vacuum port on the side of the intake that opens the petcock, I hadn’t closed off the fuel feed line to the carb. So I was either running out of vacuum, or running out of vacuum. The Mikuni carb is a constant-vacuum type and requires militant fastidiousness when it comes to policing the vacuum lines. I’ve honestly never seen anything like this. Even my poor old Passat will fire and run with some vac lines open, being a modern Bosch innovation. My Rabbit would run with most of the intake missing, and it was merely K-Jet. Perfection, I tell you!

Since getting it running, I’ve also rejetted the carb, going up one size each on the main and pilot jets to #130 and #20 from #127.5 and #19. I’ve found references to this pair, and also to simply moving the pilot jet up to a #30 while keeping the stock #127.5 for the main. I expect my summer to involve a fair amount of carb tuning and experimentation – which will be great because it will put me in a much better position to handle little Japanese bikes in the future, and hopefully prepare me for a future life of Bing.

Yeah. I’m going there. Two Bings, to be exact.

I find a lot of people who don’t like guacamole, but then eat gobs of the guac I make. So, here is my dirty, secret recipe.

2-3 mostly ripe avacados
2T dehydrated chopped onions (I prefer the McCormick ones)
1.5oz lemon juice
salt to taste, ~1/2tsp

Halve and scrape out the avacados, them mash them up. Mostly ripe is key – better not quite ripe than overly ripe.

Put the dehydrated chopped onions and lemon juice in a microwave-proof cup and microwave them for about 20 seconds, twice. This will reconstitute them – puff them back up. They need to be fully puffed, so hit them again if necessary.

Mix reconstituted onion flakes into mashed avacados and mix well.

Add salt to taste.

There you go. Basic, Mexican guacamole. No fancy flavors, no tomatoes (yikes, tomatoes always turn me off), nothing. The big secret is using the lemon juice to reconstitute the onions. I don’t even remember when I first started making it this way, but it works.

I guarantee you will like it. Add whatever you want, if you are one of those TexMex types. We Mexico-Mexican types will enjoy it plain, thank you.

It’s all about the flour.

Some time ago, I grabbed a bag of Pamela’s Artisan Flour Blend, simply because it came in a big bag. I was rewarded with a flour that bakes pretty well, including things like pie crust. I modified the old American Heart Association oil crust recipe to handle the Pamela’s flour, and it bakes up fantastically.

2 cups Pamela’s Artisan Flour Blend

1 t baking powder

1/4 t salt

1/2 to 3/4 cup water

1/2 cup oil

Blend the dry ingredients. Add water to oil in a measuring cup and add to dry ingredient mix. Add water as needed to get texture right. The texture and general behaviour of the crust are uniquely GF as it is not as short as one would like, but overall, it is a serviceable crust that will not let you down. The baking powder is the secret and makes the crust flaky and fun.

Let me know how you do with it.