Some interesting thoughts on How to Efficiently Choose the Right Database for Your Applications.
Today I enjoyed reading Build tools around workflows, not workflows around tools. Taken with John Romero’s advice to build your own tools I feel I am on the right path with some of my current projects.
Today I stumbled upon A Vim Guide for Advanced Users. Learned a trick or two, but it’s still a long road ahead for me.
I just wanted to get something that I’ve thought for many years on record, because I don’t think I’ve ever had the chance to discuss it much before, but I believe JSON web services (“REST APIs”) and web applications should deal only in two HTTP verbs, being: GET and POST. You use GET for queries and you use POST for submissions. All POST operations go through business logic for particular services and CRUDing URLs is a supremely bad idea, in my opinion. Just wanted to get that on record. Thanks. p.s for web applications you should 3xx on success, not 2xx on success; what you do for JSON web services is up to you, but for those 2xx is probably fine.
Found an article: How to set up a basic jump host with SSH in Linux.
Some discussion about Plain Text Protocols. Who doesn’t love plain text? :)
A great article on the complexity of file systems: Files are hard.
Check out https://free-for.dev/ for a list of services which are free for developers.
Some notes from Mike Bostock about what he’s learned from the D3.js project over the years: 10 Years of Open-Source Visualization.