There was an event when a startup I was at asked Basho (they were the company behind Riak db) about backing up our data. Backing was a little side-feature that was possible to rig up, but I recall they looked at this inquiry as if I had two heads -- as if to say, it's replicated, why jump the shark? There was a bug with one of the Riak releases, and all the data was lost. (When we scaled up with this buggy Riak release, the empty node assumed master roll, and all the child nodes went, ah... the new state has no data, let's all delete records 0..k. Fun times.)
As someone who spent the weekend figuring out `flexbox' to align copy around a webpage, after years of floating divs and pulling my hair out, I can appreciate this video. Creative destruction is an awe-inspiring, yet wistful force of nature.
I think it’s great to see why web is the way it is. These people were the web devs of their days desiging lead based layouts. Imagine having to roll back a change mid print.
Without too much effort, I keep a NOTES file in each project directory. I keep it out of source-control. Anything that is worth preserving (backed up and checked in) goes in README. I also use a file called SCRAP for ephemeral matters, again, in each project root, not checked in. A great pattern that has served me well.
Great system. I do something similar by creating a "_misc" folder out of source control. The "_" is so that alphabetically it is listed at the top and not intermixed with actual project folders.
I use it to store code snippets, prototyping scripts, misc notes that don't fit in my main folder system for notes/todos, query output, and other random items. If the _misc/ directory becomes too cluttered , then I throw most of the items into an "archive_$DATE" sub-directory (inside _misc).
I'm still working on a broader, general organization system for notes, documents, links, todos, etc... (lots of good ideas in this thread). But this works well for more ephemeral project-specific stuff.
In using cowboy directly, it would be a mistake (at least from personal experience) to rely of cowboy for anything other than your api endpoints and/or dynamic templates. Static assets, including html, are best served via nginx, with cowboy serving requests to your application. I've never had a cowboy + OTP project not lean on nginx in some way (yet).
Long-time vi[m] user, and always learning/amazement. This very morning I learned about the `-c` flag. So, `vim -c "set spell" my-misspelled-file.txt` starts up vim with a given setting.
When you consider the array of different exploits the thieves had to use to steal this guy's bitcoins, I think that this is a rare case where they are accurately described as hackers. But in the more common cases, such as Podesta's email account getting spearphished, you're correct that calling the perpetrators hackers is an insult to hackers.
