At Herrmann, one of our key fundamentals is that we try to "eat our own cooking" and use Whole Brain® Thinking in our own work. This post is part of a series where our engineering team talks about how they use Whole Brain® Thinking in their own workflow.

Here at Herrmann International one of our key fundamentals is that we try to "eat our own cooking" and use Whole Brain® Thinking in our own work. This post is part of a series where some of our team members talk about some ways they use Whole Brain® Thinking for their day-do-day work.

This post is by our Lead Software Engineer, Andrew Swerlick.

At first glance, software development might not seem like a job that involves a lot of day-to-day Whole Brain® Thinking. After all, a lot of what our team does seems like it's firmly situated in the technical, analytical A quadrant. Sure, we do have to collaborate with other internal teams on product design, requirements gathering, etc., but when it get to the point where our developers put their fingers to the keyboard and start writing code, all the other quadrants go away, right?

When I first started at Herrmann a couple of years ago, I probably would have said yes. But recently, our development team has adopted some practices that are showing me the value of writing Whole Brain® code.