Recently, I helped spearhead our department’s adoption of centralized static code analysis. I worked with one of our mobile engineers to research various tools and create a decision matrix for comparing options. I’ve introduced new tools to my team before, but this was my first time selecting a tool that would be rolled out and used by my entire engineering department. It was also our department’s first time trying centralized static code analysis.
Software development in 2016 is a crazy complex process. Modern applications are increasingly distributed, regularly requiring access to an array of systems controlled by 3rd, 4th and 5th parties. So what happens when we are building the next killer-app-uber-disrupting-unicorn and the API that we NEED to access goes down?
Slam our Macbooks shut, whine about up-time and go home?
Consume our body weight in caffeine in preparation for the glorious return of the API?
Sit quietly and wait for morning to come?
Here’s the first template post in this series, following my opinion piece on when to use a PM tool versus creating your own spreadsheet. True to our nature as proponents of open source software, we also enjoy opening up our process a bit.
I’m starting a new series dedicated to sharing project management templates we’ve created and frequently use at Metal Toad. We use various tools on projects (Harvest, Jira, Basecamp, Trello, Invision, etc.), but like many others we’ve talked to, we still use plenty of spreadsheets and documents to improve project tracking and documentation. Yes, there are tools that accomplish what we’re looking to do, but many don’t do it well enough, and others do it too well. Sometimes a spreadsheet is just right.
I recently attended BADCamp where I had the opportunity to talk shop with project managers from a number of different agencies. I had some insightful conversations and a few really good takeaways that will help me improve project management at Metal Toad. But for the most part, the go-to conversation seems to be about project management tools. Do you use Basecamp? How about Trello? Jira? MS Project? Any of the other five hundred options out there?
At tonight's PDX WordPress Dev meetup (thanks for the pizza Digital Trends) Daniel Bachhuber had some questions about benchmarking a plugin. Benchmarking WordPress itself is easy, but it's harder to isolate a specific plugin, much less a few calls to preg_match_all() within it. The questioned SEO Auto Linker plugin does this on every page load, so any running time adds latency on every page.
Speculation from the meetup is that a PHP regex operating on post content, a blob, and looping through hundreds of links could be pretty slow. Too much caffeine today meant I had to give it a try.
I recently helped a friend with a couple bugs they were fixing on a mobile site, and suddenly realized that there is a good basic list of tools that folks should have in their frontend dev kit. Robbie wrote a little while ago about some of the front end (CSS/CSS3) tools he uses, so I thought I'd add to the list, and lean a bit more toward debugging.