Play To Your Strengths (The Leader’s Serenity Prayer)

Originally published on forbes.com.

The role of stretching is often overlooked in the process of growth.

When you’re strength training and you lift weights, it stresses your muscles, which triggers the growth process. But if you neglect to stretch afterward, your muscles shorten and become tight, which leads to them becoming weaker, not stronger, and causes damage to your joints and muscles.

When leading, it is inevitable that your teams will be stressed at one point or another. Leveraging your team through those stresses, and stretching properly between stresses, is as important to your team’s success as stressing your muscles and stretching them are in strength training.

There is a lot of literature about how to move away from leading while you’re perpetually under stress. I’m not going to talk about that here. I’d like to discuss how to get the most out of your team when you are functioning under stress and how to stretch in between stresses.

When I’m in stretch mode, that’s when I explore — be it a new technology or way of running things — and let my team explore. To be completely honest, this is what I do with most of my evenings and weekends as well. Exploring doesn’t mean wasting time. Rather, it means giving people the opportunity to get out of their comfort zones, which, as they say, is where all the good stuff happens.

By stretching, I was able to implement version control with our codebase (you have to start somewhere). I was able to build private development environments instead of having our developers share a development server. I updated our servers to run better, faster and more secure infrastructure. As a team, we’ve trained in and implemented all the best parts of ES6 and PHP7+. We’ve explored better project management processes. We’ve waged a battle on spaghetti code, implemented unit testing and added new frameworks like ReactJS.

If we had allowed ourselves to be pushed into perpetual stress, we wouldn’t have any of this, and our company would be worse off for it.

When you can stretch, that is the time to for encouraging growth, exploring new open source libraries, and making sure all your foundations are solid. Does everyone on your team know how classes work in ES6? This is what you can look forward to when you start your campaign to move away from living in a state where you’re perpetually chasing the urgent issues.

Then there’s the stress…

When you’re in stress mode, your team will grow, but your team needs to perform at its highest levels and play to its strengths. All hands on deck.

What do I mean by that?

If one member of your team is much better at CSS — even if you need all your team members to be proficient in CSS — now is the time to rely on that team member specifically for all your CSS needs. Now is not the time to cultivate weak or latent skills.

During your stressful periods, you’ll see that some of your team members grow into roles. But just as you don’t try a new powerlifting stance when you’re competing to break a record at the gym, you shouldn’t be seeking out hidden talents when you’re in stress mode at work. If these talents reveal themselves, so be it — otherwise, tap from the existing wells.

Open Source: To Use Or Not To Use (And How To Choose)

Originally published on forbes.com.

You’d like to use open source software, but you’re not sure what criteria you should use when deciding whether to rely on it for a specific project or not.

I have a long, complicated history with open source software. I use open source libraries every day in my work, and I’ve developed several criteria for evaluating projects.

I got my professional start in tech as the technical co-founder of a news startup. My co-founder had chosen to use WordPress. I volunteered to maintain the tech since I had a strong background in HTML and high school-level understanding of Pascal and figured that would be enough.

WordPress, as it is for many, was my gateway drug into tech — and open source. When I had any questions, I quickly found solutions from the robust and supportive WordPress community.

That’s the ideal open source — a ubiquitous platform with a helpful and supportive community.

Several years later, at another startup, I got entangled with a different open source community. Having used WordPress during my initial experience with open source, I trusted open source. I was tasked with managing an online community, and I chose this open source solution without fully understanding what had made the WordPress choice so successful with my previous endeavor.

Customizations were expensive, if they were even possible. Updates didn’t update smoothly, nor were they timely. The community using and supporting the software was very small at the time and not very helpful.

That’s where open source can go wrong — a project that’s not properly maintained or supported with an unhelpful community. Even when open source goes wrong, you are not necessarily going to do better with a proprietary solution.

Many development firms try to sell their proprietary systems so they can lock in clients. Every new feature the client needs costs an additional work fee. That’s clearly in the interest of the development firm — not the client.

If you opt out of working with them for future developments, then you are responsible for developing the core codebase. You have to constantly monitor the core codebase for security risks because you have purchased a proprietary system. You are on your own.

With open source systems, you get all the infrastructure for your site from the community. The same goes for Flask, Drupal or ExpressJS — all projects I’ve leveraged at one time or another. User management, community plugins, security and data structures are all taken care of, leaving you to focus on the features your company needs.

How To Vet An Open Source Project

