Unnamed Project

A Programming Library for IoT

This Guy?

This Talk

A little bit technical

A little bit rock & roll

In the beginning

Weird Ideas

but, one thing at a time...

First Lines of Code

gpio mode 0 out
gpio write 0 1
gpio write 0 0

I threw up in my mouth a little bit when I saw this code.

Programming the Obvious

Code should be...

descriptive
portable
separation of concerns

When we write code, it should be descriptive of what the code is trying to accomplish. That's why we give variables and methods names which describe what they are and what they do. You should be able to read a program and get some idea of what it does. That last bit of code with the GPIO stuff doesn't tell you what it does really, it tells you the actions it should take, not the effect it is going to have. It also isn't portable. We can't take that code and run it on multiple devices because we can't be guaranteed that both devices would have the same thing plugged into port 0, or that anything would be on port 0. Separations of concerns, not sure if I used the right term there, but basically, your software developer shouldn't be so closely tied to a hardware platform that the intricacies of the hard dictates the software, I think their should be a middle layer that abstracts as much of that out as possible.

Let's try this...

$$('led').on();
$$('led').off();
$$('temperature').get();
$$('temperature').live(3000);

What makes this possible

{"name":"descriptive_name", "abilities":[
{"type":"led","pin":16, "interface":"gpio","color":"red"},
{"type":"led","pin":15,"interface":"gpio","color":"green"},
{"type":"led","pin":18,"interface":"gpio","color":"blue"},
{"type":"temperature","pin":"28-000004acb882", "interface":"w1"}]}

Really? Javascript?

Every Device is a server

does the 'I' really mean Internet
device-to-device communication
do me a favour

Imaginary World Example

I cook alot

Wrapping-up

Thank You

pete@kitchon.com