network profile
| bio | website | davedelong.com |
|---|---|---|
| location | Cupertino, CA | |
| age | 26 | |
| visits | member for | 3 years |
| seen | Dec 27 '12 at 19:31 | |
| stats | profile views | 112 |
I'm Dave, and I love Objective-C.
My Projects:
- DDMathParser - a library for parsing
NSStringobjects as mathematical expressions and evaluating them - CHCSVParser - a library for reading and writing CSV files
- DDUnitConverter - a simple library for converting between units
- StackKit - a framework for using the StackExchange API.
If you think I'm a nice guy, check out my Amazon Wishlist! :)
My answers and opinions expressed here are my own and do not represent my employer's views in any way.
|
Jan 9 |
awarded | Critic |
|
Jan 5 |
comment |
API Inconsistencies Badge and User have a many-to-many relationship. Proper decomposition mandates that the way to model that correctly with a -to-one relationship on one side (which is what JSON can handle) is with another object, the Awarded Badge. I understand that text searching is expensive. It's just frustrating to think "ok, this had inname, that had inname, this should to. Wait, it doesn't? wtf?". |
|
Jan 5 |
comment |
API Inconsistencies (Comments in order) I'm willing to let things like hot, week, and month slide as sort values on questions, because there's no way for clients to duplicate the algorithm used to determine the "hotness" of a question. But I maintain that consuming the API is not the same thing as using the site. The API is for us developers, and thus it should be consistent. If I'm sorting by the score of a question, then don't call it votes, call it score. If I'm sorting by when an object was creation, don't call it creation, call it creation_date. The sort key should match the object field. |
|
Jan 5 |
comment |
API Inconsistencies @Jonathan. good point on award_count, but I definitely think total_award_count would be a better name. Making the semantic meaning of a field dependent on the context is a bad idea. Badges, IMO, shouldn't contain any user-specific information, because there's nothing inherent about a badge that has to do with a User. |
|
Jan 4 |
asked | API Inconsistencies |
|
Jan 4 |
comment |
Documentation sorted by return type Hooray for status-planned!!! |
|
Jan 4 |
comment |
filter=total is returning 0? Excellent, thank you! :) |
|
Jan 4 |
accepted | filter=total is returning 0? |
|
Jan 2 |
answered | Documentation sorted by return type |
|
Jan 2 |
comment |
Documentation sorted by return type And to emphasize how much I think this should be done, I will gladly put up the maximum bounty if people need convincing. |
|
Jan 2 |
asked | Documentation sorted by return type |
|
Jan 2 |
revised |
filter=total is returning 0? added 124 characters in body |
|
Jan 2 |
asked | filter=total is returning 0? |
|
Jan 2 |
revised |
StackKit: an API framework for Cocoa added 104 characters in body |
|
Dec 22 |
comment |
StackKit: an API framework for Cocoa Not actively, no. I've been thinking about resurrecting it for the 2.0 SDK, however. We'll see... |
|
May 22 |
awarded | Yearling |
|
Mar 28 |
awarded | Notable Question |
|
Feb 26 |
accepted | Timeline results contain redundant information? |
|
Feb 25 |
asked | Timeline results contain redundant information? |
|
Feb 22 |
revised |
Definitive on timeline_type? Signature |
