I. M. Wright’s “Hard Code”

An opinion column for developers.Brutally honest, no pulled punches.
Posts
  • I. M. Wright’s “Hard Code”

    August 1, 2005: “Controlling your boss for fun and profit”

    • 4 Comments
    I. M. Wright's "Hard Code" book excerpt There’s a great gesture you can do to show just how little you care about someone who is wallowing in self-pity. You lightly rub the tips of your thumb and forefinger together saying, “This is the world’s smallest...
  • I. M. Wright’s “Hard Code”

    Don’t be a tool

    • 4 Comments
    A recent flood of build breaks triggered a wave of tool suggestions to plug the cracks in our code. Some argued for faster builds. Some argued for deeper branching. Some argued for a “gauntlet” service that simulates official builds and blocks...
  • I. M. Wright’s “Hard Code”

    A change would do you good

    • 4 Comments
    Few Microsoft engineers change positions between mid-May and mid-August—they don’t want a role change to adversely impact their annual performance ratings, which lock around mid-August. Of course, managers shouldn’t allow position changes...
  • I. M. Wright’s “Hard Code”

    There's no place like production

    • 4 Comments
    As much as I love Microsoft®, and as many advantages as we have as a company in the intelligence of our people, the breadth of our products, and the boldness of our vision, there are times when people here are frigging clueless. It’s not everyone—Microsoft...
  • I. M. Wright’s “Hard Code”

    Cycle time—the soothsayer of productivity

    • 4 Comments
    Nothing infuriates me more than wasted time and wasted effort. I’m not talking about training, reorgs, moves, morale events, or vacations. Those at least have the potential to be valuable in your life. I’m talking about build time, integration...
  • I. M. Wright’s “Hard Code”

    Coordinated agility

    • 3 Comments
    I’ve been using Scrum for seven years and writing about it for the last six. Scrum’s concept is fantastic—multidiscipline, self-directed teams, iterating on short scenarios (stories), in small batches from start to finish, within short, fixed-length,...
  • I. M. Wright’s “Hard Code”

    Quality is in the eye of the customer

    • 3 Comments
    Not every bug is the same. A bug that frequently freezes an app gets more attention than an extra line of green pixels in a border. An embarrassing typo in a prominent feature is more urgent to fix than an inappropriate exception thrown by a misused API...
  • I. M. Wright’s “Hard Code”

    Software performance: What are you waiting for?

    • 3 Comments
    You hurt your shoulder playing volleyball, so you make an appointment to see your doctor. You enter the office and wait in line for five minutes just to let the receptionist know you've arrived. He has you verify your contact and insurance information...
  • I. M. Wright’s “Hard Code”

    So far away: Distributed development

    • 3 Comments
    If you are a software geek, like me, being the product support technician for your friends and family comes with the territory. While it's painful to watch your family struggle with software, particularly if you helped write it, at least you can tell...
  • I. M. Wright’s “Hard Code”

    My experiment worked! (Prototyping)

    • 3 Comments
    It's summertime. Time to sit out in the sun and daydream, perhaps on a vacation or a weekend afternoon. When your mind is relaxed at times like these, you often think of beautiful new ideas. You further develop those ideas and then, when the time is right...
  • I. M. Wright’s “Hard Code”

    At your service

    • 3 Comments
    Remember this one, "The microprocessor changes everything!" No, it didn't. Yes, it had a big impact, but people still fretted about the same problems and tried to accomplish the same things. They just created problems and accomplished things more efficiently...
  • I. M. Wright’s “Hard Code”

    How do you measure yourself?

    • 2 Comments
    At Microsoft, we can execute, but can we think? When billions of dollars are on the line, you better not be guessing about decisions. A decade ago, our products weren't guesses; they were enhanced impersonations of our competitors' successful products...
  • I. M. Wright’s “Hard Code”

    Lead, follow, or get out of the way

    • 2 Comments
    We're closing in on midyear career discussions again. It's time to place your hopes and humility in the hands of your hierarchy. I still haven't recovered from the amputation of our midyear ratings, which allowed managers to send messages and employees...
  • I. M. Wright’s “Hard Code”

    October 1, 2006: “Bold predictions of quality”

    • 2 Comments
    I. M. Wright's "Hard Code" book excerpt I’ve been busy dogfooding lately. It’s an ideal diversion for masochists. When it gets to be too much, I can always take respite in a nice horror film. Thank goodness what passes for dogfood now is a vast improvement...
  • I. M. Wright’s “Hard Code”

    Are we functional?

    • 2 Comments
    When Steven Sinofsky and Jon DeVaan took on joint management of Windows® 7, they made several significant changes to the entire organization. Two profound changes were creating a single centralized plan and switching to a functional organizational structure...
  • I. M. Wright’s “Hard Code”

    20 years together

    • 2 Comments
    Eric Aside It's my 20th Wedding Anniversary. My wife and I are celebrating in the San Francisco Bay area, where we first started living together a few blinks of an eye ago. We'll watch a ball game, see some sites, and visit Tesla Motors to check out a...
  • I. M. Wright’s “Hard Code”

    De-optimization

    • 2 Comments
    Why? Why! Why do managers make stupid decisions that cause devastating churn and tawdry results? And it's not just managers, though they are particularly proficient at promoting poor performance—architects, leads, and individual contributors flood the...
  • I. M. Wright’s “Hard Code”

    Hired helpers

    • 2 Comments
    There are never enough resources to complete our ambitious plans, so Microsoft is constantly hiring help—vendors and contingent staff (CSG). Full-time employees (FTEs) are hired too, but the relationship is different—at least it’s supposed...
  • I. M. Wright’s “Hard Code”

    I messed up

    • 2 Comments
    Ever make a bad mistake? One that makes you feel like there’s a hollow in your chest—you know you’ve messed up badly. Maybe you were even trying to do the right thing, but it just ended up wrong unintentionally. This happens to me regularly...
  • I. M. Wright’s “Hard Code”

    Am I bugging you? Bug Reports

    • 2 Comments
    Some developers hate seeing bugs. They think bugs indicate a failure on their part—that their code seemed perfect until bugs were found. These developers are called “amateurs.” Real developers know the only reason you haven’t found...
  • I. M. Wright’s “Hard Code”

    You're no bargain either

    • 2 Comments
    “Can I talk to you about Bozo? He gets on people’s nerves. His communication style causes trouble. He’s bringing the whole team down. He’s a freaking clown.” If you’re a manager, you’ve probably heard this before...
  • I. M. Wright’s “Hard Code”

    Data-driven decisions

    • 2 Comments
    You’re working on a feature and think there’s an obvious customer improvement to be made. The tester thinks you’re in obvious need of medical attention from a psychiatric professional. She believes the shipped design was fine from the...
  • I. M. Wright’s “Hard Code”

    Evil assumptions

    • 1 Comments
    You work on big, important projects that involve many moving parts and many different teams. You work hard to deliver your piece on time and with high quality. No one can claim that you’re the one who held things up. No, it’s always those...
  • I. M. Wright’s “Hard Code”

    You have to make a decision

    • 1 Comments
    What’s worse—a flawed decision or no decision? That’s easy. Decisions keep a business moving. An imperfect decision might move your business slightly in the wrong direction, but at least it will be moving. Make a few adjustments, and...
  • I. M. Wright’s “Hard Code”

    Individual leadership

    • 1 Comments
    Want to create a noxious gas? Combine ambitious yet clueless engineers, a flat functional organizational structure, and the upcoming midyear career discussions. Soon toxic fumes will emanate from individual contributors (ICs) in response to impotent explanations...
Page 2 of 3 (71 items) 123