Knowing which open source projects you can rely on is an acquired skill. If you choose wrong, it will cost you. I’ve thought a lot about this topic over the years and have come up with the following criteria for evaluating a project:

1. Who is developing and maintaining the project?

Does the company have a good track record for keeping open source projects going? Sometimes a company will open up a tool it uses in-house. This is a good sign that it is likely to keep developing it further. Other companies don’t want to actually kill projects, so they offload them to an open source platform and cease development. You can adopt such a project, but just assume that its maintenance will most likely be entirely on you.

For example, Facebook has a fairly good track record for supporting its open source projects. It has a department dedicated to open source tools. I can’t vouch for its non-open source services, because each one is a different case. But I happily incorporate projects like ReactJS into my site, knowing that it will be maintained.

2. How popular is the project?

The more people rely on the project, the more likely it is to be maintained — if not by the original development team, then by others who need it and take it over.

The popularity of a platform is an argument that can be used against incorporating some open source projects. WordPress powers roughly 28% of the internet; some see that as a security risk. But any systems administrator worth their salt knows how to mask and lock down WordPress. Not to mention, because of its ubiquity, security issues in WordPress are detected and patched quickly. In contrast, if you run a stagnant system, do you really know what security skeletons are hiding in there?

3. How often is it updated?

When a project stops attracting regular contributors, it’s a strong indication that that project is going to die. Similarly, if there are a lot of open issues on their GitHub repository, it means that the team behind the project is neither active nor responsive to the needs of the community.

4. What does the codebase look like?

Code that is clean and well-thought-out is a good indication that professionals are behind the project. Even if it was left to die, it might be a project a company would happily take in-house and maintain further for its needs.

If you are debating whether you can incorporate a project into your codebase, remember the following: A good open source project is maintained by a core group of people who rely upon it. It will likely be used by a lot of people, and it will be updated often. Finally, a good project, open source or not, will have clean code that is well-maintained. If you do incorporate it into your codebase, you will benefit from the expertise of the entire community using that project.

On Assholes and Leaders

“If you run into an asshole in the morning, you ran into an asshole. If you run into assholes all day, you’re the asshole.”

― Raylan Givens, Justified

The asshole doesn’t see that he is one — that is the true nature of being an asshole. Ultimately being one is truly just a manifestation of selfishness. If you don’t care how your actions affect the people around you, the people around you will see you as an asshole.

If the actions of everyone around you are pissing you off, you’re only thinking of yourself. When we start life, we can only think of our own needs. We’re not capable of doing otherwise. As we grow older, our ability to think of the needs of others grows. That’s why kids on the playground can be so brutal. Part of growing up is learning to see past our own needs.

Assholes are the people who never truly grow up.

Caring about how your actions affect the people around you does not make you a pansy, or weak. Sometimes you might know that what you need to do will have adverse effects on people. When that happens, the only way to avoid being an asshole is if you first consider the effects of your actions. At that point, depending on your considerations you may still be an asshole, but you might be a leader.

Therein lies the paradox. To not inadvertently be an asshole, you have to be self-aware enough to know that what you are doing is affecting others adversely. Assholes are insensitive and therefore detestable.

“The measure of a leader is not the number of people who serve him but the number of people he serves.”

– John C. Maxwell

Traditional leadership, as we think of it, is when you’re the boss. You command, and your minions listen. But the average serf doesn’t do great work. They have no reason to do great work. Why should they?

Commanding and expecting it will get done, threatening, pressuring, having no sense of the needs of the person you are asking from — all these are classic actions of an asshole.

The antithesis of being an asshole is being a leader.

A good leader knows that the buck stops with them; that they are ultimately responsible for what needs to get done. From raising the next round, to making sure the servers are running, to sweeping the floor — it is all up to them.

A good leader has to be aware of the state of the entire company. A good leader looks outward to see how they can serve better. Good leaders learn to look past themselves, past the people immediately around them, and to see as much of the big picture as they can.

An asshole stands in front of a subway door, oblivious to the people who can’t get on.

If you want to rise above being an asshole and become more of a leader, take time to think about the people around you, the people you interact with, and care a little bit. If you do this you’ll start to see people turning to you to get things done.

A Weekly Book Project

I’ve taken a step back from following all the podcasts I’d been listening to, for obvious reasons. I have the 3 I listen to, to keep up with the news… And that’s it. At a certain point, reading more news stories will only make me less effective.

In 2015 I set out to read a book a week, and ended up reading 83 books. In order to keep my sanity, I plan to attempt this project again this year.

