zsup

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

zsup

npm install serialport
-
> serialport@1.5.0 install /Users/zsupalla/Dropbox (Spark)/Software/Code/spark-cli/node_modules/serialport
> node-pre-gyp install --fallback-to-build

child_process: customFds option is deprecated, use stdio instead.
  CXX(target) Release/obj.target/serialport/src/serialport.o
  CXX(target) Release/obj.target/serialport/src/serialport_unix.o
../src/serialport_unix.cpp:663:20: warning: comparison of array 'device.locationId' not equal to a null pointer is always true [-Wtautological-pointer-compare]
        if (device.locationId != NULL) {

zsup

/**
 * Slay and pillage an unprotected network! ...oh, we can't do that? 
 * Ok, let's publish an event instead, to a backdrop of flashing lights and
 * clashing of metal on metal.
 */
void vanquishOpenNetwork() {
    if (!openNetworkCount || !strongest.rssi)
        return;
    RGB.control(false);     // allow the system to control the LED so we can see cloud connection progress
    makeSound();

zsup

/*
 * Connected sensor
 * Spark.publish() + PIR motion sensor = awesome
 * Thanks to Adafruit for the reference and inspiration
 */

int inputPin = D0;              // choose the input pin (for PIR sensor)
int pirState = LOW;             // we start, assuming no motion detected
int val = 0;                    // variable for reading the pin status
int calibrateTime = 10000;      // wait for the thingy to calibrate

zsup

TCPClient client;

void setup() {
    Serial.begin(9600);
    
    Spark.function("connect", connect_to_my_server);
    
    for (int pin = D0; pin <= D7; ++pin) {
        pinMode(pin, OUTPUT);
    }

zsup

TCPClient client;

void setup() {
    Serial.begin(9600);
    
    Spark.function("connect", connect_to_my_server);
    
    for (int pin = D0; pin <= D7; ++pin) {
        pinMode(pin, OUTPUT);
    }

zsup

TCPClient client;

void setup() {
    Serial.begin(9600);
    
    Spark.function("connect", connect_to_my_server);
    
    for (int pin = D0; pin <= D7; ++pin) {
        pinMode(pin, OUTPUT);
    }

zsup

/**
 ******************************************************************************
 * @file    spark_wiring_servo.h
 * @author  Zach Supalla
 * @version V1.0.0
 * @date    06-December-2013
 * @brief   Header for spark_wiring_servo.h module
 ******************************************************************************
  Copyright (c) 2013 Spark Labs, Inc.  All rights reserved.
  Copyright (c) 2010 LeafLabs, LLC.

zsup

int motion = 0;
int buzzer = 1;

void setup() {
  pinMode(motion, INPUT);
  pinMode(buzzer, OUTPUT);
  Spark.variable(motion);
  Spark.function(buzz);
}

zsup

test