spout

September 17, 2001 spout

Flattery

September 17th, 2001

Is it imitation or nudity that’s the sincerest form of flattery? Either way, it looks like Robert Scoble is naked outside where the neighbors could see (unlike mine, which was inside and very private : ).

September 11, 2001 spout

Give Comfort

September 11th, 2001

The World Trade Center and the Pentagon were attacked today when hi-jacked commercial airlines crashed into them, destroying both of the towers and damaging the Pentagon. I can’t possibly know what the people who had friends and families in those buildings are going through right now, but my thoughts and prayers are with them. If there’s anything you can do today or in the coming weeks or months to help those people to recover from their loss, please put aside your computers and your work and do it. I will be doing the same. Thank you.

If you’re interested, both Amazon.com and PayPay.com have set up disaster relief donation funds. 100% of all donations go directly to the American Red Cross.

August 23, 2001 spout

Q&A: .NET Cross Language Inheritance?

August 23rd, 2001

Q: D.J. Stachniak writes:

I missed the Conference.NET, but I’ve been reading through the PowerPoint presentations posted on DevelopMentor’s web site. I noticed in the C++ In A Managed World presentation that there is a slide (page 62 specifically) which says .NET supports real inheritance across languages - Although, that doesn’t mean you should use it…”

Would anyone like to take a crack and explain to me why cross language inheritance might be bad?

A: Chris responds:

At the Microsoft PDC in 1993 (also known as the COM PDC), Kraig B. introduced COM by saying that it didn’t have inheritance, but that was a good thing, because of the fragile base class problem. This problem says that derived objects, by definition, need to have incestuous knowledge of their base classes, including full understanding of the implied contract (which often requires to source to determine). What made this relationship fragile was that reliance on the implied contract caused all kinds of trouble when it changed, implying that it was knowledge of the source that caused this problem.

Of course, that’s not the case. We often experiment with components that we don’t have the source for and made decisions based on implied contracts that can easily change version to version. I would call this the fragile use” problem, but it’s more commonly called DLL Hell.” The idea that components can be replaced in the field without breaking things has long been known as a fallacy, and it doesn’t matter if you’ve got the source or whether you’re doing inheritance, aggregation or mere creation.

Eiffel’s Design by Contract is a good step towards detecting problems, but that’s an Eiffel-only thing. A good step towards reducing DLL Hell is the aggressive versioning and side-by-side installation of multiple versions that  .NET supports. If your client or derived class binds to a specific version of a component, then there’s no need to worry about it changing out from under you. Lack of source makes it harder to derive than to merely use, but assuming you can make things work empirically, cross-language inheritance might actually work in .NET (but don’t hold me to that : ).

August 17, 2001 spout

Conference.NET: Notes from the Field

August 17th, 2001

In talking to fellow DevelopMentor instructor Craig Andera today, I realized that those of you who didn’t get to attend DevelopMentor’s Conference.NET this week, must’ve hoped that DevelopMentor’s inaugural conference would suck so that you didn’t miss anything good. Well, I’m pleased to tell you that it didn’t suck. In fact, it was awesome. In further fact, I can’t say that I’ve ever had more fun at a conference. Of course, I couldn’t be everywhere, but here’s what happened to me:

Day 1: Chris Doesn’t Suck

