Daniel Read's blog

On his popular blog, The Mindset, Lidor Wyssocky has written some worthwhile posts recently that riff on the intersection of two current hot topics in blogland, one relating to methodology, the other to software team composition--both of which have an underlying theme of "What is the best way to enable success in building software?"

Pat Eyler has posted an interview with developer.* Books author Robert L. Glass, author of Software Conflict 2.0 and the forthcoming Software Creativity 2.0, and 25 or so other books.

If you don't have Jeff Atwood's Coding Horror blog on your radar, it's a good one for daily reading. Today, Jeff ponders some aspects of software programming history, recent and otherwise...

Via a reference today from the AYE blog, I came across a very interesting page on the AYE Wiki called "Musings on Women in IT," including many excellent comments that follow Johanna Rothman's original post...

Amazingly, I just spent ten minutes searching the web for a list of all of the built-in SQL Server stored procedures. I figured that's reason enough to post a link for the next poor sucker who has to do the same. So here it is: Microsoft's MSDN complete list / reference of all of the native / built-in / system stored procedures within the SQL Server database.

In relation to Terry Cornwell's question of whether to "DDA or not to DDA," this story seems like one to watch.

This looks like it should be fun:
http://www.anappaday.com/. "I plan on writing 30 applications in 30 days."

I very much enjoyed this thoughtful and well written post by blogger Ravi Mohan, " But Martin, Enterprise Software IS Boring." Ravi responds to a recent post by Martin Fowler regarding "customer affinity" and "enterprise developers," and ends up doing a great job exploring an area I've thought a lot about myself (with little to show for it): what accounts for the apparent differences between business-oriented developers from their counterparts who are more interested in "things like compilers and hardware hacks and 'tough' algorithmic problems" (Ravi's phrasing)?

developer.* watchers are no doubt aware that our first two books (Software Conflict 2.0 and the forthcoming Software Creativity 2.0) were written by Robert L. Glass, author or editor of more than 25 software books and a member of the profession for more than 50 years.

I recently found out about a new blog by Pete McBreen, author of two books I enjoyed a lot, Software Craftsmanship and Questioning Extreme Programming. The blog is called "Improving Wetware"

I can't resist contributing my own modest viewpoint to the debate that has been sparked by a recent pair of posts ("Language Wars" and "Wasabi") by Joel Spolsky regarding his company's use of a proprietary, home-grown language called Wasabi to produce the company's FogBugz product. Joel in the same posts shared his view that Ruby is not up to full enterprise production snuff (my paraphrasing), which triggered defensive responses by Ruby on Rails founder David Hansson, "Fear, Uncertain, and Doubt by Joel Spolsky" (sic) and "Was Joel's Wasabi a joke?".

On Ruby blogger Pat Eyler published today an intereview with Hal Fulton, author of The Ruby Way (forthcoming in a new second edition). Whether or not Ruby is of interest to you, if software development books and publishing are, you might find the interview interesting.

Some links and commentary related to the imminent release of IE 7 and related ripple effects.

I sometimes write articles connected to my position as a consultant at Northridge Systems that are published in a local Atlanta technology magazine called TechLINKS. The latest article is called "It’s 2:00am. Do You Know Where Your Unattended Systems Are?" I'm going to re-publish this article on the developer.* web site at some point in the future, but I thought I'd point to it in meantime at TechLINKS for anyone who'd like to check it out.

No matter how many articles I read about XSS attacks (a.k.a. cross-site scripting attacks), I can never get enough of them. Here's a good one from InformIT that narrates a hacker-for-hire's attack on a client's web application; he starts with a simple login form and ends up pretty much in total control after a short amount of time...