Do Real Programmers Use Source Control?

Andrew MacNeill asks Isn’t Source Control part of programming 101 yet?

Source code control, change management, modeling, testing and project planning are skills that distinguish professional programmers from “coders.” When the PC revolution displaced the entrenched bureaucracy of the mainframe and mini computer of the “Data Processing Department,” there were lots of babies thrown out with the bathwater. Every Tom, Jane or Mary who could code a macro in 1-2-3 then worked out hex codes for 132-column print, batch files, then created dBASE tables. One day they were brave enough to try to change the printer ribbon, the next they are writing multi-tier, distributed, transactional, multilingual applications. So, many folks didn’t have the advantage of computer science training that teaches methodical software development. The last twenty years has been a thrashing attempt to bring back the reliability (without the cost and time delay) of committee-driven waterfall development methodologies in a Rapid Application Development, Extreme Programming, Cyclic Development or another Personal Software Process.

One of the many ugly truths that IT doesn’t like to admit is that most of the folks out there delivering applications are amateurs. It’s why, in 1997, I presented “It’s the Process, Stupid!.” Because there is not one “generally accepted practice” of software development, there are huge variations in the amount of care, professionalism and engineering that’s brought to bear on software development tasks. In many of the shops I consult with, the line workers often know there ought to be a better way, but getting middle- and upper-management buy-in to invest in tools and training is difficult. Solo practitioners are on their own to work it all out. Some fly by the seat of their pants and get away with it; others dive in too deep and get bogged down with complexities of managing the tools. Another bunch decide against anything Not Invented Here and whip up their own source code control techniques, making daily ZIP files and hoping to add the right arguments to their copy commands. Rarely do these tools support branching, labeling, rollback, point-at-time images, reporting or the other key SCC features.

SCC may be part of Programming 101 now, but when did your client take the course?

MSNBC loses Dr. Weinberger

Scripting News points to David Weinberger’s post on doing 90-second blurbs on “the blogosphere” for MSNBC: David Weinberger: “I quit.”

and “I’m in the blogosphere to escape from this degradation of values.”

Excellent and insightful post. If the topics of blogs vs. mainstream media (the insiders are abbreviating it MSM in some of the posts), follow a few of the links for some thoughtful back-and-forth, I think Jeff Jarvis nails it: “Blogs don’t need mainstream media. Mainstream media needs blogs.”

Windows 2000 Mainstream Support ends 30-June-2005

Microsoft Watch from Mary Jo Foley notes “Windows 2000 Users: The Clock Is Ticking. June 30 marks the end of mainstream support for both the client and server Windows 2000 releases. A Windows 2000 rollup pack is still due by midyear.”

Time to start evaluating your options for your next operating system. There are lots of good choices out there. Me? I’m thinking Tiger, Ubuntu, Fedora and perhaps a little SuSE ought to do me.

Enderle: How Linux Saved Microsoft

OSNews also points to Linux Insider: How Linux Saved Microsoft. “Rob Enderle has an commentary at LinuxInsider discussing the effect Linux has had on Microsoft. An excerpt: “As I look at how Microsoft is changing to address the Linux threat, one that may actually turn out to be no more real then Netscape’s was, I can’t help but see how Microsoft has dramatically benefited from it — and much more broadly so than they did from the rise of Netscape.”

I think Enderle is right on when he talks about the effect that Open Source is having with Microsoft. “Competition breeds Innovation.” However, I think he falls off the deep end in his last section “False Threat?” where he tries to explain what Open Source is.

“open source” which, in turn, is based on a false concept. This concept is that people actually want to look at source code. No, it’s that people want the security of knowing that the code is there for a community to maintain, support and enhance, that a monopolistic code owner can’t take away the freedom to run the code they have.

Finally, we know that what is largely holding the open-source community together is a dislike for Microsoft. Little holds the community together! :) But the individuals who choose Open Source each choose it for their own reasons, often freedom of choice, freedom to experiment, freedom to extend, integrate, modify and hack together the solution to their own problem. It’s not about Microsoft, nor Computer Associates, nor IBM, nor any other one target.

… unless something dramatically changes, by 2015 we’ll be largely wondering what all the fuss surrounding Linux was really about. Perhaps, Rob. See you in 2015 and we can compare notes.