Monday started with a rousing keynote from David Chappel, the industry’s best-dressed speaker (not a high bar in our industry, of course, but even I have to admit that he’s very good looking : ). An overview of his talk is available here, but what I most remember is that he pegged C++ as for dinosaurs only. While I certainly see his point, Microsoft’s Managed Extensions to C++ are going to enable a lot of people to enter the world of .NET without rewriting large code bases, which is going to make it enormously popular. This was further evidenced by the volume of MC++ questions that I fielded all week long (one attendee left the lab unhappy with the answer he’d gotten from a C# bigot and dragged me back there to examine his problem). Like VB before it, I predict MC++ to be the .NET love that dares not speak its name. Of course, David’s comments weren’t exactly designed to fill my day-long MC++ tutorial later that day…

Further compounding my potential attendance problem was going to be Don Box. Don’s an amazing man. He has the ability to dive completely into a technology, understanding it better than the designers, while still remembering the technical details of every other technology he’s ever ingested and completely belittling any value they might have had when compared to his latest fetish. In his talk, C++ didn’t respect the programmer, VB was the bane of every other programmer, COM was a mess and of course people had trouble getting DCOM to work over the Internet (how could it work when our neck-bearded network administrators had been replaced with kids pulled away from flipping burgers by the siren song of readily available MS networking certification?). Of course, to Don, only .NET and C# are at all useful to the reasonable, thinking developer. My biggest issue with Don is how right he usually is, but when he singled me out as destined to be the world’s last C++ programmer by painting an image of me in a 76 Ford truck sporting a gun rack and a bumper sticker reading, You can have my C++ when you pry it from my cold dead fingers,” I knew that those attendees who hadn’t yet decided weren’t likely to show up in my MC++ tutorial…

The last 2/3rds of my day was spent teaching my first real material in about three years. Oh, I’d given the odd conference talk now and again, but after years on the sidelines managing the development of Gen<X>, I was nervous. After all that time, could I still manage to entertain and educate a room full of people on a topic that the keynote speakers had spent all morning panning? As it turns out, I can. Oh, I can’t say I was brilliant, but I didn’t suck, and that was enough.

Day 2: Chris Has a Bad Hair Day

Day 1 ended with lots of celebration of my not sucking. I got to hang out with dear friends from as far back as 3rd grade and enjoy a bit more alcohol than was strictly necessary. After finally collapsing into bed at around 5:30am, I was hardly in any shape for my 8am business breakfast (note to self: never let the commission-based sales guy schedule the meetings — they’re just too damn eager). Needless to say I grabbed every minute of sleep that I could, but because of my short, deathlike REM, my hair was remarkably unmussed when I showed up without a shower (and even managed to make a point or two without falling asleep in my waffle). After two hours of scintillating business wrangling, I retired to my room to grab some quick Zs before returning to office hours” in the lab. The lab was really great, because it contained a couple of hundred PCs with exercises from each of the conference talks so that attendees could practice what they’d learned, getting help from the rotating speakers pulling lab monkey duty and answering attendee questions about designs scrawled on cocktail napkins. This was also where I learned that my continued lack of a shower had finally made it’s way to my hair. After thirty minutes of frightened stares, I stopped by the gift shop to buy a hat (stupid looking, but better than the Elijah Prince do” I was sporting) on the way to my first Birds of a Feather talk.

The BOF that I was to do with Brian Randell, a died in the wool VB guy, was entitled WinForms: Love it or leave it,” and it was designed for two things: 1) to leave things very open to audience participation and 2) to make sure that Brian and I could show up without any preparation whatsoever. You see, both of us had fallen in love with WinForms, but we hadn’t gotten to do much with it. We showed some fun demos, though. Mine was dedicated to the splitting and docking that WinForms has built into it (a thing of beauty!). Brian’s was dedicated to the new opacity property setting which makes windows imperceptible (how very useful…). So, after me making fun of Brian about this fetish, he was getting a bit tense. Then, when the WinForms designer decided to crap out because of a license file problem, causing Brian to have to shut down the IDE, delete files manually, restart the IDE, etc, he got even more tense. When Don decided to rub it in with his standard, You know, when I use Emacs, that never happens,” Brian snapped. Before I even had a chance to draw a breath to put Don back in his place, Brian came right back with, And how many products did you ship last year, Don?” A low moan swept the audience and Don turned tail and ran (after waiting a few minutes to let the ruckus die down). It was an awesome site to behold! I gained much respect for Brian that day.

I also gained much respect for WinForms. In spite of all of the hype about ASP.NET and Web Services, the thin-client backlash was in full swing at this BOF. Our room started out full and just gained people as it went on. Somewhere in the middle it became standing room only and still people came. And they didn’t just sit there, either. They all participated in a very rousing discussion first about MFC/VB vs. WinForms and then onto the more interesting thin vs. rich client. These people were very tired of the limitations of HTML 3.2 and cross-platform DHTML and anxious to get back to a real development environment for UIs. Truly, the Renaissance for rich UIs has begun.

