Change.

Yesterday, a software engineer, also new to the organization, roughly told me the following. The way the organisation plans projects is so different to what he is used to as a software engineer. Planning projects with a horizon of 12 or even 24 months is something he says he just cannot wrap his head around.

While this is very common and necessary in the hardware industry, it is indeed something terribly alienating software people. Software is typically treated as a living product, that takes tiny changes at a time, it is more governed towards a direction to take than having the one exact goal it has to hit by a specific date.

These very fundamental goals both mindsets follow make it difficult for change to happen. While the software engineer above obviously has a point to make, he cannot reach the people he needs to reach, because both sides are just too far apart.

At the same time, I don’t yet have an answer to the problem, but the problem itself became so obvious when this colleague told me he just doesn’t know what to say. The digital world does not yet have a common language, not to mention a common way to think about approaching problems, and unless this hurdle is taken, change will only happen slowly.

A couple of weeks later…

A few weeks into the new role, I’m busy with all the new and exciting responsibilities. Being in charge for a product is fantastic, all along with the rising technology in the Internet of Things makes it a really unique experience. Also the approach to the market broadens my horizon and there are so many things I should be writing about, but cannot find the time. Also, a new article for the TEMS Leader is in the making, which keeps me off nomorecubes.

The project is not abondoned yet, though, just like it had ups and downs over the years.

Go best practices

Peter Bourgon has some experience with go, and he shares this on his website. Go is a language developed at Google 2007 and released to the public in 2009. In first place, this is fairly unrelated, but we’re currently evaluating go as a language for an IoT project, which makes it fit the topic of this blog.

Even though go does a great job providing a newbie with an environment to get started, there are experiences you can avoid making, listening to somebody that did it before.

via: Go best practices, six years in

Goodbye Servers, Hello Devices.

It’s been a wild ride for the most time of the past 9 years. The Internet came a long way and the time I spent at Akamai Technologies since 2007 were an amazing and exciting experience. Before I came there, I was working for a security consultancy, planning deployments of hundreds of Firewalls and Intrusion-Detection Systems. Having to deal with thousands of servers was absolutely the right choice at that time and the decision didn’t turn out wrong.

During my time at the company, I worked for close to 100 brands, from all kinds of vertical like automotive, air-travel, industry, logistics, high-tech, e-commerce, media & entertainment. Mostly global corporations, all of which were well-known brands, even outside the Internet industry.

Having held 4 different roles, I helped customers on 2 continents to get their digital strategy in place, visited uncounted customers and prospects, places and offices in 10 different countries, collecting 80+ stamps and visa on my 3 new passports, while I reported to 9 different managers. Akamai likely gained 160.000 servers in the same timeframe, coming to more than 200.000 at the time of this writing.

And during the same time, Internet evolved further. When my time at Akamai began, the iPhone was about 3 months old, and became available in Germany only after I started. Since mobile Internet is broadly available,  technology and after all society really changed. This shift towards general acceptance of internet made the time with the company a wild ride.

While the normal smart phone user takes Internet availability for granted today, technology doesn’t stand still. The broad availability of connectivity  came to a point where new opportunities are starting to emerge. Having stepped up the game from hundreds of firewalls in 2003 to hundreds of thousands of servers in 2007, today house hold appliances start to become available with a “connected” options, making them more smart at the promise to make life more efficient and convenient.

The Internet of Things opens the opportunity to work with millions of Internet connected things going forward. And this forthcoming development will lead to another wild ride that I wanted to take part in right from the beginning. Therefor, I decided to join Osram’s Lightify department, starting tomorrow! I’m excited!

Revolv Smart Home Service being shut down

Remember the Revolv home automation hub? Probably not. The device was released in late 2013, and while fantastic, it largely flew under the radar before Google’s Nest division bought the company,…

Well, neither do I remember the Revolv devices, and they’re apparently out of sale since they were acquired by Nest/Google. Now that their cloud service is being shut down, they make a good point for open standards though. Without the possibility to operate them further and their manufacturer out of business, the hardware will only be good as a doorstop starting May this year.

via: TechCrunch

Zigbee for #IoT

IMG_4114.JPG
Dresden Electronic Raspbee

Zigbee is a wireless protocol for applications not requiring lots of bandwidth, e.g. home automation, lighting or sensor networks. The idea is to create so called Personal Area Networks. The specification is standardized as IEEE 802.15.4.

Dresden Electronic offers the Rasbee (Picture to the left) to get started with low budget Raspberry Pi Hardware.