software development concepts
I've been unhappy with every single piece of software I've ever released. Partly because, like many software developers, I'm a perfectionist. And then, there are inevitably … problems: * The schedule was too aggressive and too short. We need more time! * We ran into unforeseen technical
programming practices
When you join a team, it's important to bend your preferences a little to accommodate the generally accepted coding practices of that team. Not everyone has to agree on every miniscule detail of the code, of course, but it's a good idea to dicuss it with
software development
Since I started at Vertigo, here are a few of the projects I've worked on: * Michelangelo * Nash * Whiskeytown * Gobstopper These are our internal project code names. The names are chosen alphabetically from a set of items; every new project gets a name from the set. We start with
programming practices
Is software development an activity preferred by anti-social, misanthropic individuals who'd rather deal with computers than other people? If so, does it then follow that all software projects are best performed by a single person, working alone? The answer to the first question may be a reluctant yes,
ownership
One of the frustrations I’ve experienced with offshoring projects is the diminished sense of ownership. We’re still responsible for the software put in front of the end users, and yet we’re not allowed to put our hands on the code. Instead, we draw UML diagrams, we enter