Writing your own tools for development

Writing your own tools for development

By Andrew Hewus Fresh (‎AFresh1‎) from pdx.pm
Date: Wednesday, 22 June 2016 09:00
Duration: 50 minutes
Target audience: Any
Language: English
Tags: annoyances development tools

You can find more information on the speaker's site:


My development style is to keep my environment as simple as possible, but no simpler. To that end I've written some tools that make writing and testing perl better, from a customer request that became a tool for load testing to a ruby tool I saw in a video and desired so much I just had to reproduce it. I have examples of making it easier to use NYTProf in our environment and how our darkpan and Carton are making my life better as well as some of the ways I've made writing tests easier and getting coworkers to write more of them. Whether you use my ideas or just find strategies for coming up with your own, you should come away thinking about what gets in your way and how you can add tools ways to improve your development process, code, and life.


Attended by: Chad Granum (‎Exodist‎), Dave Rolsky (‎autarch‎), Lee Johnson, Greg Brennan, David H. Adler (‎dha‎), Chris Shelton, Turd Furgison (‎fartfart‎), Mike Weisenborn, Tushar Dave, Jason Crome (‎CromeDome‎), Josh Lavin (‎digory‎), Ross Steiner (‎rdsteiner‎), Adam Boyers, Thomas Glase, Paul Johnson, D Ruth Bavousett (‎druthb‎), Henry Van Styn (‎vanstyn‎), Leonard Harris, Upasana Shukla, Brad Lhotsky, Adam Engle, Doug Bell (‎preaction‎), Dana Jacobsen (‎danaj‎), James E Keenan (‎kid51‎), Karsten Schiela, Julian Brown, Aaron Staves (‎astaves‎), Walt Mankowski (‎waltman‎), Jon Gentle (‎atrodo‎), Michael Hamlin (‎myrrhlin‎), Brian Kelly, Galen Charlton, Miller Hall, R Geoffrey Avery (‎rGeoffrey‎),