afair

==========================================          ==========================================
             TMUX COMMAND                                        WINDOW (TAB)
==========================================          ==========================================

List    tmux ls                                     List         ^b w
New          new -s <session>                       Create       ^b c
Attach       att -t <session>                       Rename       ^b , <name>
Rename       rename-session -t <old> <new>          Last         ^b l               (lower-L)
Kill         kill-session -t <session>              Close        ^b &

mjallday

Make a client

curl http://balanced-hangman.herokuapp.com

Hopefully you'll see something like

{
 "index": "/", 
 "me": "/me", 

xpepper

I'm currently studying The Agile Fluency model by James Shore and Diana Larsen, and I found this talk, which is almost a perfect transposition of the great article published by the very same authors on Martin Fowler's blog: http://martinfowler.com/articles/agileFluency.html. This post is indeed the starting point if you want to deepen this topic. Or you can check out my notes here...

Here's the video: https://vimeo.com/68327316

The promise of Agile is simple and compelling: a team that effortlessly surfs the wave of business possibility, changing direction to meet the needs of a changing market. So why do so few teams achieve that ideal? Lack of fluency. Agile may be simple, but it's far from easy, and it takes years of practice to do well. We'll look at four phases of Agile fluency, what you can expect from each phase, and how to increase your team's fluency so you can achieve what Agile promises.

My personal notes taken while watching this video

>"Essentially, all models are wrong, but