I’ve already started, and you can follow my progress.

One thing I’d like to do differently this time around, as you might have noticed, is I want to absorb more of what I read. So I started writing a few paragraphs about each book, a takeaway, once I’m done.

I also wouldn’t mind company on this journey. I love discussing ideas, and what I’ve read and am thinking about. You can see from my 2015 list and my most recent additions that it’s an eclectic collection. So if you’d like to suggest a book you’d like to discuss, or know what I’m reading before I’ve finished, let me know and I’d be more than happy to discuss.

For the curious, the secret to accomplishing this, is to plan. I always have several books in my queue that I’m in the middle of, and a few shorter books (Shakespeare plays, etc.) that I can finish in a day or so in case the end of the week surprises me. That way I’m always ready to finish a book each week.

Technological Evolution, Microsoft vs Apple

I’m writing this from my iPad Pro with the Smart Keyboard. It’s a beautiful experience. It’s also a natural evolution of where technology has been going.

This past week Microsoft has displayed that it understands this. Apple has not.

Writing here is not a perfect experience: I still think multitasking on iOS could benefit by some improvements. But I enjoy being able to reach up, touch the screen and do things. When I switch back to my MacBook Pro, I’ll invariably find myself reaching up to the screen to manipulate something.

There have been several innovations along the path of technological evolution that have sparked exponential adoption and further innovation.

“Evolutionary processes creates a capability and uses that capability to bring on the next stage.”

– Ray Kurzweil, TED (Minute 5:21)

There is a rabbinical tradition that on the sixth day, before sundown, God created the first pair of tongs–giving the world’s first blacksmith the necessary tool with which to make more. But it’s more likely that man iterated on his tools, building up to some sort of tong. This is how technology develops.

Similarly, with interfaces, we build off previous iterations of interfaces towards more efficient tools. Punch cards led to keyboards; command line interfaces led to GUIs; mice led to touchscreen.

“Progress of technical science is characterized by the fact: first, that more and more energy is utilized for human purposes, and secondly, that the transformation of the raw energies into useful forms of energy is attended by ever-increasing efficiency.”

– William Ostwald, Efficiency

Our tools progress towards being more efficient. That is what defines technological progress. Whatever issues that are lacking in touch interface are not because of it being less ideal an interface than command line (no, VIM is not better)–it is because of the implementation of the tool. Newtons were horrific, but iPhones are a beautiful experience.

Another concept Kurzweil talks about is exponential growth. Not only did RNA lead to the Cambrian period, it led to the Cambrian explosion. Not only that, but as far as we know, all cellular life has DNA, an evolutionary step past RNA. When a biological process is surpassed, it tends to be left behind. This is also true of technology. Our trains are not steam-powered anymore, nor do we use vacuum tubes in our computers.

iOS was originally forked off of OSX. It was done so because OSX was a solid platform, but somewhat over-bloated for the limited resources of the original iPhones. There were speculations about if/when they would be re-merged.

Microsoft has already done so with Windows. While I’m not a big Windows fan, I will admit that that was the right play and the proof of that is this past week’s tech announcements from both companies.

I’ve been an Apple fanboy for a very long time, it pains me to say this.

It is doubtful whether a contextual touchscreen on a keyboard provides added efficiency in your workflow–if it does, it is linear. This past year Apple has not demonstrated exponential growth, their iterations have been little more than linear, or catching up to parallel technologies. Waterproofing a watch, putting an accelerometer into a TV remote, adding zoom to a camera. These all add to the experience, but other tech is surpassing these technologies.

Microsoft, on the other hand, has been developing entirely new interfaces. Kinect tracks your movement, creating a whole new way to interact with games. Hololense will bring AR to a place where it can be useful.

The Surface Studio looks beautiful. They are embracing touch interface as the next step in the evolution of interfaces. It’s more than a linear step along the way–I don’t know if it’s exponential, but it shames a slightly augmented keyboard. It combines the power of a desktop with the interactive interface of a tablet. The result looks like a better experience than the sum of its parts. This is technological progress.

Cover image 

Blood Toil Tears And Sweat

On May 10th 1940 Germany invaded Belgium, France, Luxembourg and the Netherlands; Winston Churchill became Prime Minister of the United Kingdom upon the resignation of Neville Chamberlain. The United Kingdom invaded Iceland, and Belgium declared a state of emergency.

