Henry Ford already knew about Karl Benz invention (which was by then selling hundreds of models per year and on display widely in Europe) before he set about creating his own version in 1896. The only research Ford needed to do was to ask a given person on the street: “Would you buy a cheaper automobile (they were luxury items at the time only for the rich) from Karl Benz? Yes?” Market research complete!
If we are going to quote great inventors to find inspiration, we should be quoting Karl Benz (“My first customer was a lunatic. My second had a death wish.”)
While Henry Fords contributions are legendary, I don’t think it is accurate to believe that no customer input or market research of any type was done in the conception and design of the automobile. To know the truth, we would have to ask Karl Benz.
Had the opportunity to give a workshop on the topic of Intel Edison, Node.js and the Internet of Things at O’Reilly Solid earlier today. Also had a great time attending Sandeep Mistry’s Bluetooth LE + Arduino workshop later in the day.
Thanks so much to Jeremy Foster from Microsoft for spending an hour with Intel to discuss the topic of hardware hackathons. We had a great exchange of ideas about the future of Internet of Things and the importance of DX for hardware and software developers!
This is the fastest way to get Mono onto your Intel Edison. I saw some other solutions that involve compiling Mono yourself which takes hours, do this instead to install an existing precompiled image using opkg.
This process works specifically for the Week 18 build (Yocto 2.1).
This is the talk I am planning on presenting this coming Wednesday at Future Insights, Las Vegas. I haven’t decided how much to add or remove from this deck in particular yet as it is the first test run of this thing. The focus is going to be on giving a basic overview of important concepts from the world of microcontrollers that may interest web developers who are interested in using their existing skills to work with hardware (something that is now possible due to intermediate layers such as Intel’s LibMRAA).
More likely than not I will be tweaking this thing constantly over the next week.
This is the extended version of my talk on evangelizing hardware devices at hardware hackathons. My original deck was 38 slides, this one is 109 slides. There is much I am leaving out even at 109 slides.
This is a talk series I gave last year on the topic of beacons. I had a longer version of it stretching into the hundred+ range of slides that went much farther into the technical details of Bluetooth LE (which are fascinating to me). Now that I read it again I can’t help but be disappointed at the lack of more depth on the topic of services, attributes, GATT and the entire protocol stack itself (which fill the entire BLE Developers Handbook by themselves).
Part of the preparation for this involved buying every available beacon on the market and testing it, attending two 8-hour workshops to assemble a beacon from scratch led by Morgan Redfield here at the Metrix Create Space, several meetings with local software consultants building BLE technology, writing my own beacons and GATT profiles for the Intel Edison using the Bleno and Noble Node.js libraries from Sandeep Mistry and then a field trip to the Kirkland Bluetooth SIG to meet with Vincent Gao and have him further educate me about the BLE protocol.
There simply wasn’t a good way to contain this much information and an outline of why beacons are useful into one slide deck.
Maybe I need to create a new deck entirely dedicated to doing a great job talking about BLE which is a really interesting protocol with a lot of applications. For now, we will have to be satisfied with this!