performance
In my previous entry on the real cost of performance, there were some complaints that my code’s slow and it sucks. If I had a nickel every time someone told me that, I could have retired years ago. Let’s take a look at the specific complaint that the
software development concepts
A recent post by Wesner Moise after a two month hiatus got me thinking about a passage from Steve McConnell’s, After The Gold Rush. Like all Steve’s stuff, it’s great, but the title is unintentionally ironic: the book was released in 1999, at the very height of
programming languages
It’s always reassuring to be reminded that people much more talented than myself make mistakes, too. And I especially appreciate it when they share those mistakes in the form of advice: On avoiding IT mistakes: Rick Cattell’s, Things I Wish I Learned in Engineering School: * Good technology is
javascript
When I visited Alex Gorbatchev’s blog, I noticed he had a unique client-side code highlighting solution in place, one I hadn’t seen anywhere else. That’s something I’ve wanted on my blog for a while; the vanilla <PRE> sections I’ve been using are serviceable,
multithreading
Back when I was writing for Tech Report, I had an epiphany: the future of CPU development had to be multiple cores on the same die. Even in 2001, a simple extrapolation of transistor counts versus time bore this out: what the heck are they going to do with those
software development concepts
Brad Wilson pointed out a new, interesting blog yesterday: Spurious Pundit. On managing developers: It’s like you’re asking them to hang a picture for you, but they’ve never done it before. You understand what you need done - the trick is getting them to do it. In
.net
Coming from humble Visual Basic 3.0 beginnings, by way of AmigaBasic, AppleSoft Basic, and Coleco Adam SmartBasic, I didn’t get a lot of exposure to formal programming practice. One of the primary benefits of .NET is that it brings VB programmers into the fold – we’re now real
programming languages
I stumbled across the Craig Andera post, The Last Configuration Section Handler I’ll Ever Need a few months ago, but I didn’t really understand the implications until I started writing a bunch of configuration section handlers. His approach is very clever; instead of writing a bunch of tedious
programming languages
Mike Gunderloy’s book, Coder to Developer, suggests, as part of configuring your IDE, that you explore programming specific fonts. I was intrigued, because I hadn’t ever considered that. I’ve been using Courier New 9 for years. A little searching turned up a few links: * This programming font
programming languages
Back in June, I mentioned that my favorite visual differencing tool was Araxis Merge. A co-worker recently recommended that I try out Beyond Compare, so I downloaded the 30-day trial and spent an hour playing with it. It’s definitely comparable to Araxis Merge. And in a lot of ways,
programming languages
As the old adage goes: Good programmers write good code; great programmers steal great code. This is definitely true, mostly because great programmers have learned to do some research before writing anything at all. However, even great programmers tend to be absolutely terrible at graphic design, even though the solution
programming languages
I found two interesting top 10 lists yesterday. From MSDN Magazine, 10 Tips for Writing High-Performance Web Applications, is a fine read. I’ll summarize: 1. Return Multiple Result sets 2. Paged Data Access 3. Connection Pooling 4. ASP.NET Cache API 5. Per-Request Caching 6. Background Processing 7. Page