HN user

relate

276 karma

Research Scientist @ Google Zurich

https://scholar.google.com/citations?hl=en&user=Uhvyua4AAAAJ&view_op=list_works&sortby=pubdate

Posts3
Comments54
View on HN

I've done whiteboard only interviews, as well as shared doc/coderpad only, and I find both limiting. When thinking about the problem, it's great to have a whiteboard to sketch examples etc, but writing code is much easier with a text editor.

Recently I interviewed at Google, and they had no problem fulfilling my request to do both: sketch the solution approach on whiteboard and then write the code with a laptop.

I find it strange you mention transfer learning, since one of the reasons neural networks are so popular are because they tend to excel at it. Adapting (i.e. fine-tuning) networks trained on a task with a lot of data (e.g. image classification on ImageNet) to different tasks, such as image segmentation, has proven a very successful approach.

Could't they open source the design/implementation without a permissive licence? I.e. everyone could audit, but nobody could use it commercially.

Hi, I'm one of the authors. That is correct in a strict sense, but we wanted to focus on the more 'creative' part of logos rather than the text. GANs are known to struggle with high resolutions, but we note that we show higher resolution logos later in the paper (see page 12 and 15 e.g) which is trained on the smaller but higher-resolution version of our dataset.

I would have thought the same. However instead of adding random latency, one could have a buffer, that only allows a couple of fixed output rates (eg, 150,160,...,300 CPM), when typing. This would probably be quite annoying to type on though :-)

Thanks :-) The stack is based on:

* A Javascript based SPA with handlebars for template and leaflet.js for map

* Django + Postgres for the API

* Simple Vertex-Edge model of the train system, with shortest-path to estimate travel times (including walking distance)

-This is on our to-do list to improve, but we do this since querying all pairwise travel times from SBB/google would be too heavy.

* Numpy/Scipy for the machine learning

I'm one of the creators. This was built in 40 hours at Hackzurich 2015 (www.hackzurich.com) and combines the following:

    * The largest rent database of Switzerland 
    * A model of the train system of Switzerland
    * A simple recommender system
    * Google maps for name -> geolocation
    * OpenStreetMap for the map
There are some heavy calculations behind each query, so it takes about 15 sec to load. Furthermore, you need to like at least 3 apartments and dislike at least 3, before the system starts recommending.

Except that increased money supply means inflation which means that middle & upper class can buy less than before. E.g. someone with a medium salary might only get 20% higher income post-stipend but prices would rise more.

You took a poor example since pi is not known to be a normal number (see eg http://mathworld.wolfram.com/NormalNumber.html )

This number however is:

    0.0 1 10 11 100 101 110 111 1000 ...
This number contains all movies that have and will ever exist. However to specify where a 700mb harry potter movie is in this number, you'll need at least 700mb to represent the index. So in some sense harry potter 'exists' in this number - but in another sense its just a silly encoding method.

This is a common criticism. However, almost all ML methods have some built in heuristic choices, that are the result of finding something that both works and is mathematically nice. Each of these choices restricts us to some family of functions where it's hard to justify why it's really relevant to the problem at hand, e.g. convex loss functions (l1, l2, ..), convex regularizers (l1,l2,..), gaussian priors, linear classifiers, some mathematically nice kernel functions, e.t.c. In the end, people usually statistically estimate the performance of the methods and use what works.