hide

Read Next

Augmented Reality by Siamak Ashrafi & Mobile Energy Consumption by Frank Maker

I attended a great Android Meetup tonight by the Silicon Valley Android Developers Meetup (which, amazingly, has over 1,800 members).  There were several presenters tonight.  The first was Siamak Ashrafi, who talked about Augmented Reality and described the differences between Augmented Reality with GPS Markers vs. Fiduciary Markers.  You can find his presentation slides here.  The slides also have a few great videos showing AR off.  This Android group has recently created a forum for Android developers in Silicon Valley.

Frank Maker then gave a talk about Mobile Energy Consumption and ways to use software to decrease energy consumption.  That video is also below.

Siamak Ashrafi Augmented Reality Video:

I attended a great Android Meetup tonight by the Silicon Valley Android Developers Meetup (which, amazingly, has over 1,800 members).  There were several presenters tonight.  The first was Siamak Ashrafi, who talked about Augmented Reality and described the differences between Augmented Reality with GPS Markers vs. Fiduciary Markers.  You can find his presentation slides here.  The slides also have a few great videos showing AR off.  This Android group has recently created a forum for Android developers in Silicon Valley. Frank Maker then gave a talk about Mobile Energy Consumption and ways to use software to decrease energy consumption.  That video is also below. Siamak Ashrafi Augmented Reality Video: Mobile Energy Consumption by Frank Maker:

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...