This is just a spot to keep miscellaneous links. It also shows you what a geek I am.
Friday, August 31, 2007
The Joel Test: 12 Steps to Better Code - Joel on Software
The Joel Test
1. Do you use source control?
2. Can you make a build in one step?
3. Do you make daily builds?
4. Do you have a bug database?
5. Do you fix bugs before writing new code?
6. Do you have an up-to-date schedule?
7. Do you have a spec?
8. Do programmers have quiet working conditions?
9. Do you use the best tools money can buy?
10. Do you have testers?
11. Do new candidates write code during their interview?
12. Do you do hallway usability testing?"
Thursday, August 30, 2007
Patrick Labatut's personal page - FAQ
Tuesday, August 28, 2007
Here's the word list, and a PDF version of the word list.
Here's a list of easy-to-type words, i.e. that alternate between left and right keys on the keyboard: http://flamebox.narod.ru/lrwords.txt. It's mirrored here: http://brink.st/config/files/docs/lrwords.txt
Here's a password tester to test the results: http://www.securepassword.info/index.php
PasswordSafe is a good password generator.
Thursday, August 23, 2007
I was unable to create custom handlers in the Enterprise Library. The key is this. Note in particular the code in bold and italic.
The key is the constructor. It requires a signature of
(NameValueCollection ignore)
.using System;
using System.Collections.Specialized;
using System.IO;
using System.Text;
using System.Diagnostics;
using System.Windows.Forms;
using Microsoft.Practices.EnterpriseLibrary.Common.Configuration;
using Microsoft.Practices.EnterpriseLibrary.ExceptionHandling;
using Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Configuration;
namespace CustomExceptionHandling
{
[Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationElementType(
typeof(Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Configuration.CustomHandlerData))]
public class MyCustomExceptionHandler : IExceptionHandler
{
public MyCustomExceptionHandler(NameValueCollection ignore) { }
#region IExceptionHandler Members
//...
#endregion
}
}
Tuesday, August 21, 2007
How to: Launch the Debugger Automatically
"Sometimes, you may need to debug the startup code for an application that is launched by another process. Examples include services and custom setup actions. In these scenarios, you can have the debugger launch and automatically attach when your application starts.
To setup an application to launch the debugger automatically
-
Start the Registry Editor (regedit).
-
In the Registry Editor, open the HKEY_LOCAL_MACHINE folder.
-
Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\currentversion\image file execution options.
-
In the Image File Execution Options folder, locate the name of the application you want to debug, such as myapp.exe. If you cannot find the application you want to debug:
-
Right-click the Image File Execution Options folder, and on the shortcut menu, click New Key.
-
Right-click the new key, and on the shortcut menu, click Rename.
-
Edit the key name to the name of your application; myapp.exe, in this example.
-
-
Right-click the myapp.exe folder, and on the shortcut menu, click New String Value.
-
Right-click the new string value, and on the shortcut menu, click Rename.
-
Change the name to debugger.
-
Right-click the new string value, and on the shortcut menu, click Modify.
The Edit String dialog box appears.
-
In the Value data box, type vsjitdebugger.exe.
-
Click OK.
-
From the Registry menu, click Exit.
-
The directory containing vsjitdebugger.exe must be in your system path. To add it to the system path, follow these steps:
-
Open the Control Panel in Classic view, and double-click System.
-
In System Properties, click the Advanced tab.
-
On the Advanced tab, click Environment Variables.
-
In the Environment Variables dialog box, under System variables, select Path, then click the Edit button.
-
In the Edit System Variable dialog box, add the directory to Variable value. Use a semicolon to separate it from other entries in the list.
-
Click OK to close the Edit System Variable dialog box.
-
Click OK to close the Environment Variables dialog box.
-
Click OK to close the System Properties dialog box.
Now, use any method to start your application. Visual Studio will start and load the application."
-
Thursday, August 16, 2007
If the Freakonomics guys and Malcolm Gladwell hosted This American Life... - (37signals)
"Radio Lab (iTunes podcast link) is what you’d get if you put Freakonomics, Malcolm Gladwell, and This American Life in a blender.
"Each episode of the folksy science show is “a patchwork of people, sounds, stories and experiences centered around One Big Idea.” The banter between hosts Jad Abumrad & Robert Krulwich can be slightly grating at times, but, overall, they do a great job of boiling down complex subjects and keeping things interesting. The way they use sound is intriguing too."