software development concepts
During the fantastic Monad session at PDC 2005,* Jeffrey Snover and Jim Truher illustrated the tradeoff between verbosity and conciseness: cp c:apples c:oranges -fo -r copy-item c:apples c:oranges -force -recurse Monad has a ton of aliases for common commands (e.g., echo is the same as
windows
1. If you’re lazy: 2. If you’re a contortionist: Shift + Ctrl + Esc 3. If you love modal dialogs: Ctrl + Alt + Del, then click or press the T key. 4. If you’re a ninja keyboard user: + R, taskman, Enter
software development concepts
In Waltzing with Bears: Managing Risk on Software Projects, DeMarco and Lister outline the dangers of penalizing negative thinking: Once you’ve identified and quantified these risks, they can be managed just like the others. But getting them out on the table can be a problem. The culture of our
security
Marcus Ranum, the inventor of the proxy firewall, brilliantly condenses why many security efforts are doomed from the start: they fall prey to the The Six Dumbest Ideas in Computer Security : 1. Default Permit Also known as “on by default.” This one is huge, and it alone is why the
software development concepts
I noticed something strange in a Windows ME screenshot embedded in a Joel Spolsky article I linked yesterday: Notice the Qantas icons? Those are shortcuts to a now-defunct unix machine at Joel’s company, Fog Creek Software. You can find evidence of it at the bottom of this forum post
software development concepts
Navigating a new codebase can feel like like landing on an alien planet. That’s where static code analysis tools come in handy; they’re akin to software tricorders. They provide a general snapshot of unfamiliar code: Is it normal? Is it unusual? Is it dangerous?* There’s an element
software development concepts
I’m beginning to wonder if the book Head First Design Patterns would be better titled Ass Backwards Design Patterns. Here are some quotes from pages 594 and 595 of this 629 page book: First of all, when you design, solve things in the simplest way possible. Your goal should
user experience
Shawn Burke’s post Shippin’ Ain’t Easy (but somebody gotta do it) explains why you have to resist change at the end of a project, no matter how justifiable and rational the reasons may be. Even the smallest change has a real risk of introducing additional bugs. The first
.net
Omar Shahine’s Clean Sources is a nifty little right-click app for .NET developers: This application does one thing. It adds an explorer shell menu to folders that when selected will recursively delete the contents of the bin, obj and setup folders. If you have a .NET project that you
c++
If you were about to throw out your C++ compilers because of my post on the productivity benefits of managed code and scripting languages, hold your horses. Although managed code is pretty darn fast, sometimes performance still comes first. As Ole Eichorn points out in the comments: [You said] “given
programming languages
There’s a chart in Code Complete that compares the productivity of working in different languages: Programmers working with high-level languages achieve better productivity and quality than those working with lower-level languages. Languages such as C++, Java, Smalltalk, and Visual Basic have been credited with improving productivity, reliability, and comprehensibility
security
We were discussing nasty software hacks today at lunch. The worst hacks are always in software, but those software hacks have an insidious tendency to seep into the hardware, too. I was reminded of Intel’s infamous CPUID hack: Prior to the Pentium, software had to jump through elaborate loops