This post sat in my drafts for over a year now. The contents yield no result, but I hope this might inspire you to do something crazy with your day. Honestly, this idiot whom ran over a cyclist inspired me to publish this post.

Last week's video highlighted the dangerous design of NYC bike lanes. Today a cyclist in a bike lane (yes, that's a bike lane) sandwiched between two driving lanes was rear-ended by a van. #VisionZero appropriately describes the street lighting. @StreetsblogNYC @TransAlt @NYC_DOT pic.twitter.com/L1XvWf7YY6

— Jessica (@Thund3r_H4wk) November 12, 2019

One of the favourite API design techniques I have applied a lot lately is to use so called “cursors” throughout API’s to improve its consistency.

Summarized; use cursors when:

• You mix multiple different types of identifiers throughout your API (strings, integers, guid’s)
• You do not want to imply order when there is none

Opposite, feel free to ignore cursors when:

• You consistently apply a single identifier type throughout the whole API/backend, and do not see that changing in the future.
• You do not care about API consistency