As the new prime minister, Churchill was called on to form a wartime coalition government. On May 13, 1940 Winston Churchill gave his First Speech as Prime Minister to the House of Commons.

Why this speech?

World War II changed the face of the world. There were two possible paths ahead. One side represented division, discrimination and destruction in the name of making one nation “great” among the rest of the world. The other path, was fighting for it’s existence and against all the evils that their opponents stood for.

Churchill is one of the great orators of the 20th century and this speech captures so succinctly that moment in history… with parallels to today that are not lost on me.

We Choose To Go To The Moon

On September 12 1962 John F. Kennedy gave a speech at Rice University where he declared his plan to send man to the moon within the decade.

I chose this as the first speech I would practice because it serves as a constant source of inspiration to me. This speech gives me chills each time I hear or read it, and it is the prime example, for me, of the power of speeches.

Why this speech?

Not only did President Kennedy cover so many of the important accomplishments of humanity, but he was able to put them into perspective.

50 years is hard enough to comprehend, but it is within a lifespan. He could have said “Less than 100 years ago we developed penicillin.” Instead, he said “less than a week ago.” A week in the context of 50 years is far more powerful than 100 years in context of 50,000 years. Most people can remember what they had for breakfast a week ago; while, I don’t know anyone who remembers first hand anything that happened 100 years ago.

Putting a man on the moon might have seemed impossible then, but when looking back over humanity’s accomplishments and seeing those accomplishments in the perspective of the exponential progression it took, it almost feels achievable.

That leads into the second piece I read from the speech, the why.

Reading this speech makes me want to be better, it plays chords on my soul reviving the sense of adventure I felt as a child when first discovering new things, new stories in books, hearing about new places and wanting to go there.

This speech speaks directly to the greater spirit of man, the transcendent urge to be, to conquer, and it channels that great desire towards one of the greatest achievements man could ever think of doing at that time. A challenge we haven’t achieved since.

And this speech has the power that it could do it. It could inspire man to reach that goal. and It did.

“For if Achillês is left alone to fight…” – Zeus Cloudgatherer

The literature of humanity that has stayed with us taps into the deepest part of how we perceive our existence. The stories that our ancestors have crafted and passed down to us resonated with them. The stories that made it down to us, made it through the filter of time because those stories said something important to each link the the chain from then until now.

Pondering this I recently read the Iliad for the first time, and then I read it again. One way that it resonated, surprised me.

Growing up I was never one of the athletic kids, but several of my close friends were, and thus I learned to play. There’s a unique excitement that engrosses you when you are participating in a game. I can still remember viscerally how deeply I wanted to win — especially during tournaments, and how it felt that all the powers of nature were conspiring for each event that happened during that game.

“You should pray to the everlasting gods yourself. You are no mere man.” Apollo to Aineias

– Iliad, book XX

Feeling this — while playing an intense game — it is 100% natural to pray to god, to request a favorable outcome to your game. Looking back 20 years later, or even a single month, most of those circumstances seem a silly catalyst for requesting divine intervention. But when you’re in the moment, heaven and earth should move for you to get that touchdown, or home run.

This affects spectating participants as it does the players. As a Red Sox fan (since before 2004) it’s clear to me that divine intervention is involved in these great games…

Achillês now cast his spear, and struck on the outermost ring, where the metal was thinnest and the hide thinnest behind. The Pelian lancewood ran through with a ringing sound. Aineias had crouched down holding up the shield; so the shaft passed over his back and stuck in the ground, still fast in the shield with the two layers torn apart. But he had escaped: he stood up dizzy and shaken when he saw that shaft sticking at his elbow. Achillês then drew sword and leaped at him with a shout. Aineias lifted a great big stone in his hand such as two men could not carry, as men go now, but he managed it easily alone. And now Aineias would have crashed down that stone on his helmet, or on that shield which had saved him before, and Peleidês would have chased and killed him with that sword; but Poseidon Earthshaker thought his time was come…

So Poseidon left them, and passed through the battle to the place where Aineias and Achillês were face to face. He drew a mist over the eyes of Achillês; he pulled out the spear from the shield of Aineias and laid it before the other’s feet, whisked up Aineias off the ground and hurled him through the air. Over the ranks of fighting men Aineias flew from the god’s hand, over the lines of horses, and alighted on the outskirts of battle where the Cauconians were getting ready for action.

– Iliad, book XX

This is exactly how I felt while engrossed in my games, praying for me or my team to win.

