dschinkel

module Scorer exposing (..)

import Array exposing (fromList, get, map, set)
import List exposing (foldl, map)
import Maybe exposing (withDefault)


markerX : Char
markerX =
    'X'

dschinkel

module Scorer exposing (..)

import Array exposing (fromList, get, map, set, toList)
import List exposing (all, foldl, map)
import Maybe exposing (withDefault)


markerX : Char
markerX =
    'X'

dschinkel

{-- 
    Overview
     - this only works with List or Array of Char.  I'll change it to be generic soon.
     - Example list sent in: [['X',' ',' '],['O','O',' '],['X',' ',' ']] : List (List Char)
     - After Conversion it's type of Array.Array (Array.Array Char)
    
    
    
##### If you'd like to try this out in elm repl, run the following:#####

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

        var args = [].slice.call(arguments, 0);

dschinkel

// makes Part2 test pass & removed what we don't need

import * as React from "react";
import { RouteComponentProps } from "react-router";
import WithEditProjectQuestions from "containers/recruiter/WithEditProjectQuestions";
import ProjectQuestionsForm from "components/recruiter/ProjectQuestionsForm";

export class EditProjectQuestions extends React.Component {
  public render() {
    // we're passing it a dummy function that does nothing to satisfy the ProjectQuestionsForm contract just to get us by

dschinkel

dschinkel

// source: https://github.com/dschinkel/we-do-tdd/commit/9e58e254b2c4fc70ebf54ff475079facd2c61d71

import {Component,Store} from 'reactivate';
import CompanyHeader from '../../client/components/companyDetail/CompanyHeader';
import {expect} from 'chai';
import {reactUtil} from '../helper';
const store = Store();
const {renderIntoDocument, find} = reactUtil;

 describe('Company Detail - Header', () => {

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

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!";