@jsmith said:
Hungarian notation also makes some things a little more cumbersome. Example - a database with 500 stored procedures all starting with "sp". If they started with a range of letters, then it would be easier to navigate the list by typing the first letter in Enterprise Manager.
When using MSFT SQL Server, try not to prefix your user stored procs with 'sp'. (a quick google returns this http://vadivel.blogspot.com/2006/12/dont-start-user-defined-stored.html).
As for HN.. I don't like it anymore. I used to think it was good - "wow, man, you can tell the type just by reading the name". But these days I prefer more concise code. Most of the time I KNOW the type! "strFirstName" is hardly helpful. When would a FirstName be anything BUT a string? If there's any doubt, the IDE will help you.
Anything that makes code easier to READ is good by me, and that includes dropping HN (and most of the time comments :).
The only use I see for HN is when you look at a bit of code for the FIRST time, ie you are new to a project/codebase and are learning your way around. Once you know the code well, HN becomes pointless.