This looks like a good idea: Introducing State Partitioning.
Some thoughts on Andriod app design: Everything I’d do differently if I could go back and rewrite my Android app today.
Had a quick read of Practical Color Theory for People Who Code.
Over on the StackOverflow blog: Best practices for REST API design. Some of it is good but I disagree with a bunch of things. I made some notes:
* Use singular https://www.example.com/comment/list Not: https://www.example.com/comments * Use multidimensional selectors, not path/hierarchical selectors: https://www.example.com/comment/list?artist=nirvana&album=nevermind Not: https://www.example.com/album/nirvana/nevermind/comments * Use noun/verb format: https://www.example.com/comment/list https://www.example.com/comment/register https://www.example.com/comment/edit/54688 https://www.example.com/comment/view/54688 https://www.example.com/comment/reply/54688 * The [ noun, verb ] pairs map to Facilities for implementation: [ comment, list ] => CommentLister [ comment, edit ] => CommentEditor [ comment, view ] => CommentViewer Facilities have submit/render functionality and round-trip view state. * HTTP success 30x's not 2xx's. * Include a 'submission ID' on <form> elements for idempotent operations * GET and POST only, don't CRUD URLs, rather invoke business processes
Today I discovered: noyaml.com. Ah, sarcasm.
Oooh. I like JWCC. Pronounced jay-wok?
Today I read An incomplete list of complaints about real code. I don’t agree with most of her conclusions, but they were interesting to read and consider.
In Time for Next-Gen Codecs to Dethrone JPEG various graphical formats are compared and contrasted.
So apparently I have Dyshidrotic Eczema on my hands. The good news is that it’s not contagious. The bad news is that it is unsightly and can be a bit itchy.