Yeah... Ordered an iPhone 7

It took only two weeks since writing the letter to myself trying to stop myself switching away from Android. Guess what, it didn't work. Last night I ordered a Jet Black iPhone 7 128GB.

So what happened? 

It was all triggered by my twins being born. Congrats, yes, thanks. They're healthy, great, and tiring. I spend a fair amount of time with a son in one arm, and a phone in the other. As I wrote in my previous post, I currently own a Nexus 6p, which is a 5.7", also known as: pretty darn big, heavy and not that comfortable to operate with one hand. That's problem number one, number two is the camera. Practically all pictures taken off my first since were iPhone pictures, and they're pretty decent. Not pro level, but good, made instantly, never had a complaint. The Nexus 6p has a reasonable camera, but not as nice as my old iPhone 6. Meeting problem, it sometimes takes 2 seconds to snap the picture which can mean it missed the moment.

Case in point:

Here's my oldest son blowing out the candles during his third birthday last week:

Nice timing Nexus...

Nice timing Nexus...

Yeah, that's a shame. Don't remember having such issues with an iPhone. You're phone's camera is a big deal, especially if you have kids growing up. And I do... An army of them.

So, size, weight and camera kicked off the doubts once more. The way my brains work, this then results in revaluation of just about every pro and con, and guess what, things tipped over to the iPhone side again.

So I'm eagerly awaiting my iPhone 7. See you again Android, perhaps in another couple of years... 

Micro Services on the Client?

The Micro Service Architecture is all about splitting up your application's (or group of applications') functionality into separate services that communicate with each other in some standardized way, e.g. JSON over HTTP. While this approach is rapidly gaining adoption on the back-end, I wonder: is there also a case to be made for micro services on the client? Is there a case to be made to apply this pattern in browser-based applications and native desktop applications?

Read More

Note to self: Things to Consider When Switching Back from Android to iOS

Dear Zef,

We both know you will read this note one day — perhaps sooner than later. You being you, you will decide once more that Apple is much cooler than Google, and it's time to go all-in on Apple products again. More specifically it's time to buy and iPhone once more and get rid of your current Android phone (Nexus 6P at the time of this writing). I'm writing this letter to you now, so you'll remember what you'll be giving up on when this day will come. Just in case I will write and publish this before the September 7th Apple iPhone event.

Read More

"Resilience Thinking" in the Micro-Service Architecture

Micro services — the idea of splitting up your “monolith” software architecture into dozens, even hundreds of small services — pops up all over the place these days. At Egnyte we are also regularly discussing this topic, and investigating how to move towards this model more and more.

Resilience is a hot topic in this area. Resilience is all about gracefully handling failures — which will inevitably happen at increasing rates as your system becomes more distributed (a natural consequence of the micro-service architecture).

Read More

Brilliant, But Stuck

You're one of them — one of those 10x developers. The cream of the crop. You know how to build things, and build them well. Technical challenges don't scare you — you got a track record of getting them done. People like working with you, because they know they will learn from you. In fact, people join whichever company you work for, just to be able to work with you. Recruitment loves you.

Yet, not all is perfect.

Read More