Day 3: Jason Whittington is Accused of Slut-like Ignorance

Day 3 was a big day for me. It started with a talk on a subject near and dear to my heart, generative programming. This is a relatively new term for the technology ideas we’d been using for years in building Gen<X>. Again, my room was full, not only of attendees but also of two of the software engineers from the Gen<X> team (Chris Tavares and Shawn Vanness). The audience was certainly spending a lot of time nodding their heads and understanding the benefits of generative programming, but when I showed them how far we had taken it and all of the things for which we were using Gen<X>, that took them right over the top.

And then, right after getting to pitch my favorite technology, I got to proceed right to my next BOF, where I would get to tilt at my own personal windmill —  non-deterministic finalization. Those of you who know me or my programming style know that I’m absolutely in love with the idea of objects managing their own resources and them being notified immediately when the last client is done with them, either via COM-style reference counting or via a C++ destructor. This kind of deterministic finalization allows for very aggressive reclamation of resources, even in the face of exceptions or forgetful programmers. Non-deterministic finalization, on the other hand, leaves notification that an object is no longer in use to a background thread managed by a garbage collector. Because when the GC will get around to notifying an object is non-deterministic and empirically takes a long time, this means that resources can no longer be claimed by automatic means, instead leaving it to the client to manually notify the object via a Close or Dispose method. In my opinion, this is not a robust technique in the face of exceptions or forgetful programmers.

This issue has been the bane of my existence for years. When Java was first becoming popular, I was studying to become DevelopMentor’s first Java instructor. And at first, I really liked it. Then I discovered that Java had non-deterministic destruction and my life turned to ATL instead. Fast forward a few years to an early design preview of .NET where I learn that Microsoft was leveraging” many of the ideas of Java in its new runtime, including my favorite: non-deterministic finalization. I try to explain the problems inherent in this decision, but apparently, they’ve been all through this and Bill Gates has already made the decision for them. Of course, I don’t know this, so I kept fighting the good fight with one of the first emails on DevelopMentor’s .NET mailing list. This caused quite a stir, consuming much bandwidth to this day and eventually culminating in a long, explanatory email from Brian Harry, a PM on the .NET team. This email was intelligent and thoughtful and annoyed me no end because it put the final nail into the coffin containing my hope for DF in v1.0 of .NET, which we’re going to be living with for years. In fact, this email annoyed me so much that, on Day 2, I referred to it as Brian Harry’s little’ email.” After all, the room was nearly empty except for a few of my very close friends and one attendee who I hadn’t met. I met him 5 seconds later. It was, of course, Brian Harry. Remember, this was the day I had almost zero sleep, so I wasn’t exactly on top of my game. What an inauspicious way to meet your arch-enemy… [1].

Now, I told you that story so that I could tell you this one.

The BOF was to be a debate between me (pro-DF) and Jason Whittington (pro-garbage collection), with Don as the master of ceremonies. Imagine a thoughtful, reasoned exchange of ideas between calm, measured adults. Now throw that image away. Instead, Don introduced the BOF by saying that there was the right way of thinking and the Chris way of thinking and that I had been lured into the packed room (containing, as backup for the side of evil, Brian Harry) for an intervention.” Now, it’s not as if some of us didn’t try to be thoughtful and reasoned. For example, Jason gave us all kinds of background into the history and practice of garbage collection and how it works under .NET. In fact, if you haven’t yet had a chance to read Jason’s GC talk from Conference.NET, you should. It’s great. Unfortunately, the passions in the audience and in the other side of the debate, i.e. me, left little time for Jason’s approach. Instead, Don and I and the audience went back and forth, invoking stories of ASP.NET applications written by the cream of the crop at DevelopMentor that leaked so many resources as to make them unusable, laments of the semantic incorrectness of tying resource management to object lifetime and analogies of deck chairs on boats that did and didn’t sink. It was somewhere between a gospel revival and a schlock talk show (in fact, at one particularly cantankerous moment, the audience was literally chanting Jerry! Jerry!). At one point, I got so worked up during Jason’s attempts to shed some actual light on the topic that I interrupted him exclaim, Jason Whittington, you ignorant slut!” It was one of the highlights of my life…

