This is Alexander Knopf's Typepad Profile.
Join Typepad and start following Alexander Knopf's activity
Join Now!
Already a member? Sign In
Alexander Knopf
Recent Activity
To all of you who got annoyed at the question being deleted, you can all just make your own stack exchange site, or propose for a new one on area51.stackexchange.com. So I figured I would just go ahead and do it. Hopefully enough people will like the idea to actually make it come to life. http://area51.stackexchange.com/proposals/42460/off-topic-humor
Toggle Commented Jul 22, 2012 on New Programming Jargon at Coding Horror
Imho (and very just my own opinion) reusing the same password for some things isn't that bad of an idea, as long as you know what you're doing. i personally use the same password (and quite possibly user name/email) for a lot of things, all of them completely inconsequential. i don't care at all if someone gets that "unimportant" password and logs in to everything that i used that password on, because it's all sites like forums, online games, J Random Website, etc. beyond that i have a password i use for things that are slightly more important but still an inconsequential loss on sites i trust. then i have different passwords for things like email accounts. and then i have secure IDs for my online poker accounts and would feel much more comfortable if my email accounts had something similar. now on the issue of storing passwords when you have a website/other kinda server that you require people to log on to (there's still a few things you can't use OpenID for i believe). When you only store a hash of a password, salted or otherwise, you're effectively shortening passwords to 20 bytes (or however long your hash is)(which is obviously longer than probably over 95% of passwords). now if you store 2 different hashes of passwords it's almost impossible to produce a hash collision since you need to have a string of characters that produces the same hash value against 2 different algorithms which then needs to be the same as the original password. but yeah obviously use openID wherever possible.
Toggle Commented Dec 15, 2010 on The Dirty Truth About Web Passwords at Coding Horror
one thing that you haven't mentioned (and i'm not sure if anyone else has) the non-programming programmer takes away the job of a programmer. which is bad for the programmer, the company, and any potential customer of that company. so considering so many of them actually make it to the interview in the first place.... how can the programming-able programmer distinguish himself from the one who can not actually program. should i add a line to my resume saying "i can actually program" ? would be nice if someone could come up with a way of helping all involved, the programmer who wants the job, the interviewer who would be very happy of never having to actually interview someone who can't program, and the company that does the hiring. i'm thinking a web based application process wouldn't be a bad thing, some little flash application that records all the keystrokes of a simple programming question (just so you rule out the ctrl-V people) and give the people who succeed a GUID of some sort which they have to put on their application. then you start by interviewing the people who have completed the simple question and only if you run out of applicants who have done that you start interviewing those who have not (and probably ask them to finish it before coming in for the interview, or before you call them).
Toggle Commented Feb 23, 2010 on The Non-Programming Programmer at Coding Horror
Alexander Knopf is now following The Typepad Team
Feb 22, 2010