yattom

研修、トレーニング、ワークショップ 1回(1日) 15万円

yattom

First you want some software. You know what you want, so it makes sense that it’s most convenient if the the software is built by yourself.

Unfortunately (or luckily) you’re too busy doing your own stuff to write a software. You call up someone and ask him to write the software for you. You save time and he got a job. Win-Win!

But wait. He needs to understand what you want. You need to tell the developer what you want. You need communication. One of the problems of communication is you cannot tell if you successfully communicated. You ask something. The only way to see if your request is communicated right is to see the resulting product. The developer show the product as a proof of the communication.

Time is money. If it proves wrong after several months, ah-oh. It’s wasted time. You don’t want to waste time or money. You want to see the proof early, as early as possible. So the developer wants to, for the sake of a satisfied customer, create only a small chunk of software and show it to yo

yattom

An experimental tralnslation of http://alistair.cockburn.us/Heart+of+Agile+Fortune+Teller+in+English into Japanese.

    COLLABORATE 協働

    +1 : COLLABORATE 協働

+1 : How does it feel to take turns contributing ? お互いに助け合ったらどんな気分だろう？

    +1 : TRUST 信頼

yattom

kawagutiさんが公開してくれたFearless Changeのワークショップの簡単な内容です。

https://github.com/kawaguti/fearless-change-pub/tree/master/carddeck

1. 人を集める。Fearless Changeやパターンを勉強するとは言わず、みんなの現状と課題を共有できるワークショップがあるからやってみようと声をかける。
2. 資料を印刷する(5,6人なら1セット63枚。8人以上なら4～6人ずつに分け、グループごとにセット準備)。できればコピー用紙ではなく、B6か3x5のカードに印刷する。
3. まず白紙のカードを配り、各自で現在感じている問題を書いてもらう。1枚1点で、何枚書いてもいい。(5分)
4. 各自書いた中で一番重要と思う問題を1枚選び、全員で発表する。
5. パターンのカードを机にばらまき、みんなで眺めながら、誰かの問題に使えるかも？と思うものを見つけて共有したり話し合ったりする。組み合わせや順序も考えてみる。 (5.は、誰かの問題1つだけに絞って全員で探しても良い)

yattom

def right_triangle_of_natural_numbers(max_n):
    '''
    Return all right traiangles whose edges are natural number length.
    Triangles of same ratio are discarded.

    >>> right_triangle_of_natural_numbers(5)
    [(5, 4, 3)]
    >>> right_triangle_of_natural_numbers(20)
    [(5, 4, 3), (13, 12, 5), (17, 15, 8)]    
    '''

yattom

// An ugly quick hack to get prices from Amazon
// Using node-apac https://github.com/dmcquay/node-apac/
// and almost same as the example in its README
var util = require('util'),
    OperationHelper = require('apac').OperationHelper;

var opHelper = new OperationHelper({
    awsId:     process.env.AWS_ID,
    awsSecret: process.env.AWS_SECRET,
    assocId:   process.env.ASSOCIATE_ID,

yattom

What is Pragmatic TDD?

プラグマティックTDDとはなにか？ こちらの記事の翻訳になります http://adaptiveobjectmodel.com/2012/01/what-is-pragmatic-tdd/

by JOSEPH YODER on JANUARY 11, 2012

by Joseph Yoder & Rebecca Wirfs-Brock

What do we mean by Pragmatic TDD?

僕らがプラグマティックTDDという言葉を使うわけ

yattom

TDDBC課題：整数の区間

課題１ 整数の閉区間 (closed range)

【例】

[3,8]
-> 下端点 (lower endpoint) が3, 上端点 (upper endpoint) が8 である整数閉区間
-> 3 と 8 は区間に含まれます

yattom

import java.security.AlgorithmParameters;
import java.security.Key;
import java.security.SecureRandom;

import javax.crypto.*;
import javax.crypto.spec.*;
import java.security.spec.*;

import org.apache.commons.codec.binary.Base64;

yattom

// ==UserScript==
// @name        OlympicRemover
// @namespace   http://yattom.jp/experimental
// @include     http://www.nikkei.com/
// @version     1
// ==/UserScript==


var org_func = window.onload();