DeeKaying @ Nettle

Divya and I had some free time. We spent it making this crazy free hand drawing. We did it turn by turn, each putting in a stroke or two from a blue pen. It's kind of reflective of the times. :)

Today's my last working day at Google... Hi folks,    After 4 years, 1500+ CLs, 50 design docs, 15 major launches and 2 amazing teams, it is now time for me to hang my boots at Google. It's been an amazing journey and a great feeling to have touched the lives of millions / billions of people and I'm sad for having to leave all of this behind. I have learnt a lot from all of you: about life, about people and about code. It's been exhilarating and instructive and I'm very happy to have been a part of it.  Google is an amazing company, possibly a company that comes once in a generation. However, a new future awaits me at LinkedIn (just down the street) with different problems to solve and new people to meet. I hope the future for all of you will be just as bright. Wishing you the best. Do stay in touch! I'm sure our paths are likely to cross again another day. LI:  https://www.linkedin.com/in/divyekapoor FB:  https://www.facebook.com/divye.ka...

I recently tried hosting a static site on Github with a custom domain. Github's docs on getting this done are unnecessarily confusing. Here's a quick snapshot of how to get this done quickly: I'm going to use the zigndog.com Github repo as an example. The custom domain is zigndog.com . You can just change the values in the 2 bash variables below and execute the same sequence of steps. Verify that everything worked by visiting your website published on Github: eg. http://divyekapoor.github.io/zigndog.com/ for the zigndog.com repo. If you have a different repo name, just use that along with your username: eg. http://${GITHUB_USER}.github.io/${REPO_NAME} Next, visit your domain's DNS registrar and add a DNS A record pointing to Github. The Github static IP addresses are detailed here:  https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/ . For reference, at the time I did my configuration, they were: 192.30.252.153 192.3...

India's had some terrible inflation lately, I took some time to figure out the cumulative 2-year, 3-year, 5-year and 10-year cumulative price index (CPI) based inflation figures in the cumulative price index (CPI) over the past 56 years. These numbers are based on a dataset from inflation.eu. Here are the numbers: annual inflation (dec vs. dec) inflation 2-year trailing inflation 3-year trailing inflation 5-year trailing inflation 10-year trailing inflation CPI India 2014 5.86% 15.53% 28.43% 49.72% 124.06% CPI India 2013 9.13% 21.32% 29.19% 62.60% 119.66% CPI India 2012 11.17% 18.38% 29.60% 63.45% 108.77% CPI India 2011 6.49% 16.57% 34.03% 55.13% 93.80% CPI India 2010 9.47% 25.86% 38.07% 55.19% 91.38% CPI India 2009 14.97% 26.12% 33.07% 49.66% 80.91% CPI India 2008 9.70% 15.74% 23.30% 35.09% 58.09% ...

A beginning programmer writes her programs like an ant builds her hill, one piece at a time, without thought for the bigger structure. Her programs will be like loose sand. They may stand for a while, but growing too big they fall apart. Realizing this problem, the programmer will start to spend a lot of time thinking about structure. Her programs will be rigidly structured, like rock sculptures. They are solid, but when they must change, violence must be done to them. The master programmer knows when to apply structure and when to leave things in their simple form. Her programs are like clay, solid yet malleable . -- Master Yuan-Ma,  The Book of Programming Found this on the web... it struck a chord. :)

Very recently, I've started working on a hobby project on the Raspberry Pi . One of the first things I've noticed though is that the Pi isn't very stable (especially if it has a Wolfson Audio Card attached to it). Frequently (as in somewhere every 24 hours or so) the entire system bricks with a Kernel panic. Now, that isn't a great position to be in if you're looking to the Pi for some stability for embedded applications. To figure out how frequently the Pi fails on me, I've resorted to a simple script that I run every minute in a crontab: Script check_health.sh: #!/bin/bash echo `date +%F-%H:%M:%S` Server up Crontab (runs the script every minute): $ crontab -e * * * * * /home/pi/healthz/check_health.sh >> /home/pi/healthz/healthz.log This simple mechanism is a quick way to figure out when your Pi crashes and how long it typically stays up. Simple and elegant. Maybe this will be useful to you too in some other project that you're working ...

Lost my wallet yesterday. If anyone finds it, please contact me using the details on the left side of this page...