dschinkel

package subscriptions;

import dependencies.User;
import dependencies.UserMailer;
import dependencies.UserRepository;

public class EmailSweeper {
    UserMailer mailer;
    UserRepository repository;
    String unpaidMessage = "Please renew your subscription to Ferret Fancy!";

slagyr

/**
 * Micah's Autumn setup
 */

alert('Running Autumn!');

/**
 * Window management
 */

dschinkel

My repsonse to zsup/ddd.md in which he wrote:

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

dschinkel

dschinkel

-- instead of using a 2D list or 2D array to represent a game node/board, lets use a Dict instead
-- with Dict unlike List or Array, it's much easier to insert, find, and update values
{--
    repl:
    
    make sure you have no trailing spaces after \.  Also, might need to uses spaces not tab in Sublime text
    
    import Dict
board = Dict.fromList \
    [ \

dschinkel

{--
  Below shows some code commands that if entered into elm repl shows the output received
--}

import List
empty = ' '
markerX = 'X'
markerO = 'O'

gameNode = [ [ markerX, empty, empty ], [ markerO, markerO, empty ], [ markerX, empty, empty ]]

skfarhat

/*
 * This file was generated by the Gradle 'init' task.
 *
 * This is a general purpose Gradle build.
 * Learn how to create Gradle builds at https://guides.gradle.org/creating-new-gradle-builds/
 */

plugins {
    id "com.github.samueltbrown.cucumber" version "0.9"
}

tonybaines

Configuring and Using IntelliJ IDEA for basic Elm development

Assumes an elm toolchain installed through NPM

npm install -g elm elm-test elm-format

Versions

• Elm 0.18
• IntelliJ IDEA 2017.3.4

sgdan

{--
  Iterate through a list and compare each element to all the others to decide what to keep
  
  Run at http://elm-lang.org:1234/try
--}

import Html exposing (text, div, br)
import String exposing (..)

initial = ["a", "ab", "c", "cdb", "cd"]

sgdan

{--
  Some Elm code for various ways to iterate over a map
  
  Run at http://elm-lang.org:1234/try
--}

import Html exposing (text, div, br)
import Dict exposing (Dict)
import String exposing (toUpper)