333 reputation
16
bio website mahemoff.com
location London, United Kingdom
age
visits member for 2 years, 10 months
seen Jul 18 at 15:08

My last permanent role was on Google's Chrome team, helping external developers learn and use HTML5 and Chrome tools. I'm currently baking node apps.

I'm an Aussie in London.


Jul
13
comment How to handle divide by zero in a language that doesn't support exceptions?
"So far, we've been unsuccessful." Yes, there has been plenty of hype - "Finally we have a language managers can use and no longer need programmers. Meet COBOL". However, saying we've been unsuccessful depends on your definition of a programming language and the nature of the users. Domain-specific languages have been successfully introduced for non-programmers and even tools like Yahoo! Pipes and IFTTT are a form of programming (unless we stick to a rigid circular definition...they certainly accomplish what might otherwise require a "program" to do).
May
19
accepted A RESTful way to verify server state
May
19
comment A RESTful way to verify server state
Yes I did immediately update this question to clarify it. Please re-open.
May
4
revised A RESTful way to verify server state
update link
May
4
revised A RESTful way to verify server state
added 104 characters in body
May
3
asked A RESTful way to verify server state
Jan
21
awarded  Commentator
Jan
21
comment Versioned Resources to Improve Cacheability
Close. The possible alternatives I'm avoiding are (a) an expensive monolithic 200 and (b) a small 200 (like the one here) followed by N more 200s or relatively expensive 304s (because the comparison can't be edge-cached).
Jan
19
comment Versioned Resources to Improve Cacheability
I may be misunderstanding, but the HTML comment at the end was more about an analogy to the main idea, which is about a JSON API. The idea is to keep the personal, non-cacheable, part minimal, and the public cacheable stuff can sit on the edge. All this data changes quite often, so if it was all fetched in a single big response, that response would be new every time.
Jan
11
revised Versioned Resources to Improve Cacheability
added 495 characters in body
Jan
9
accepted Versioned Resources to Improve Cacheability
Jan
8
revised Versioned Resources to Improve Cacheability
deleted 3 characters in body
Jan
8
comment Versioned Resources to Improve Cacheability
There's a slight risk of a race condition where a topic is updated just after the user JSON is sent, but it shouldn't be a problem to most applications if the previous version of the topic is retrieved as it would have been used a minute earlier anyway.
Jan
8
comment Versioned Resources to Improve Cacheability
For now, I'm mainly thinking about the N+1 polling scenario, ie where the child resources are immediately sync'd after the parent resource, so there's no risk of stale resources being fetched.
Jan
8
revised Versioned Resources to Improve Cacheability
added 220 characters in body
Jan
8
asked Versioned Resources to Improve Cacheability
Oct
10
awarded  Yearling
Sep
27
awarded  Scholar
Sep
27
accepted Random Cache Expiry
Jul
30
revised What to answer to a customer who asks which one of two equivalent technologies must be used?
copyedit