146 reputation
4
bio website
location
age
visits member for 1 year
seen Mar 28 at 0:16

Mar
27
awarded  Commentator
Mar
27
comment Why is it bad to write something in language X as if you're writing a program in language Y in terms of using a shared coding paradigm
I understand the distinction, but I still don't accept that you are actually asking a question.
Mar
27
comment Why is it bad to write something in language X as if you're writing a program in language Y in terms of using a shared coding paradigm
This isn't a question, it's a complaint about another question. You asked people to help you, and now you want to vent because you're not happy about what they said. This belongs on your blog.
Feb
10
revised Is just using an email address for login a good idea?
added 590 characters in body
Feb
10
comment Is just using an email address for login a good idea?
@JeffO, I just don't understand why the password reset requests are any less vulnerable than the 'login emails'. People have and do hijack accounts by doing exactly what you said.
Feb
10
revised Is just using an email address for login a good idea?
added 590 characters in body
Feb
10
comment Is just using an email address for login a good idea?
I assumed that the email suggested by the OP would also be a temporary invitation to become logged in without a password - see the edit to my answer.
Feb
10
comment Is just using an email address for login a good idea?
The requirement to log out (on a shared computer etc.) isn't any different then if you have logged in with a password.
Feb
10
comment Is just using an email address for login a good idea?
Are you aware that passwords can often be reset using a link sent in plaintext email?
Feb
10
answered Is just using an email address for login a good idea?
Oct
8
awarded  Editor
Oct
8
revised Why use an OO approach instead of a giant “switch” statement?
edited body
Sep
19
comment Is it appropriate for interviewers to ask candidates for their Stack Exchange user name?
@emory This is a pain for the user. It is difficult to do properly as you never know when you might spout brilliance as part of a pragmatic 'work' query. It makes SE and the rep system less useful. It invalidates the benefit to employers as they are no longer seeing your real working headspace but the rep you built up cynically in your spare time. Finally it provides an incentive to aggressively answer easy questions about things like how to delete a remote branch in Git, rather than write detailed answers to obscure technical question that only you know about.
Sep
19
comment Is it appropriate for interviewers to ask candidates for their Stack Exchange user name?
A correlation between their performance and what about their questions/answers? The number? The score? The quality?
Sep
18
comment Is it appropriate for interviewers to ask candidates for their Stack Exchange user name?
Asking for SE/SO or github uids is one of those things that became much less useful as a indicator as soon as more than a few people start asking. In the past activity may have reflected someone who is passionate about programming and learning in their spare time. Now it could just as well mean someone karma-whoring and editing themselves to look good to employers.
Sep
18
comment Is it appropriate for interviewers to ask candidates for their Stack Exchange user name?
Agree. I have declined to provide my userid before. My feeling is that it would be detrimental to my work and a disservice to my current employer if I have to think about my online presence for future job applications everytime I use SE/SO.
Jul
25
awarded  Teacher
Jul
25
answered Why use an OO approach instead of a giant “switch” statement?
Mar
25
awarded  Supporter