meta user
network profile
| bio | website | drowtales.com |
|---|---|---|
| location | Latvia | |
| age | 28 | |
| visits | member for | 2 years, 7 months |
| seen | Mar 12 at 11:12 | |
| stats | profile views | 25 |
Just your average everyday programmer.
|
Nov 7 |
awarded | Yearling |
|
Nov 1 |
revised |
Is there a limit on the number of threads that can be spawned simultaneously? added 729 characters in body |
|
Nov 1 |
answered | Is there a limit on the number of threads that can be spawned simultaneously? |
|
Oct 21 |
awarded | Popular Question |
|
Oct 11 |
awarded | Popular Question |
|
Sep 2 |
awarded | Good Question |
|
Aug 24 |
comment |
Should a stack trace be in the error message presented to the user? @MarkBooth - a unique ID serves the same purpose, but I suppose that adding time won't hurt either. Thanks! :) |
|
Aug 24 |
comment |
Should a stack trace be in the error message presented to the user? @ChrisF - Way ahead of you :) |
|
Aug 23 |
comment |
Should a stack trace be in the error message presented to the user? @AviD - Maybe you can point me to some resources that explain how a stack trace can be dangerous? I'm ready to accept that, but I want something more than the general priciple of "only show what you need to". |
|
Aug 23 |
comment |
Should a stack trace be in the error message presented to the user? @AviD - in truth, I don't know what they analyzed, but from some reports I saw it seemed like a black-box test to me. To be honest, I don't want to work against them. Indeed, I did like the news when I heard them. But this particular "vulnerability" of theirs seems silly to me. In every security decision you have to weigh the threat reduction against the usability reduction. In this case I think it reduces the usability a lot more than it improves security. |
|
Aug 23 |
awarded | Nice Question |
|
Aug 23 |
comment |
Should a stack trace be in the error message presented to the user? I like your answer because it presents a "middle road" - don't show, but make the looking-up of exceptions easy. I'll try to push for that now, I hope that they will agree. Thank you! |
|
Aug 23 |
accepted | Should a stack trace be in the error message presented to the user? |
|
Aug 23 |
asked | Should a stack trace be in the error message presented to the user? |
|
May 25 |
comment |
Checking for emptiness of collections with (in)equalities - what's the best practice? Just to note - IsEmpty() is an elegant solution indeed, but it's not so elegant if you're using a standard data structure (like an array) which does not have this method. You can, of course, write one yourself, but the code becomes much longer than the simple .Length==0. Arguably, that also hurts readability. |
|
May 25 |
revised |
Checking for emptiness of collections with (in)equalities - what's the best practice? added 431 characters in body |
|
May 25 |
comment |
Checking for emptiness of collections with (in)equalities - what's the best practice? As I commented to @leftaroundabout - naturally, if getting .length is a lengthy operation, or other special conditions apply, then this is the wrong approach altogether. This question was for simple collections where getting length is a O(1) operation. |
|
May 25 |
comment |
Checking for emptiness of collections with (in)equalities - what's the best practice? @leftaroundabout - Obviously, I was talking about the typical everyday cases when obtaining .Length is a O(1) operation. If special conditions apply to getting it, then this is all irrelevant. |
|
May 25 |
accepted | Checking for emptiness of collections with (in)equalities - what's the best practice? |
|
May 25 |
comment |
Checking for emptiness of collections with (in)equalities - what's the best practice? Oh, I'm not thinking hard. It's just a thought that struck me as I was doing work today, and since I couldn't decide on my own in a few moments, I posted it here. :) |
