| bio | website | geekality.net |
|---|---|---|
| location | Oslo, Norway | |
| age | 28 | |
| visits | member for | 1 year, 7 months |
| seen | yesterday | |
| stats | profile views | 5 |
Software Developer, Seventh-Day Adventist, Hobby Juggler... should for the most part sum things up :)
Favorite language: C#
Currently working with: Java, PHP, JS, HTML, CSS, et cetera
c'' , )
|
1d |
awarded | Quorum |
|
1d |
revised |
Why does the email subject appear before the body when composing an email? fixed typo |
|
1d |
suggested | suggested edit on Why does the email subject appear before the body when composing an email? |
|
Apr 10 |
comment |
How should we prepare users for a site overhaul? @georgiosd "I would advise keeping the designs separate", so in other words, if I interpret it correctly, there's no need to keep the feel and even look of the existing site in the new version. |
|
Mar 20 |
comment |
Can an OK button do nothing? I'd also change the label on the button from OK to <verb> |
|
Feb 25 |
awarded | Teacher |
|
Feb 25 |
comment |
When should auto-correction occur? Agreed! Silent auto-corrections, no thanks. Clear auto-suggestions with quick "correct" action, yes please. |
|
Feb 25 |
comment |
When should auto-correction occur? I can't say anything backed by data on that issue, but in my personal opinion I tend to prefer suggested-correction rather than auto-correction since auto-correction in many cases gets things wrong and then you have to fix it. Or you miss the auto-incorrection completely and end up having typed something else than what you thought. |
|
Feb 25 |
comment |
When should auto-correction occur? Aha, I see. Didn't know that! |
|
Feb 25 |
awarded | Editor |
|
Feb 25 |
revised |
When should auto-correction occur? added 188 characters in body |
|
Feb 25 |
answered | When should auto-correction occur? |
|
Feb 12 |
comment |
When client and server side validations occur, doesn't it make for a better UX to only do server validations? Remember you can use the server side validation through ajax calls as well. Meaning you'd be able to use the exact same rules in both places. Yes there's a short delay compared to a fully client side validation, but not much. |
|
Jan 3 |
comment |
Do people really want to look at multiple windows at once? I wouldn't necessarily use the term multi-tasking for this either. As a programmer I'm very often using multiple windows at the same time, but I'm working on a single task. Reason for the multiple windows is because this single task requires parallel usage of multiple tools at the same time. And if I have to do full screen switches between them I quickly lose my train of thought. By having them next to each other it's easier to have them "all in my head at once" so to speak. |
|
Dec 13 |
comment |
Should we use a sound/jingle when users arrive on our site or open our app? @PeterOlson Oh I've been annoyed by those, but depends a bit on how smooth and long they are, and if they can be skipped by pressing anything. Love one of those short Ubisoft jingles for example, but hate plenty of others. |
|
Dec 13 |
comment |
Should we use a sound/jingle when users arrive on our site or open our app? @eskimo Me too. And then I go straight to Sounds and turn off everything, including the startup jingle. |
|
May 30 |
comment |
Why do sites split 'password' and 'username' retrieval into two separate operations? Must say I disagree with point #1. Adding a second step doesn't increase security when the email is still the only key you need. For #2 I believe we shouldn't design our UX based on our backend services. Solutions should be easy to use for end-users, not developers ;) As for #3, it's a bit of a difference case you describe. "Email" OR "Client ID AND Username" ask for two separate kinds credential. In my case I was asked for "Email" to get username and then "Email AND Username" to reset password. Or did you mean that the password was only reset when you provided "Client ID and Username"? |
|
May 30 |
comment |
Why do sites split 'password' and 'username' retrieval into two separate operations? That makes a lot of sense. I fully agree :) |
|
May 26 |
comment |
Why do sites split 'password' and 'username' retrieval into two separate operations? Hm, for me it's more like neither or both. Either I know both my username and my password because I've been using the site regularly, or I remember neither because it's been a while. And besides, the email should be a unique key anyways, so why ask for another detail? I just find that annoying. And also, the security question I gotta say is horrible... I usually put in an enormous hash of some sort as the answer and store it in KeePass :p (I do that for username and password, but I don't have all sites in there yet. Came over this issue with last.fm which I hadn't used in ages :) |
|
May 26 |
awarded | Student |