I’m the Director of Web Development at ISDA, a trade organization whose goal is to make the global derivatives markets safer and more efficient. I started there a little over 6 years ago, just after they had launched a new site. The design was contemporary for its time. The codebase was built on top of a custom CMS developed by three separate development firms in the Ukraine. There were some interesting design decisions in the codebase, and a lot of hacks that had been implemented to “just make it work.
Back in April I gave a talk at WPNYC about debugging. Enjoy!
Originally published on forbes.com. You’d like to use open source software, but you’re not sure what criteria you should use when deciding whether to rely on it for a specific project or not. I have a long, complicated history with open source software. I use open source libraries every day in my work, and I’ve developed several criteria for evaluating projects. I got my professional start in tech as the technical co-founder of a news startup.
I’ve been exploring Vagrant lately. At work we need a better development workflow, and at home I’ve been reaping the benefits as well. One of the nice aspects of Vagrant is the ephemeral nature it gives to your environment. You can spin up a development box quickly and easily with a single command vagrant up when you’re not working you can halt the virtual machine with vagrant halt and when you’re not working on the project you can destroy the virtual machine and clear up your resources with vagrant destroy.