When you’re watching a Super Bowl and a long toss is sent, you can feel the entire stadium willing that ball to do one thing or another. There is little doubt in my mind that people are hoping for Great Earthshaker Poseidon, or whichever surrogate they pray to, to whisk the ball through the air into the hands of the right mythical hero to make that touchdown.

I got chills reading this next piece; having studied religious liturgy for a good part of my life, I hear clear echoes of my prayers from the Days of Awe.

But when the fourth time they drew near the two fountains, see now, the Father laid out his golden scales and placed in them two fates of death, one for Achillês and one for Hector. He grasped the balance and lifted it: Hector’s doom sank down, sank down to Hadês, and Apollo left him.

At that moment Athena was by the side of Achillês, and she said in plain words:

“Now you and I will win, my splendid Achillês! Now I hope we shall bring great glory to our camp before the Achaian nation, by destroying Hector, for all his insatiable courage. Now there is no chance that he can escape, not if Apollo Shootafar should fume and fret and roll over and over on the ground before Zeus Almighty! Rest and take breath, and I will go and persuade the man to stand up to you.”

– Iliad, book XXII

The imagery of scales is universal. This expression of scales balancing the fate of the two heroes of the Iliad echoes through every confrontation I witnessed, and every request I have ever made in any prayer.

When reading through the Iliad there were points where I could not fathom why this piece was so important, especially when lineage went on for pages. After finishing reading the work I understand more why we must study and cherish the great treasures passed down to us from ages past.

Image credit: Pietro da Cortona

The Privacy / Convenience Polarity is a Myth

There is a myth, that if you want to have privacy, it will be at the expense of convenience; and if you want convenience, it will be at the expense of privacy.

They say that is the way things have to be, but it really doesn’t have to be this way.

Open up your iPhone and go to settings, then open up Privacy > Location Services and see how many apps are using your location “always”. See how many of those apps were just defaulted to “always” and how many require to always have your location. Then ask yourself which of those apps actually NEED to ALWAY have your location?

Here is how this is justified. Let’s use a location recommendation service, like Foursquare or Yelp, as an example.

The pitch is, this location recommendation app gives you value by finding all the great places your friends like.

However, In order for you to benefit from that data you need to enable the location services on your phone. The app then tracks where you, as well as your friends, go. It records all the places you “check in” to. Based on where your friends “check in” and based on the ratings other people who frequent that venue give, you can get the best recommendations everywhere you go.

This app can then sells to advertisers the data it collects. This is the app’s business model. The app sees that you frequent a specific gym. It can then go to the gym across the street and sell them the opportunity to advertise to you, as you go to their competitor. That’s how they pay the bills.

People will tell you that this is the way it NEEDS to be if you want the convenience of getting the best recommendations. 

The problem with this approach is that the more independent services that manage your sensitive data, the more you are open to vulnerabilities. Do you know what systems each individual place that handles your data uses to protect that data?

Why should you care?

In many situations, like what my favorite pizza order is, I am less susceptible to being hurt by a breach of privacy. But that’s not the case with ALL personal data.

What happens when a company that collects your location data goes out of business or is acquired? Any agreement it might have had with you vis-a-vis privacy is can be ignored. When Internet companies go out of business, their data is often the only valuable asset they have left.

Or from the comments of the CDT before the FCC.

Consumers’ dissatisfaction is likely to be heightened when the advertisements arrive from third parties with whom the consumer has not established any relationship. Without awareness of how their location information is being used and who has access to it, consumers will feel as though there is omnipresent surveillance of their activities by companies they do not know. The invasiveness of such advertising increases when the volume and frequency of messages is also outside of their control.

The real issue is that Apple, Android, and Microsoft, the gatekeepers to the location services on our devices, haven’t built their systems properly.

There is a concept in computer science called Data Encapsulation.

Data encapsulation, also known as data hiding, is the mechanism whereby the implementation details of a class are kept hidden from the user. The user can only perform a restricted set of operations on the hidden members of the class by executing special functions commonly called methods. – Wikipedia

(Note: “User” here refers to the classes or methods manipulating the data, i.e. the user of the data.)

This actually is a best practice of software architecture. When your code knows too much about the other components that means that those sections of code are probably dependent upon that knowledge, which means that your code is inflexible, fragile, rigid, and more likely to break.

Let me show you another way location, and other sensitive data could be designed.

Stripe is a payment processor. It’s my favorite to use, because they clearly care about both security and ease of implementation. I.e. they care about the people using their service.

One of the interesting aspects of how they implement their system is that if you use them, your server never has any idea what the purchaser’s credit card number is.

