mFingers

Story Mapping

Overview

Software is never “done”. Instead, we continually improve it over time. We can mark how the software changes over time in terms of “Releases”. Simply put, a release is nothing more than a set of expected functionality - work completed within a named period of time. Note that releases are separate from deployments. We may deploy dozens, or even hundreds, of times before a release is over. A release simply marks the point in time when we have completed that set of expected functionality.

Organizing Work

Work is often found in a backlog, but the backlog does nothing to help visualize what the system does. I propose creating a structure to the backlog, so that it describes the system. This idea is a story map. I strongly suggest reading Jeff Patton’s introduction of the Story Map. The idea is that work is categorized along the User Journey: ![image](https://user-images.githubusercontent.com/1946506/140441937-1370ec2

mFingers

Keybase proof

I hereby claim:

• I am mfingers on github.
• I am mfingers (https://keybase.io/mfingers) on keybase.
• I have a public key ASB7MnxpVXw5XriS6C4m-73GwPWhXrCL_PvrhkLX57F7ogo

To claim this, I am signing this object:

mFingers

diff --git a/app/assets/javascripts/helpers/pubsub_helper.js.coffee b/app/assets/javascripts/helpers/pubsub_helper.js.coffee
index c3f8482a5a..97529051b8 100644
--- a/app/assets/javascripts/helpers/pubsub_helper.js.coffee
+++ b/app/assets/javascripts/helpers/pubsub_helper.js.coffee
@@ -82,7 +82,8 @@ class App.Helpers.PubSub extends Backbone.View
     $session_row.remove()
 
   updateTestCount: (method) ->
-    page_title = $('title').text()
+    $title = $('head title')

mFingers

module.exports = function (config) {
    config.set({
        frameworks: ['jspm', 'jasmine-ajax', 'jasmine'],

        reporters: ['spec'],

        files: [
            'node_modules/babel-polyfill/dist/polyfill.js'
        ],

mFingers

This is what I was thinking along the lines of testing the "internals" of SQLProvider. queryTemplate acts as a stub that we can use to create different query conditions.

However, in order to make this work, I had to expose a number of types and methods by removing the internal access modifier. I'm not sure how that feels for you. I don't understand the architecture well enough yet to make any kind of opinion.

But that stuff aside, would something like this be desirable?

module ``Generate FROM clause``
    open NUnit.Framework
 open FSharp.Data.Sql.Common

mFingers

using System;
using System.Collections.Generic;
using System.Linq;

namespace CreditCardValidator {
    public class CreditCard {
        private string ccNumber;

        private const int minThreshold = 13;
        private const int maxThreshold = 16;