This week I found an amazing article on hexagonal grids which I strongly recommend for all game developers. If you only read one link from this week’s list, make it that one. And be sure to check out the hexagon Haskell library by the same author.
Lately I have been doing more work in Python and PHP, so this week you will see more links for those two languages than anything else. As always I hope you find something useful and/or interesting!
Earlier this week I saw the following comment:
HTTP defines a limited set of verbs, but APIs should be allowed to define their own verbs. Oftentimes, "get" or "post" or "delete" simply isn’t what you really. Then one of the following usually happens – either we use an HTTP verb that doesn’t accurately describe what’s happening, or we put the real verb somewhere else (e.g. in the URI or JSON body).
It is true that HTTP defines a small set of verbs, or ‘methods’ in the words of the standard. But developers can define their own, yet I rarely see anyone take advantage of this. So today I will show you how and why you may wish to do so.
Note: I’m not going to show any actual code in this article, under the assumption that you know how to use the language and web framework of your choice in order to return HTTP headers in requests, handle requests based on specific HTTP methods, and so on.
One of the more uncommon aspects of the Python programming language is how it allows
else blocks in multiple types of compound statements. Python has the classic
if-else, but it also has a
for-else construct. And today I want to show you a simple use for it.
Today I want to share with you some of my personal hydras, i.e. groups of key-bindings for use with the Hydra package for GNU Emacs. Along the way I’ll also be referencing a variety of useful packages.