This is a really good thing for developers. If your system handles credit cards you have to make sure your system is PCI compliant otherwise you’re opening yourself up to all sorts of legal fun. Making your system PCI compliant is not easy. Which means that implementing e-commerce can be a challenge… Unless you work with a company like Stripe that already solved that problem for you.

How does Stripe make sure that your server never touches a credit card number?

When you submit a form, the fields in the form have to be named. If the fields are not named the browser simply will not pass the data in those fields to the server. It can’t, because it doesn’t know how to label that data.

Stripe takes advantage of this “feature” and hijacks the submit button. When a purchaser on your site puts in their credit card information Stripe collects all the data in the form securely sends it to their servers and sends back a token and places that token in a proper form field on your site.

Once the data is submitted, the browser doesn’t send the credit card data, because it isn’t named, but it does sent over the token that Stripe created for this interaction.

As a developer you can look up information about that transaction, even about the purchaser. But you can’t have the full credit card number. The purchaser is protected, because there is an impartial third party who is responsible for keeping the credit card information secure. And the site is protected as it does not have to hold sensitive data. But can have all the benefits as if it did save the credit card number. The site has usage statistics, purchase statistics, all the bells and whistles.

This is the beauty of data encapsulation.

Location data should work this way too.

For starters. There should not be an option for services to have location data always on, by default. I’m saying this as a developer fascinated by location-centric apps. Location data should be as protected as credit card information. There is no excuse for that.

The creators of the operating systems should be the gatekeepers of our location data. If they were serious about security this should be the next front line. They already collect and record the data if it is enabled, they should be the only ones.

Apple Pay, Google Wallet, these are all big targets because they have huge revenue potential. They also make things safer. A pay-per-use location API would be too (there are many affordable ways to make pay-per-use services, see Mailchimp.)

There should be a PCI SCC equivalence for location data. There should be a council looking out for your privacy and making sure that others hold to those standards.

This probably won’t happen, people don’t seem to care enough.

But don’t listen when people tell you it has to work this way.

Image Credit: Dizzy Fripper

Say: “Alexa, turn on the living room lights”

Say it. No, really. Say it aloud.

You might feel silly the first time. But the second time it feels great. Especially because Amazon Echo actually works.

We were sold the hype of Siri. Sadly, Siri just doesn’t have the knowledge to understand conversational requests, nor the power to fulfill them. The Washington Post scooped the imminent release of Viv this past week, Siri’s younger sibling that hopefully will work.

But that power already exists with the Echo. Whether Viv will be able to leapfrog Alexa and takes over the market is speculation at this point. These musings are about virtual assistants finally coming to age.

First, what makes Amazon Echo so powerful is the combination of:

  • Hearing you from everywhere; you don’t have to shout “hey Siri” three times.
  • The ability to understand natural language; you can speak naturally. You don’t have to learn boolean logic, like we did to become proficient with Google.
  • Alexa has skills. There is a phenomenal API that Amazon is actively cultivating with developers at hackathons, and funding. Each week I get an email with updates about how Alexa has learned something new.

<aside>A caveat on the first point. That’s somewhat scary, how Alexa can hear everything. A friend of mine set up a network filter to see what is actually transmitted back to the mothership. He said that the Echo only sends small packets of data when you say the wake word “Alexa”. Amazon confirms this on their FAQs, also they confirm that you can delete the history of your searches, and it will actually be deleted from their servers.</aside>

Previously when I read about smart home devices it sounded quaint, a hobby to try sometime; like drones. But try saying “Alexa, turn on the living room lights” and imagine your living room lights turning on.

It’s not about being lazy. You can turn your whole home off in one go. If you have multiple lamps in a room, like we do, you can turn them all on or off at will — with a phrase.

But virtual assistants are about a whole lot more than living room lights.

Technology has created a lot of opportunities by making our lives easier. When I was younger and complained about typing a paper for school my mother told me about how she wasn’t allowed more than 3 typos on a page. If she made more than 3 typos on a page, she would have to resubmit the whole paper.

How much spontaneous creativity do you think happened in those papers when you had to retype entire pages just to move a paragraph around? That’s the power of word processors, of technology.

Factories have been implementing robots to do menial, and dangerous, tasks. This is paralleled in humanity’s move to an agrarian based society; which, freed up enough time for humanity to focus on creating culture and technology.

Virtual assistants are finally coming of age and I’m excited to see where they go from here.