< ^ txt
Sun May 7 08:26:09 EDT 2017
Slept from eleven to eight. Woke briefly around four.
High of fifty four and sunny today.
Goals:
- Work on Faux Bat
Done.
- Play with D&D saltbox
A bit.
- JMAP?
Done.
http://jmap.io/
"JMAP is intended to be a new standard for email clients to connect to mail stores. It therefore intends to primarily replace IMAP + SMTP submission. It is also designed to be more generic such that it can be extended with contacts, calendars in the future (replacing CardDAV/CalDAV). It does not replace MTA-to-MTA SMTP transmission."
Run JMAP over https.
https://cyrusimap.org/imap/developer/jmap.html
Watched Train to Busan on Netflix.
Zombies on a Korean bullet train.
Good. A solid film and a fun zombie flick.
Really makes you hate some of the characters and love others.
Maybe I'll eat more vegetarian.
https://paulgorman.org/misc/cooking/diet.txt
I bought TumbleSeed for the Switch.
A "rolly roguelike". A novel, relaxing game.
Vacuumed, washed dishes, took out the trash, a few minor chores.
http://mcfunley.com/choose-boring-technology
> Let's say every company gets about three innovation tokens. You can spend these however you want, but the supply is fixed for a long while. You might get a few more after you achieve a certain level of stability and maturity, but the general tendency is to overestimate the contents of your wallet. Clearly this model is approximate, but I think it helps.
> If you choose to write your website in NodeJS, you just spent one of your innovation tokens. If you choose to use MongoDB, you just spent one of your innovation tokens. If you choose to use service discovery tech that's existed for a year or less, you just spent one of your innovation tokens. If you choose to write your own database, oh god, you're in trouble.
> Any of those choices might be sensible if you're a javascript consultancy, or a database company. But you're probably not.
> What counts as boring? That's a little tricky. "Boring" should not be conflated with "bad." There is technology out there that is both boring and bad [2]. You should not use any of that. But there are many choices of technology that are boring and good, or at least good enough. MySQL is boring. Postgres is boring. PHP is boring. Python is boring. Memcached is boring. Squid is boring. Cron is boring.
> The nice thing about boringness (so constrained) is that the capabilities of these things are well understood. But more importantly, their failure modes are well understood.
> It is basically always the case that the long-term costs of keeping a system working reliably vastly exceed any inconveniences you encounter while building it. Mature and productive developers understand this.
> One of the most worthwhile exercises I recommend here is to consider how you would solve your immediate problem without adding anything new. First, posing this question should detect the situation where the "problem" is that someone really wants to use the technology. If that is the case, you should immediately abort.
Thirty minute walk in the afternoon.
Saw a hawk doing aerobatics, cardinals, red-winged blackbirds.
The Canada goose that has been nesting atop the carports has hatched her chicks: five yellow fuzzballs.
They've been promenading up and down the metal roof, feeding on the moss and tiny shoots growing in its crevices.
Breakfast: tomato, carrots, coffee
Lunch: left-over pizza
Dinner: tomatoes, green beans, macaroni, beer
< ^ txt