While I try to find a new home for defunct blog, I will be blogging here.
This blog has moved to randommeasures.com; please update your bookmarks.
It might be a little hasty of me to try and figure out the future of this blog given that I restarted posting here only two days ago, but there are some things that I find restrictive about wordpress.com sites:
- the inability to have a full implementation. The default only comes with the amsmath, amsfonts and amssymb installed and that is not likely to be enough in the long run. On the other hand, WP QuickLaTeX, for wordpress.org, provides fully featured , including support for TikZ and pgfplots, which I find extremely impressive.
So, over the next couple of days, I will be evaluating a couple of options to move this site back to self-hosted, including:
- dedicated AWS instance
I am not a big fan of the hosting providers because I always feel confused by their hosting plans and the control panels that they offer to customers — it is like learning a whole new system just to be able to host a website with that hosting provider. The other thing that worries me about hosting services like GoDaddy is that their business practices are not always transparent — they tend to have hidden costs, auto-renewals built in, and also clauses that do not allow domain names to be easily applied to sites hosted elsewhere. This might be FUD, but removing it would need a substantial amount of investment in reading up and finding out all the pitfalls of hosting services like GoDaddy.
However, given that all I plan to do is to only host a WordPress blog, I feel that going the AWS route might be too costly. I also know that if I go the AWS route, then I will be tempted to move the entire site to Django or Flask, and that is not a time and effort investment I want to make right now. Even so, setting up and maintaining a wordpress blog on AWS takes some work, and is not costly. There is the option of reserving an instance for a year at $0.009 an hour, but that would be a t2.micro instance, and I am not sure that it would suit the purpose of serving up a website. There are some options if you want to get rid of a reserved instance mid-way through its tenure, and also there is the possibility of upgrading an instance if the load becomes too high, but both of those options require work.
So I think I will sleep on this decision for a few days. I am not going to be making a decision on this until one of GoDaddy or FatCow provides me with an email discount coupon anyway, which they do without fail every month.
This blog used to be previously called Large Deviations, and was self-hosted, although I also like Information Matrix and Random Measures as names for a blog that is largely focused on statistics and data science.
Not being a gamer, I was not aware that some gaming keyboards, in particular, my recently acquired Cooler Master Quickfire Rapid I, have a Windows key lock that prevent exiting from gaming mode in case that the Windows key is pressed accidentally. I use the Windows key quite frequently on Ubuntu to emulate the Windows “Snap to Sides” feature that maps Ctrl+Win+RightArrow to snap a window to the right of the screen, for example. I was not able to figure out why it was not working with my new keyboard. Turns out the Windows key lock is turned on by default, and can be turned off using Fn+PrtSc.
I spent some amount of time trying to figure out if I could get Google Analytics to track the traffic on my WordPress.com account, but it seems that this is only a feature available using WordPress Business plan, or if I migrate the site to WordPress.org.
I also spent some time figuring out how to set up a new account and property within a Google Analytics account. And then there is the question of configuring useful views of the data within a property (Account > Property > Views). For now, I have created two accounts within my GA account, one for my main site and the other for all the blogs I have on services such as tumblr and this site on WordPress.com.
I googled and put together a lightly curated set of links that I want to read to collate a strategy on how to prepare for a data science interview.
- http://career.guru99.com/top-50-interview-questions-on-machine-learning/: This link appears to have random questions, and the answers lack any depth whatsoever, but it appears to cover topics that are unlikely to come up in interviews, would be good to know about superficially.
- http://robertheaton.com/2014/03/07/lessons-from-a-silicon-valley-job-search/: This is not about machine learning in particular, but I liked the detailed writeup on how to structure a job search.
Since I will be answering questions on programming using Python, here are some links on Python programming interview questions:
I must admit that I don’t really like the look of some of these links as they seem too focused on syntax or clever and compact ways of achieving trivial things, and not on the language big picture, architecture of applications or actually solving difficult problems. In addition, these don’t cover some of the core packages that a data scientist should know, such as NumPy, SciPy or scikit-learn, and to a lesser extent pandas and statsmodels.
For reference, here is my implementation of FizzBuzz.
for x in range(101): if x % 15 == 0: print("FizzBuzz") elif x % 3 == 0: print("Fizz") elif x % 5 == 0: print("Buzz") else: print(x)
This is the vanilla implementation that can be found all over the internet, and the trick really is to handle division modulo 15 first rather than last, as it reads in the question. Everything else is standard syntax. At some point, I have implemented it using generators, but I can’t find that solution, and I don’t want to get distracted from pulling together links for my interview prep.
Over the next couple of days I intend to work through these links, and I will see if I can refine down to a core strategy that I can use to preapre and review before interview. I also intend to blog about some of the peripheral aspects of job search such as writing a good resume and cover letter, interview etiquette and searching for relevant jobs.