373 reputation
112
bio website androiddesignpatterns.com
location Manhattan, NY
age 23
visits member for 2 years, 5 months
seen Dec 8 at 14:24

Author of Android Design Patterns & 2048++


I'm a recent graduate from Carnegie Mellon University with a strong interest in application frameworks, GUI toolkits, the Go Programming Language, and open-source software.

I am currently a Google engineer working on Android Studio.

Most of my time on StackOverflow is spent answering questions under the , , and tags.

Sites:


Jul
2
awarded  Curious
Jul
25
awarded  Yearling
Jun
1
awarded  Self-Learner
Oct
7
revised API docs titled “v2.0”; should be “v2.1”
edited title
Oct
7
accepted API docs titled “v2.0”; should be “v2.1”
Oct
7
comment API docs titled “v2.0”; should be “v2.1”
Yeah... I mean that's what I figured. That's why I tagged my question under "bug". Hopefully someone will see this and update the docs, because it's not readily obvious from the documentation that v2.1 has been released.
Oct
6
asked API docs titled “v2.0”; should be “v2.1”
Aug
31
comment Java wrapper for the Stack Exchange API 2.0?
@jjnguy I can help out if you need me... you're one of the people who actually wrote StackWrap4J, correct?
Aug
31
awarded  Commentator
Aug
31
comment Java wrapper for the Stack Exchange API 2.0?
@jjnguy Not 100% sure (and last time I checked they hadn't even ball-parked it). API 2.0 has out of beta for about 6 months now so I'd guess sooner rather than later (?). From what I can tell 3.0 is going to be mostly an extension of 2.0 (i.e. the addition of write-only API calls). That said, there are some parts of the documentation that say things like "this could be changed at any time" etc. and I'm not always certain which parts should be trusted.
Aug
31
comment Java wrapper for the Stack Exchange API 2.0?
@jjnguy In all honesty, I didn't really end up modifying/extending all that much (I was mostly concerned with badges, inbox items, notifications, etc.). I do feel like I have a pretty good understanding of how StackWrap4J works though (I looked through probably 80% of the source code), so I'd be able to contribute I think. I would hate for v3.0 to come out though and potentially ruin any work we put into v2.0... what would be the best way to write the library given that it will eventually need to be brought up to 3.0 standards?
Aug
15
comment Is the “link” URL enough to uniquely identify an “inbox_item”?
OK, that clears up a lot of confusion... my next question was going to be are inbox items ever change once they're created. Thanks!
Aug
15
accepted Is the “link” URL enough to uniquely identify an “inbox_item”?
Aug
14
comment Add message ID to inbox items
What happens when a question is migrated to a new site? Won't the link change in this case?
Aug
14
revised Is the “link” URL enough to uniquely identify an “inbox_item”?
added 98 characters in body
Aug
14
asked Is the “link” URL enough to uniquely identify an “inbox_item”?
Aug
14
comment When will the “site” field be absent from an “inbox_item”?
One last question... when the "site" is down, shouldn't the result be an error of some sort? Why is it that the site field is absent instead?
Aug
14
comment When will the “site” field be absent from an “inbox_item”?
OK, that makes sense. Thanks for clarifying!
Aug
14
accepted When will the “site” field be absent from an “inbox_item”?
Aug
13
asked When will the “site” field be absent from an “inbox_item”?