Skip to main content

Upgraded to HTC One M8

I upgraded my phone from the original HTC One to the HTC One M8, which was a really clear choice because I just loved the HTC One, but unfortunately this is what mine looked like eventually:


It still works, if you want it for parts!

The M8 is exactly what I was looking for. It feels familiar, like holding a softer edged version of my One that fixes a few of a rare complaints I had, mostly around the purple-tinted sapphire lens camera. This is the first time I have replaced an Android phone without being frustrated by the performance of the previous. My HTC G1 (the first Android phone) and my LG G2 X (the supposed successor flagship) were both great phones when I got them and I still have both, in various levels of “working condition”, but they both showed signs of age as newer and newer applications ran sluggishly or refused to run at all on their dated hardware.

Android hardware skyrocketed for the first few years, but I think we’ve seen it taper off now, and that’s a good thing.

So these days I can buy a phone and just select it based on factors that don’t have much to do with the hardware, because all of it is pretty great. Its hard to buy a bad Android phone these days if you aren’t some kind of hardcode mobile gamer.

Comments

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…