But that was not to be the highlight of the show. Oh no. The most amazing thing about the show was later that evening at the close of conference party, where DevelopMentor introduced the .NET Band: The Band on the Runtime, made up of speakers and attendees who were also accomplished musicians. It was an awesome mix of showmanship, musicality and parody lyrics that caused the audience to sing along, wave their candles (in lieu of lighters), jump on stage and scream for an encore. When it was over, I was so moved that, in spite of my long friendship with Don and my pride in never seeing him as the hi-tech rock star that most folks do, I had to rush backstage to shake his hand and to be in his presence. I felt like a giddy school girl hoping to snatch a sweaty handkerchief from across his brow (which I’ll be auctioning off at eBay when I’m good and ready…).

Day n: The Rest of My Life

I have to say that I was deeply affected this week at Conference.NET. I’d like to thank everyone who organized it and hosted it and made it happen. And those of you who had the chance to go, but didn’t? Well, on your heads be it. Don’t make that mistake again next year…

Related Links

[1] As it turns out, it didn’t take long to make up with Mr. Harry and I soon found him to be reasoned and intelligent. Even worse, I found that I liked him. Damn it!

August 6, 2001 spout

What I Love Best About .NET

Monday, 8/6/01

DevelopMentor has long attracted smart folks. Really smart folks. These are the caliber of people that forces you to look up every once and a while and question your own worthiness. With this many high-caliber people together, you’d think they’d be able to look objectively at the world and avoid such religious arguments as What’s the best language?”, What’s the best platform?” and What’s the best editor?”

Nope.

We get into arguments like this (and even more esoteric) stuff all the time. Oh, open debate is healthy and we eventually come to a reasoned, balanced decision, blah, blah, blah, but these kinds of arguments made me realize that the thing I love most about .NET is that one of the most contentious arguments has just gone away: What’s the best language?” In the old days, this boiled down to VB vs. C++, otherwise known as practical vs. theoretical, simple vs. complicated or even, my personal favorite, journalism major vs. computer scientist. The argument was a real one, though, because VB6 and below put a real straight jacket on you when it came to real object-oriented features (the lack of implementation inheritance springs to mind), whereas C++ was so hard for so many people, it was almost impossible to build correct code with it. Much mud was thrown during these debates and no progress was ever made.

Until now.

Now, we have the same What’s the best language” arguments over VB.NET vs. C#, but they always peter out very quickly. While it’s true that VB.NET makes it much easier to build late binding component clients and C# allows unsafe code sections, neither of these features is enough for us to avoid agreeing that, modulo syntax, the two languages overlap by about 90%. Which means, and now I’m coming to the part that really makes me love .NET, I get to work with lots more smart people at DevelopMentor. Before, it was about the star-bellied Sneetches and the plain-bellied Sneetches. Since I felt I was one with a star on his belly (doesn’t everyone feel that way?), I couldn’t work with those without stars upon thars! Well, Sylvester McMonkey McBean, you can teach a Sneetch! [1]

I just got off the phone with a good friend of mine who I’ve never been able to work with before, because we’ve always had a great divide between us caused by my C++ bias. Now, for the first time, we get to work together! He can do his stuff in VB and I can either work with it directly, or I can easily port it to C#, because all the classes and functions that he’s going use in VB are going to be identical to what I would do in C#. So, while 90% of the language features overlap, there’s 99.999% overlap in the framework and how to use it between the two languages. To answer Rodney King’s immortal question, Yes. Finally, thank .NET, we can all just get along.”

[1] Those of you with kids will understand…

August 3, 2001 spout

My Favorite Web Sites

Friday, 8/3/01

These are the sites that I visit on a regular basis and like (the sites I visit on a regular basis and don’t like are not listed : ):

August 3, 2001 spout

My Favorite Software

