Hi, I’m Daniel Peck.
I help people make the world's best systems.

Luma Has Been Acquired

Earlier this month Luma was acquired by Newell (Fortune #208). Our team will be joining First Alert, Newell’s security and safety division, to build connected products under the OneLink brand. I’m excited that all of the engineers and product managers on my team will be coming along to Newell to make sure that our fleet of Lumas continue to be well taken care of. We announced the first OneLink device that will include Luma’s software at CES last week, and I cannot wait to get it launched later this year.

Best in Design

This was the first time I was able to go to the Consumer Electronics Show, and it was an experience. Being able to see all the new products up close as they’re being announced to the world was awesome. There are some neat things out there, and the partnership conversations that happen inside of a single week are unbelievable. We’re on the right track with Luma. The connected home is exploding and people are going to need a way to secure and control their IoT devices, and their kids devices, more than ever.

Luma Launched!

Wow. Today we unveiled Luma, the project I’ve been working on for most of the last year. We’re going to completely change the way that people feel about their WiFi. We’re building on the mesh concepts that have been used in some enterprise and industrial uses, and bringing them into homes. And since our founding team all have a long history in cybersecurity they’ll be no shortage of security and control features.

Scripting APKs With Ruby

While many of my colleagues were away at Blackhat, Defcon, and Bsides Las Vegas I decided to spend a day exploring through an Android app. I became interested in this particular app due to it being the “official” app of a popular web service that included some functionality not exposed to end users through the API that they’ve provided and this annoyed me, as I was reasonably sure that some spammers on this web service were using this functionality and I was interested to see just how difficult it was to do.

Twitter, OAuth, and Client Restrictions

Over the last 24 or so hours theres been a lot of commentary on Twitter reitterating their policy that developers should not implement full twitter clients. This should have come as a suprise to no one, but seems to have kicked off a lot of ire in the dev community, nearly all of it misplaced, Yes, Twitter gained a lot in its early days from having a warm relationship with developers, and yes its a shame that they’re moving away from that stance, but at the same time they’ve made some very nice contributions back to the OSS community, Bootstrap is a godsend for people like me who haven’t invested the time to design things well.