In the high tech industry we continuously reach peak breadth of business models, only to discover a new way of monetizing stuff. Just some 5 years ago it was licensing, ads, subscriptions, monthly/yearly fees, hardware margins, accessories, paid apps (and soon in-app purchases), consulting fees, bundles, training fees, carrier subsidies and maybe a handful of other more that were indicative of the diversity of business models available for creators.
However, a lot of the variations were built on top of the existing foundations that go back to the 90s or earlier: licensing fees, services fees, content fees.
One really disruptive model was driven by social computing and data explosion, and it is the API economy. The fact that people that spent OPEX in a library or research center getting numbers or CAPEX buying research from others are now investing their money in consuming APIs and data markets across the globe is a good example of the sophistication and idealization level that the knowledge society has achieved.
With wearables, we are being presented “our numbers” in devices that have become socially acceptable enough that we can wear them. There are accurate and small sensors for time, position, distance, temperature, steps, calories, heart rate, cadence and many others. I find it realistic to think than in less than a couple years we will also have small, fashionable devices that you can attach to the sides of your head and add EKG signals.
But one important part of wearables is the interaction among wearables: an API for your self. Provided you are willing, your wearables can share and request data from others, like your current mood, cultural and personality traits, preferences for this day (food, activities, agenda) and present it to the user in an assertive way to improve relationships, productivity and effectiveness.
Your wearables can also gather environmental data that, either aggregated or in a context, can be transacted for market value. Let’s say you are the first one off a very hot subway train and you find a refreshment vendor on the street. You ask for a Coke. Your wearables can interact in fractions of a second, the vendor’s system can get this data from you, prepare an impromptu marketing campaign for the people that are coming behind you and in return give you a Coke for free.
This also has the potential to change how we do primary consumer research for marketing. No longer I need to worry about predisposition of survey takers or the inherent entropy of a sample. If your wearable knows that when you do groceries you just fly by the Doritos, not even look at them, it can sell this “measly” data to researchers (someone observing you over CCTV can get the same information, at a higher cost) This also can happen automatically so you just walk around in your day and by the end of the day you would have earned some money just by being who you are.
One important blocker for all this is payment mechanisms. I wrote about the value of Bitcoin as a payment mechanism, and I recently had an experience in Vancouver where I spent 30 minutes on the phone and spent tenths of dollars on roaming charges to talk to my bank and be able to withdraw Canadian dollars from an ATM whereas I only spent 7 minutes on a Bitcoin ATM to buy 20 CAD worth of Bitcoin (which are now worth 30 CAD, although those fluctuations are normal in BTC and can also be negative growth in some currencies and securities)
And of course… the creepy factor. Such an idea requires a granularity on policies, not only the boring tl;dr “privacy policies” (that are one of the results of ads in high-tech) but interaction policies. A new social order and interaction rules. Clinical medicine still technically considers our technology relationships as insanity. How would we change this?
I see it being either a highly personal or a highly anonymized interaction. If I’m meeting with you on a 1:1, I’m willing to share with you my mood, whether I have hard stops or pending work that I’d rather do, and how I would like to set lightning, music and climate based on my experience today. I can even share with you what my current satisfaction level with our relationship or this specific project is so we can set expectations. This can work around the cultural traits in multidiverse work environments. And you would derive some of this from non-conversational queues anyway. Otherwise, I’d rather have a Jason Bourne like, highly anonymized interaction. “Someone” walked by a market researcher and “left” this data. Nothing that couldn’t have been also obtained by observing you on CCTV or following you via mesh networks or whatever.
That said, I think it’s pretty realistic to think that within 5 years such an economy would be sailing ahead.
But if the current state of the communications infrastructure, financial system and payment mechanisms can’t enable someone to pay by tap, chip or band in fractions of a seconds, but rather in several seconds (and I still see places where Internet access is being “solved” only by cell phone towers or satellite), an API for your self and a market for derisory metrics would be too cumbersome to implement. It just wouldn’t flow.
During the past few months I worked on a book project with Packt to make it easier for people new to Debian to leverage it for Web-based applications. I’m happy to announce that Instant Debian – Build a Web Server is now available. Although it is not my first project with Packt (I’ve reviewed some nginx books before) it is the first one that I’m authoring, and I’m already working on some new projects.
I had the fortune of having a senior leader that I deeply respect from the Debian Project as my technical reviewer, and the full support of the Packt team. The motivation for the book is simple: in a world of elastic clouds, simpler NoSQL’s and explosive growth, developers, sysadmins and business leaders are less concerned about the operating system and more about their time-to-market. In this book, I use my 10-year experience with Debian to provide a simpler path to a solid Web platform.
In fact, all of my immediate writing projects are related to most of those low-hanging fruits that add incredible value to business decision makers in the broader technology conversations of todays: elasticity, information security and privacy and performance. In a way, this book answers the “why” I get from the business side when explaining technical decisions related to Debian: why use noexec in /tmp, why use codenames in sources.list for APT, why use sudo, etc. – only with a goal: reduce time-to-market.
This is a beginner’s book. If you haven’t heard about Debian before, and would like to leverage virtualization or cloud technologies to create a “template” for your Web deployment, Instant Debian – Build a Web Server will provide exactly that, while exploring the rationales and laying a solid foundation for you to continue exploring the system.
The lawyers warned me: “he’s a scared kid”
Lauro is 17 years old, just like Humberto, although shorter and decidedly of Mayan origin. He is from Guatemala and has been around for a while, now living with foster parents. They tell me that he’s stressed out because he’s being bullied at school, picked on because he has a “girly” name.
I am there to translate a follow-up interview, which goes through his previous accounts of the events leading to him leaving his country. There are some inconsistencies in his record. It is not clear whether it’s the mom who punctured his ear with a wooden stick and broke it inside the cartilage until it bled or whether the older sister was the one that used a slingshot to smash a rock in his head, repeteadly. One thing was clear: he was abused at home, and was too young to run away – so he had to endure.
Although all the older figures at home abused him, he insisted that his dad and one of his sisters were “kind” to him. By kind, he means that when they hit him, they apologized. His mom, and the other sister, just wouldn’t apologize and would take away his food for days or hit him with rocks, sticks or fists. Eventually, he takes long term jobs to stay away from home, and works with a cousin.
It’s not long until he is beaten up by a gang that was in need of a new member to carry over an execution. He escapes and runs away, spending the next month gathering money to flee. He ends up in Mexico, pays for a guide and crosses the border twice, witnessing the death of the travel companions. The vehicle that was going to pick him up never arrives and he’s picked up by law enforcement instead.
Up until today, he can’t remember when those events happened. He never went to school so it was very difficult to try to place it. I try to remind him of the Korea-Japan World Soccer Cup, or the Alvaro Colom election around 2002-2003 but he really doesn’t relate. Up until today, he still talks to his mother and asks why she beat him. “Maybe they didn’t want me in the house”, he says. He’s not scared of his family (the gangs are what scare him most) but as he grows up he’s getting frustrated for not understanding why they singled him out.
He’s still too early in the process to know what’s going to happen, but I wish someone helps him figure out the answer to that question soon.
Last week I signed up for my first United Way’s Day of Caring. Microsoft is a huge sponsor, with very high employee participation and a whole month focused on employee giving, so I was very much looking forward to it.
Although for latinos there’s something not right about caring for just “one day”, the concept is very impactful because of the scale. While I was in Ecuador, we did something similar during Christmas, which actually became one of the most important moments of the year for Ailé and me, but at 0.1% the volume of support we could do here.
After some discussion, my team chose to volunteer at the University District Youth Center, a youth shelter located in Seattle. The shelter has several programs, but it’s devoted only to the youth, and particularly the homeless youth. It’s the kind of people that you really wouldn’t want to give up. If there’s a group that can go through everything, and one that should not back away, it’s that one!
I showed up there in the morning, with work gloves as requested, and everyone started to put together the projects for the day: kitchen, back stairs, front yard, etc.
I volunteered for the bathroom – which ended up being one of the most, if not the biggest project of the day. I really didn’t know what the bathroom was used for. I just jumped in. Patrick was my partner, a Microsoft engineer specialized in Labs. He briefed me on the plan for the day: tearing the bathroom apart and rebuilding it. Heh. For someone who pilgrimages to Ikea, the idea of tearing things apart and rebuilding was daunting.
But it was one of the most rewarding experiences of the year for me!
Getting everything out of the bathroom was easy. With the right tools, I unbolted the heart out of that bathroom in just a few minutes. We had to paint and recaulk, but first we needed to derust and plaster. And before that we needed to clean. I figured I could use a face mask and some safety glasses, particularly for derusting the heater that looked out of a 1950′s movie. After derusting, I started removing the old caulk.
It’s not the first time that I volunteer “hands-on” but this time I really, REALLY didn’t know what the bathroom was used for, nor what the project actually was all about. Was the bathroom used by people with communicable diseases? Or maybe by people O/D’ing, puking all over the place? Or by drug addicts? Or maybe by people who got stabbed or shot? Had someone died in that bathroom? Or someone gone into labor there?
And then it hit me: the reason why our team chose this place is because it benefits people that you don’t want to give up. You don’t want them to back away. It’s people like me, or like you. People like us. And if we had to take showers for decades in moldy tubs where someone else peed, puked and pooed, we could take any project!
Decaulking a rotten tub is not a pleasant experience, using screwdrivers, razors and even your nails to take nasty stuff out. And my next project was to buffer the tub with a heavy duty cleaner/polisher that took all the goo and concentrated it in swirls of nastiness. And after that, caulking again. And then painting and splattering paint all over ourselves, and then power cleaning the floor, replacing the curtains, drilling new holes and bolting new stuff back.
When we realized, we were 2 hours overdue for our project. Most people had left, it was about 5 PM. As I was scrambling to find some materials, someone asked me if I knew what the bathroom was going to be used for. I said no. And then they explained that homeless youth would live in their cars, and park in the shelter to use the bathroom. They would take a shower, clean their clothes, get some food, and keep going. The bathroom was actually the only place with walls and ceiling that they had. It provided an essential service that allowed them to, for example, keep working. And something that most of us give for granted.
Just before we finish, a young couple shows up. They ask for food and someone gives them the leftover subs from our lunch. While they eat, they peek at the bathroom and comment how classy the new heater in all-black paint looks, and how clean and new everything looks. It’s all worthy then. They deserve a shiny tub, new caulking, fresh paint, a hot meal and an opportunity. I pat Patrick in the back while we wrap up – it was a good day!
A few weekends ago I had the opportunity to talk to Boy Scouts about electricity and ham radio. The local ham club created the content, which talked about basics like Ohm’s law and electromagnetic fields, and the purposes and applications of ham radio. Although at first I was assisted by some senior hams, I ended up covering the content for the rest of the afternoon. It was the first time I spoke to kids on the topic in English.
One thing I noticed was that while the content was excellent, the delivery lacked a bit of excitement and purpose. It was not clear for all Scouts whether anything in that day actually added value or not. So I started using other methods, like showing them the slides on my Surface, or doing actual IRLP demos with my handheld radio. That made a lot of difference and they engaged with tons of questions and ideas.
They particularly engaged in the conversation of the value of ham radio in emergency situations. They understood the concept of a resilient infrastructure and how hams would operate in such a situation (nets, etc.) I had joined the Redmond ARES team a few weeks before so I shared with them some of the things a RACES/ARES team could deliver in case of emergency – bingo! As a former Scout, “Be Prepared” conveys a universal sense of being one step ahead, and those small 15 minutes session with each one of the 7 groups during that day was a real opportunity to make the difference.
A couple dozens of them ended up passing their ham radio exams and earning their merit badges. And while we did the post-mortem I realized that this is the kind of events in our lives that led us to STEM career. I believe in the value of STEM although I’m not an advocate of things like shoving programming down every kid’s throat. And I also realized that the lack of excitement, and the lack of those “make the difference” experiences can influence those life decisions. 73, and be prepared!