Friday, 8/3/01

The following software is what I install on nearly every computer I set up. BTW, I pay for all my favorite software and you should, too. While I am guilty of trying” friend’s software, I own legal copies of every piece of software I use.

  • Windows XP. The grand unification of Win9x and Windows 2000 is finally at hand (isn’t that one of the signs of the apocalypse?) and it is awesome. The UI make over is great, but the two killer features for me so far (I’ve only have RC2 running for a few days at this point) are the new Terminal Services client (called Remote Desktop Connection and hidden under Accessories\Communications) is amazing for the keystroke handling alone and the ClearType support for LCD panels. Unfortunately, the latter is going to force me to buy LCD panels for all my computers and will make using the former with anything by Windows XP unbearable. No wonder they have a monopoly…
     
  • Microsoft Office XP. I know that they’re a monopoly. I know that they should be broken up. But damn, they just make killer (sic) software! As a writer and web maintainer, I absolutely love Word and FrontPage. The last real feature they added was red and green squiggles, but now I can’t live without them. As a guy dealing with lots of email and people and tasks, I live in Outlook. The fact that the integration with Word is now fast enough to let me use Word as my editor (to get red and green squiggles) has cut way back on people making fun of me for my shoddy emails. And while I can’t say I’ve ever used 1% of the features in Excel, for whipping up a quick set of numbers and totals, there’s nothing like it. Also, I was a proud owner of Visio 1.0, so that fact that they now bundle it is awesome. Truly, without Office, I may very well have skipped to Linux by now, but I’m addicted.
     
  • Microsoft Visual Studio.NET. There is no better set of development tools on the planet. This is #2 reason why I haven’t gone to Linux.
     
  • WinZip from Nico Mak Computing. I keep trying others, but I always come crawling back after the flash of some upstart comes and goes out of my life.
     
  • Action Outline from Green Parrots Software. This is a free-form hierarchical information keeper. While I practically live in Outlook, it has never had a good way to keep bits and pieces from my head. And what I especially love is that, as a keyboard only boy, I can navigate between the tree view on the left and the text view on the right, including adding topics, moving topics, etc, all without taking my fingers off the keyboard, including starting it from Start->Run (via action”). The only thing that I wish they’d add is encryption and password protectionbecause I’m embarrassed to tell you just what kind of information I keep in there in plain text (Keith Mr. Security” Brown would not approve : ). Indispensable.
     
  • 1st Clock from Green Parrots Software. Actually, Green Parrots is one of my favorite software companies. They make some cool stuff. I can’t live without 1st Clock for two reasons:
    1. It puts the day of the week and the date in the toolbar (because I can never remember and the time it takes to click my way to that info is too long).
    2. It lets me put custom strings into the toolbar. I always put the machine name in the toolbar so that as I switch between multiple PCs sharing a single keyboard, mouse and monitor using my Belkin OmniView, I can tell at a glance what machine I’m currently working with.

    The built-in automatic time synching with internet time service is really cool, too.
     

  • Process Explorer from Sysinternals. This software, formerly known as HandleEx, is invaluable in helping me track down all of my Can’t replace DLL: May be in use” error messages and it’s free!
     
  • RegMon from Sysinternals. This tool will should you where a program is reading from the Registry or where it’s writing.
     
  • tcpTrace from PocketSOAP. Simon Fell is one of the most talented contributors to the Windows development community. tcpTrace is the de facto tool for tracing SOAP packets.
     
  • WinVNC from AT&T. WinVNC is a free tool for controlling one computer from another. It’s not as cool or as fast as the new Terminal Services client from Microsoft, but it lets you control the currently active Windows station instead of starting up a new one, so it’s great for controlling the PC I have connected to my home theater, from the comfort of my couch (ever try to read PC output on a TV across the room? It doesn’t work…).
     
  • DevTrack from TechExcel. DevTrack is a good bug tracking database. Even though it is not one of my favorite pieces of software (sorry to throw you for a loop there : ), it was so much easier to set up than any of the competitors at the time and it did 80% of what we needed it for, that we live with it. The web client enables developers to use it all over the world and we were able to squeeze the data out of it that we needed. We do struggle with it sometimes, but not nearly as much as we would have had to if we’d have built out own from scratch. In fact, that’s why I list it here. Please don’t waste your time writing your own bug database. Buy one. If I had it to do over again, I would definitely spend time looking at FogBUGZ from Fog Creek Software.
     
  • Source Offsite from SourceGear. Source Offsite is an NT service that allows access to your Visual SourceSource database across the internet. Until they fixed a mighty leak problem that required us to manually kill the server a couple of times a day, Source Offsite was a depressing maintenance headache that we had to put up with, because when it worked, it worked so well, and there wasn’t anything else out there. Now that the leak is fixed, it just silently works. What more can you ask from a piece of software?
     
  • CleanVC from Bear Canyon. Mike Woodring and I go way back. Like me, he also has a bend for building tools and a website where he makes them available. The one that I absolutely cannot live without is CleanVC (he’s got other cool tools worth check out, too). From the command line, CleanVC takes the name of a directory and recurses through it and all sub-directories, killing all the intermediate files you get during a build. From the shell, you can right-click on a folder, choose CleanVC and get the same thing. I use it right before I zip something up for distribution and I use it to dig through my own project directory just before my weekly backup. Fabulous.
     
  • RegSvr.reg from me. This is a simple .reg file that I built way, way back that lets you right-click on a COM DLL or EXE and register or unregister it. It’s simple, I know, but I find I can’t use my computer without it.
     
  • Reflector for .NET from Lutz Roeder. This software is the OLEVIEW of .NET and it’s free!
     
  • UrlRun from me. This is a little console app that I use to reconnect URLs split between lines in an email. It’s smart enough to take out spaces and > characters when an URL is split between forward lines in an email. To use, copy the URL (with spaces and weird characters and all) into the clipboard and run UrlRun.exe. It will take the URL out of the clipboard, clean it up and start up IE.
     
  • BTW, Doom, Half-Life, Max Payne and JellyFish are my favorite games, the latter especially since I let Don beat me badly at backgammon the other day and I need the practice!
