Speaker details

Llewellyn Falco

spun laboratories incorporated
Llewellyn Falco
As an Agile software consultant Llewellyn Falco routinely finds himself working with companies undergoing transformations who have hired him to improve their employees' ability to deal with messy, orphaned, and otherwise ugly code. He is the inventor of approval tests (<http://www.approvaltests.com>www.approvaltests.com) and you can get a pretty good idea of him form this blog post: http://tinyurl.com/6aklzv
{speaker.userFirstName} {speaker.userLastName}

Speaking Sessions

  • Technical Coaching Toolbox

    Llewellyn Falco has been traveling the world as a technical agile coach for over a decade. Along the way he has developed a structured approach for creating lasting change for his teams. In this session he'll teach us the six most powerful practices from this approach.

    Including:
    2 week iterations
    2 hour Mobs
    Learning Hour
    Retrospectives
    Lunches
    Daily Status Emails

  • Refactoring to Async

    In this C# demo, we will go through a step by step guide to turn normal code into asynchronous code. Along the way we will discover insights into what the code does while doing small proveable refactoring. Finally move to asynchronous code in a single keystroke.

    Demos in C# but applicable anywhere.

  • From 0% to Cleanly Refactored 100% tested code

    In this guided demo, we are going to look at 3 different techniques that are remarkably powerful in combination to cut through legacy code without having to go through the bother of reading or understanding it. The techniques are: Combination Testing: to get 100% test coverage quickly Code Coverage as guidance: to help us make decisions about inputs and deletion Provable Refactorings: to help us change code without having to worry about it. In combination, these 3 techniques can quickly make impossible tasks trivial. Will will be doing this on the Gilded Rose Kata, https://github.com/emilybache/GildedRose-Refactoring-Kata It is extra beneficial if you try it out yourself first so you can see how your implementation would differ.

Speaker Book(s)