Viewing profile — zphds

In a high-stress environment, try to sleep well and eat healthy. Sleep is important!

oooh, as a software engineer, too low... too low... In our defense we do not have hundreds of millions of years of test driven development. :P

Same here. I had the same problem especially when dealing with problems that required me to go back and (un)learn stuff from scratch. I found that the greatest barrier to deal with…

`uncomplicate` libraries are awesome. Thanks so much for all this write up and putting out one of my favorite pieces of open source code. It's just so easy to rapidly iterate when …

I really dig the line protocol. Pretty simple. Any HA features? Sharding to look out in 2.0? Or is the general idea to set streaming relays of influxdb tsm's and treat HA as an L7 …

Same here! Trawling around forums and mailing lists to try and get Beryl working on my old desktop with a cheap-ass SiS integrated motherboard was quite a learning experience. Dead…

Yesterday, as I was taking a left turn with my motorcycle on a big intersection with flashing red signals, I couldn't help but wonder if I'd be able to communicate with self drivin…

How does Timescale solve the problem of retention. In InfluxDB, old data is thrown out at every tick as the retention window continuously rolls. In the world of Postgres, wouldn't …

Here's another similar library for Clojure. https://github.com/overtone/overtone Recommend this talk that made Music 'click' for me. Also fun if you are trying to read GEB and gene…

Haha! Thanks Mickey! Was a fun summer.

Mickey was my mentor and didn't get a chance to directly work with Sean and Harold. My project was to build APIs in Vala to control the hardware (volume, screen brightness, etc) th…

As a Google Summer of Code student way back in 2008 for Openmoko, this brought a lot of memories :).

Here's my understanding. Please correct me if I am wrong. Visualizing your program as a tree of values that are borrowed, owned, mutated through variables helps in reasoning about …

Note that keeping them separate has a benefit that when your 'Visualization' portal is down, your 'Alerting' systems are unaffected (and vice versa). Collectd, telegraf. etc, can b…

Great work! Including a way to set grace periods will be really useful to prevent flapping on the metrics. ex, 'Alert When CPU > 95% for 10m'

"Don't do that"

try!() is a macro. Hence all it does is take a given expression and expand the whole thing into a if-error-then-return block. I guess you say that it's an explicit return under the…

It's worth mentioning that try! is a macro that basically takes that expr and turns it to something similar to your go example.

We do this with telegraf + influxdb. It has support for tags in measurements where we add the release version among other metadata which we can then visualize in grafana with a sim…

'Pair Debugging' in my experience, is much more effective than Pair programming. And the constant "No, no that line"... Ugh!

> To clarify, we don't think of these specs as URLs That makes it a lot clearer. :). Looking forward to take noms for a spin soon.

But isn't ` / ` more or less similar to ` :: `? The only difference is the choice of a delimiter to disambiguate between a database and a dataset. For me, the first scheme is much …

Going through the SDK docs, why was a scheme like ' http://localhost:8000::people' chosen instead of the plain old ' http://localhost:8000/people' ? Are there any benefits? If yes,…

It definitely complements TPP. For me, Pragmatic Programmer was a better bed time book.

Add visualizations to DOM changes as well and you have a 'living' tree. ;)