hide

Read Next

Mobile Analytics Event at Holocaust Museum

Julie Perlmutter's phenomenal Web Managers Roundtable event series continued yesterday with the United States Holocaust Museum hosting an event on Mobile Analytics.  PointAbout was a sponsor of the event.  You can also find a PDF of the PowerPoint deck here.

The event was titled "Proven Metrics Strategies for Finding Your Audience on the Mobile Web." The speaker was Greg Dowling, VP at Semphonic and previously the head of analysis at Nokia.

Event description: Mobile technologies are so new that few organizations have a handle on the metrics strategies needed to make sure their own mobile initiatives succeed. In this program of strategic insights, mobile analytics expert Greg Dowling will provide the road map.

Here's a video of the event:

Julie Perlmutter's phenomenal Web Managers Roundtable event series continued yesterday with the United States Holocaust Museum hosting an event on Mobile Analytics.  PointAbout was a sponsor of the event.  You can also find a PDF of the PowerPoint deck here. The event was titled "Proven Metrics Strategies for Finding Your Audience on the Mobile Web." The speaker was Greg Dowling, VP at Semphonic and previously the head of analysis at Nokia. Event description: Mobile technologies are so new that few organizations have a handle on the metrics strategies needed to make sure their own mobile initiatives succeed. In this program of strategic insights, mobile analytics expert Greg Dowling will provide the road map. As creator of the first worldwide mobile web analytics implementation standard, he'll discuss that work, the issues that make measurement standardizing difficult, the hurdles involved in navigating mobile's rapidly evolving terrain, and new ways to successfully address key mobile metrics issues. Here's a video of the event:

Test-Driven Development? Give me a break...

On Imported Blog

Update: At the bottom of this post, I've linked to two large and quite different discussions of this post, both of which are worth reading...

Update 2: If the contents of this post make you angry, okay. It was written somewhat brashly. But, if the title alone makes you angry, and you decide this is an article about "Why Testing Code Sucks" without having read it, you've missed the point. Or I explained it badly :-)

Some things programmers say can be massive red flags. When I hear someone start advocating Test-Driven Development as the One True Programming Methodology, that's a red flag, and I start to assume you're either a shitty (or inexperienced) programmer, or some kind of Agile Testing Consultant (which normally implies the former).Testing is a tool for helping you, not for using to engage in a "more pious than thou" dick-swinging my Cucumber is bigger than yours idiocy. Testing is about giving you the developer useful and quick feedback about if you're on the right path, and if you've broken something, and for warning people who come after you if they've broken something. It's not an arcane methodology that somehow has some magical "making your code better" side-effect...

The whole concept of Test-Driven Development is hocus, and embracing it as your philosophy, criminal. Instead: Developer-Driven Testing. Give yourself and your coworkers useful tools for solving problems and supporting yourselves, rather than disappearing in to some testing hell where you're doing it a certain way because you're supposed to.

Have I had experience (and much value) out of sometimes writing tests for certain problem classes before writing any code? Yes. Changes to existing functionality are often a good candidate. Small and well-defined pieces of work, or little add-ons to already tested code are another.

Rendering New Theme...