August 3, 2001 spout

My Favorite Books

Friday, 8/3/01

When I started writing books, I decided to stop reviewing other peoples’ books. I used to have a list of all of the books in the topic of my current interest and write a little review, either pumping them or panning them (this was long before Amazon.com). Once I decided to write books myself, I figured that there’d be a conflict of interest putting down competing books, so I stopped. However, I’ve had lots of folks ask me for a list of recommended books over the years, so I thought I’d provide one. While I’m still biased, there’s at least less conflict of interest if I just tell you about books that I love (although I’m not so proud that I don’t tag each book URL with my Amazon.com associates ID…).

I would give each of these books a 5-star rating on Amazon (and, in some cases, I’ve done just that). These are the books that I absolutely love (in no particular order):

  • The PC Is Not a Typewriter by Robin Williams. Of course, this is not by the famous actor, but Robin is as famous in the type design field as the other Robin is in the funny joke field. In fact, I’d say the former is even more impressive, because she doesn’t let herself get talked into writing bad books. You can’t go wrong with any of Robin’s books, but this is the first one of hers that I read and it still holds a special place in my heart. She specializes in teaching text design amateurs how to do text design and she’s great at it.
     
  • Genetic Programming III by J.R. Koza, et al. It’s no secret that I’ve long had a weakness in my heart for programs that generate programs. This one is the ultimate — programs that figure out themselves how to generate the correct program. Very wow. And, as is necessary for all books on this list, it’s very well written. It’s gripping in the same way that the latest John Grisham novel is gripping (to a certain kind of person : ).
     
  • Essential COM by Don Box. This is not only the classic work on COM, but it captures the heart of the movement of Windows programmers into component development. Be careful when you pick it up, though. You could start by looking something up and find yourself hours later still reading it for the pure pleasure. BTW, Don and I have good close friends for years, so I may be biased (except I’m not — this book rocks).
     
  • Don’t Make Me Think by Steve Krug. I’m still in the middle of reading this book, but wow. It lays out web usability in a way that even a web design cretin like me can appreciate. He points out the dos and don’ts in a way that’s clear, concise and entertaining. I’d love to be able to convey so much with so few words. And the production values of this book are great. I wonder if Addison-Wesley will let me write a .NET programming book in the same style…
     
  • User Interface Design for Programmers by Joel Spolsky. Joel maintains one of my favorite web logs and has collected his usability musings into a wonderful little book (clearly influenced by the Krug book). What makes this book so wonderful is that he captures all my feelings about usability, making me feel like an expert. Of course, I love a book that agrees with me. : )
     
  • Effective C++ by Scott Meyers. This is the book that started a movement. Of course, if you’re a C++ programmer, you need to read this book. But more than that, Scott laid out a style that has often been imitated, but never duplicated. (I know, because I tried.)
     
  • Mr Bunny’s Guide to ActiveX by Carlton Egemont III. If you’re a COM programmer, you need this book. Check out the close up of the pixel. It kills me every time.
     
  • C# Essentials by Peter Drayton, et al. This is hands down the best .NET programming book out there. It’s clear, concise and accurate (a novelty in the Windows book market). It only took me a few hours to read, but I learned a ton. BTW, Peter works for DevelopMentor, but I’m not biased because I don’t like him very much. : )
     
  • Fundamentals of Database System by R. A. Elmasri. This is one of the rare college text books that is not only readable, but practical. I read this after years and years of doing database work and was very surprised that they covered what software engineers actually need to know about how databases work.
     
  • Inside SQL Server by Kalen Delaney. Ironically, I haven’t had much database experience under Windows (I was a Unix Informix guy), but when I read the earlier edition by Ron Soukup, I fell in love with this product. I’m sure it was the way that Ron described it, but I couldn’t imagine doing SQL Server work without this book.
     
  • Modern Operating Systems by Andrew S. Tanenbaum. I sure wish I had had this book when I was taking my operating systems course in college, because then Linus Torvald would be reading about the success of my operating system and not the other way. This book is so great and so well-written that its inspiring. I firmly believe that every effective programmer needs to first understand what’s going on underneath their drag-n-drop, click-button IDE and this book sure lays a great foundation.
     
  • Computer Networks by Andrew S. Tanenbaum. Along those same lines, Tanenbaum’s networking book is also excellent. Makes me want to dig right into the plumbing.
     
  • TCP/IP Illustrated by W. Richard Stevens. Of course, the late Richard Stevens was a legend in the Unix community. This book, while slanted towards Unix, is still a great book about the world’s most dominant network protocol. I can’t decide whether I like this book or Computer Networks by Tanebaum better, but you can’t go wrong by owning both.
     
  • Unix Network Programming by W. Richard Stevens. As a Unix programmer not even doing network programming, this was still the bible. I know that you Windows programmers aren’t going to rush out and buy it, but if you wake up with a desire to program in a command line world, you’ll need this book.
     
  • Philip and Alex’s Guide To Web Publishing by Philip Greenspun. I don’t know how much practical information there really is in this book, but after reading it, I really wanted to quit my job and go to work for Ars Digita. Unfortunately, after Phil brought in some professional” management, they kicked him out and, as far as I can tell, are driving that company into the ground. Still, the amount that that guy has contributed to the internet community is staggering and inspiring.
     
  • ASP Internals by Jon Flanders. Now on this one, I’m very biased, because not only is Jon Flanders a fellow DevelopMentor employee, but he’s also been one of my best friends since 3rd grade and I wrote the forward. That said, if you want to know how ASP really works, down to source code for an ISAPI extension that Jon builds to work just like ASP, you need this book. And what’s so amazing is that he’s able to convey so much so concisely. I wish I could write this briefly. I hope an ASP.NET Internals is forthcoming from Jon.
     
  • The C Primer. This book is long out of print, but it’s where I learned the C syntax that has served me so well through so many languages, i.e. C++, Java, JavaScript and C#. I don’t expect anyone to need this book anymore, but it does have a special place in my heart.