Eric Anastas

San Francisco, CA

ericanastas.com

Age: 34

Feb
1
awarded Notable Question
Jan
29
awarded Popular Question
Jan
20
awarded Famous Question
Jan
20
accepted Design pattern for including errors with return values
Jan
20
accepted Is there a design pattern for a repository that always returns a single object?
Jan
4
awarded Informed
Dec
30
awarded Famous Question
Dec
12
asked Is there a design pattern for a repository that always returns a single object?
Dec
2
awarded Notable Question
Nov
15
awarded Good Question
Nov
11
awarded Notable Question
Oct
31
awarded Yearling
Oct
31
awarded Autobiographer
Oct
26
comment Design pattern for including errors with return values
This is a good option, but unfortunately I'm rarely working with single objects. The most typical use case is to compare a number of object exports from two separate files. I'm also almost always serializing the returned object to JSON, and dealing with that JSON later. So storing the errors separately would be problematic.
Oct
26
comment Design pattern for including errors with return values
Do you happen to have a link to a blog post or presentation where Martin talks about this?
Oct
26
asked Design pattern for including errors with return values
Oct
11
awarded Student
Oct
11
asked Is there a benefit to using hadoop with only one node?
Sep
26
awarded Custodian
Aug
13
comment Using JSON.Net to extract a generic tree structure from instances of my classes
JObject.FromObject() seems to be what I was looking for, can some one post an actual answer so I can mark it as correct?
1 2 3 4 5