http://sartak.org/talks http://sartak.org/talks/dcbpw-2013/git-flux/ <p><img src="git-flux.png" /></p> <p> There are a bazillion different ways to use git, which is of course a blessing and a curse. You can use it any way you like, but that puts the burden on you to figure out what's best.</p> <p> Well we've already done the hard work of figuring out what's best. I'm here to explain how we use git at Infinity Interactive to ship great software to our clients.</p> 2013-04-20 http://sartak.org/talks/yapc-eu-2012/role-usage-patterns/ <p>Roles are one of the most exciting and powerful features provided by Moose, but also one of the most misunderstood. This talk will explore, in depth, some common usage patterns (and antipatterns) for roles and how best to use them in the design of your classes. I will also talk about the philosophy of roles and how they fit in with the larger OO toolset.</p> 2012-08-22 http://sartak.org/talks/misc-2012/intro-to-moose/ <p>An updated version of my 2009 Introduction to Moose talk.</p> 2012-05-21 http://sartak.org/talks/yapc-na-2012/git-status-tackle/ <p>`git status` is verbose almost to the point of uselessness. git-status-tackle is a new suite of tools that tells you exactly what you want to know about your git repository in a very pluggable and configurable way.</p> 2012-06-14 http://sartak.org/talks/perl-oasis-2012/dtrace/ <p><a href="/talks/yapc-asia-2011/dtrace/">(日本語版はこちら)</a></p> <p>DTrace is an extremely powerful tool for examining what a computer is doing. Even in production. Without invoking the ire of the Munin Gods.</p> <p> It's also an indispensible tool for programmers who are trying to debug, optimize, or otherwise investigate what their code is doing when it ventures (and venture it must!) outside of the cozy, warm, abstract world of the Perl interpreter.</p> <p>If you tend towards printf debugging, then DTrace lets you break through to some seriously next-level shit. You don't have to pollute your application's code, or even restart it(!), to begin tracing it. You can also trace the execution of other Perl modules you're using, your operating system kernel, and other applications such as MySQL or Apache. It is awesome!</p> <p>This talk is intended as an introduction to DTrace for those who have maybe heard that it rocks but haven't ever used it. I'll also describe specifically Perl's support for DTrace and how to make use of the probes we've been adding.</p> 2012-01-14 http://sartak.org/talks/yapc-asia-2011/dtrace/ <p><a href="/talks/perl-oasis-2012/dtrace/">(English version here)</a></p> <p>DTraceは、コンピューターが何を動作していることを調べるために、とても強力なツールです。プロダクションでも使えますよ。ネットワーク監視という神様が怒らず！</p> <p> これは、Perlのやさしい世界の厳しい外部でも、デバッグや最適化や監視をするツールです。アプリケーションのコードを汚染していないままで、再起動が必要でなくて、トレースを示す可能があります！しかも、他の使っているモジューでも、カーネルプロセスでも、他のアプリケーションル（例えば:MySQL、Apache）でも、トレースで動作を検査できます。printfのようなデバッグすることが好きの方にとって、DTraceも好きになると思います。</p> <p>このトークでは、「DTraceはすごすぎるよ！」と聞いたが使ったことがない方のためにDTrace入門です。それ以外で、PerlのDTraceのサポートと、Perlに追加したプローブを説明します。</p> 2011-10-15 http://sartak.org/talks/yapc-na-2011/announcing-announcements/ <p>Say you're writing a system that uses the observer design pattern. What happens if instead of passing around the NAME of an event, you pass around an OBJECT representing the event? Turns out, a whole lot of goodness!</p> <p> Announcements enable communication from the observer to the observed, and even communication (and conspiracy) amongst observers themselves.</p> <p>All with a very strongly object-oriented, antler-shaped flavor.</p> 2011-06-28 http://sartak.org/talks/yapc-na-2011/cpandoc/ <p>This lightning talk was just a live demonstration of cpandoc. No slides, and nothing you wouldn't see in the documentation.</p> 2011-06-27 http://sartak.org/talks/yapc-asia-2010/evolution-of-path-dispatcher/ <p>A new-and-improved version of my YAPC::NA talk directly below. This talk has become a case study in Moosey design, describing how the needs of Path::Dispatcher's users have influenced its evolution. Too many talks present a topic as though the solution sprung fully-formed from the designer's brain in an instant, ignoring the interesting details of how a system is improved over time. Maybe next conference I'll present The Evolution of "The Evolution of Path::Dispatcher", a talk on how to evolve talks after presenting them. :)</p> 2010-10-15 http://sartak.org/talks/yapc-na-2010/path-dispatcher/ <p>Path::Dispatcher solves the problem of "dispatch" - mapping a string (the path) through a set of rules to find matches and then act upon them. Most commonly this is done in web applications to run one or more actions based on each incoming request URI. However, Path::Dispatcher, unlike most of the other modules in its niche, is not married to the web. It is also used to dispatch based on command-line arguments in some applications, and to dispatch commands in a MUD engine.</p> <p> This talk gives a brief overview of Path::Dispatcher's features. Then the meat of the talk describes how its flexible design has met the challenges thrown at it, and how Path::Dispatcher's sibling rival, Path::Router, would have fared.</p> 2010-06-23