The Colorful and Gray World of Engineering Management

Embark with me on my journey through the colorful situations & challenges and the (gray) ambiguity of management in the software industry.

Browse by Tags

Tagged Content List
  • Blog Post: Fixing What's Not Broken

    Many engineering teams look at change as a bad thing, something that will disrupt their work. And granted, changing for the wrong reasons, or making changes for the right reasons but too many of them too quickly, can be disruptive and affect productivity. But you should also be careful about being too...
  • Blog Post: The toughest question you can ask, isn't tough enough

    One skill all engineers need to have in order to ship high quality software is the ability to ask hard questions. No matter if you are a developer, a tester, or a project manager, you need to look at each situation, line of code, architecture/design, or user scenario and determine if you and your project...
  • Blog Post: What are Testers Thankful For?

    When I think about all the issues my QA team has to deal with to ship projects, I wonder as we get closer to Thanksgiving what they are thankful for. What makes their jobs easier or fun? Two things come to mind. Testers are thankful when their developers produce quality builds. Getting a build that...
  • Blog Post: 17 on 17

    On October 17th, I celebrate my 17th anniversary at Microsoft. If someone told me on my first day at work that I would be here for 17 years, I wouldn't have believed them. Besides marriage and family, there's not a lot else that has consistently been in my life for that long. I have new hobbies, live...
  • Blog Post: QA or Test - does the name really matter?

    I've been the manager for many different teams. Some call themselves Test and some call themselves QA. Personally, I've found it easier to just use those terms interchangeably. But for many, there are two very distinct schools of thought about what a Test team is and what a QA team is. Maybe at some...
  • Blog Post: No Surprises!

    This is what I aim for in my teams - no surprises. That means my team members do their best to not surprise me and I also aim to not surprise them. Surprises are great when it comes to birthdays at home with family and friends. But in corporate life, there's just no room for surprises. Even something...
  • Blog Post: There's No Room For Watermelons

    I have noticed a problem lately that needs some focus. I heard a statement that sums it up nicely. "Don't be green on the outside and red on the inside." Now if this was a joke (What's green on the outside and red on the inside?") I can think of a few answers like a frog, an alien (of course, maybe they...
  • Blog Post: Play with fire, but don't get burned

    Instrumenting your product's source code to get an indication of how much of the code was covered during testing is a really, really smart measurement to get. If you aren't at least measuring this number, you should be. Visual Studio provides features that continue to make this easier. What does this...
  • Blog Post: Do Whatever It Takes!

    I had a test lead years ago that did a great job at setting expectations for his people. But for himself, his main goal was always stated as "do whatever it takes to ship the product". This was really difficult to measure him against. But the concept is an interesting one. Many teams fall somewhere in...
Page 1 of 1 (9 items)