Time to switch to using the #python SDK! In the meantime, no new media uploads

Media directory backups have been failing since the 17th due to exceeding max attachment size. No alerts. #fail >>> SIZE=55759470 <<< 552 5.3.4 Message size exceeds fixed limit

Switching from yui-compressor to yuglify saved me 1KB on bootstrap.js and 30 bytes on bootstrap+hyperbola css #performance

With this latest release, hyperbola has surpassed 500 commits! #win https://github.com/hyperbola/hyperbola/tree/2015-11-21-lifestream-template-refactor

lifestream template refactor didn't yield any #performance wins, but the code is much cleaner now. #win

Front page warm nginx latency is 12ms; contact page is 20ms #performance

Current prod gunicorn time (measured at nginx) for the lifestream index page is 70ms with no partial caching and 40ms with the sidebar cached #performance

Tested rendering the lifestream index with all 3 interpreters. pypy is slower than python2.7 by 2x. python3.5 is faster than python2.7 by 2x. #performance

Local development lets me run cool experiments. I have python2.7, python3.5, and pypy virtualenvs.

Sped up the lifestream page by 30ms by caching the archive sidebar. More template speedups to be had by switching to python3 (str to unicode coercion in python2) #win #performance

Woo! I can run hyperbola on my mac. Local development! #win

Even better: precompiling app/hyperbola to pyc and getting to keep the deployment read-only. better #win

gunicorn workers get warm quicker now that I've allowed gunicorn write access to a deployment's app and virtualenv dirs #win

Root fs usage is down to 3.5G.

Finally started cleaning old deployments. After each deploy, my deploy script removes all but the latest 5 deployments for a given env. https://hyperbo.la/lifestream/352/ can rest peacefully.

90mbps upload to Box from the corporate network is pretty nice when backing up my photos (all 25GB of them).

OG status: https://github.com/hyperbola/hyperbola/tree/og-hyperbola-v1

Did some archeology today to unearth an ancient version of hyperbo.la. Same color scheme as today. Yes, there was an assets domain. Had to do forensic analysis to reconstruct the index.html.

It continually amazes me at how much conflict is solved with "assume good intent."

Added a post-commit hook to my gollum wiki today to do a pull/push. Changes instantly synced to #github. No more stupid 5-minutely cron. #win

I feel like my #django site is futureproofed for at least the next two minor version upgrades now. Just converted a ton of render_to_response snippets to the new render hotness. Even feels faster.

Despite being stable, #django deprecates frequently. What they deprecate tends to have been the recommended way of doing it circa 1.4 ... feels like they are slowly rewriting everything.

15 commit night on hyperbola, 5 on hyperbola-tools, and 12 on my dotfiles. Mostly code and style cleanups, some correctness fixes.

Having a linter is so awesome. IntelliJ rocks. #win

Next major project is migrating to a new VM. 32-bit Ubuntu 12.04 is getting long in the tooth. I have eyes on 64-bit #Debian 8 and a shiny new #linode with 2GB of RAM

Last bits of major feature work were bootstrapifying several pages and adding automatic deployment (June 2014)

Just realized that hyperbo.la has been in maintenance mode for a while. Last few projects: upgrade to django 1.8, upgrade to django 1.7, upgrade vendored dependencies (bootstrap, retinajs).

#puppet is more fun when you know what you're doing.

I bought IntelliJ Ultimate and it has already been decently valuable: https://github.com/hyperbola/hyperbola/pull/28 ... fixing lots of warnings #win

It only took a debian VM and 4 hours of my time to reformat two new USB keys. #fail

Fixed a long outstanding bug in how the sidebar on the lifestream calculated monthly post counts #win Tickled by the upgrade to #django 1.8 which caused them to all display as 1. #fail

Finally upgraded to #django 1.8. Only an 8 commit adventure