hafabnew

Thread.com (YC S12) - Software engineer who loves product (Python/Django) London, England.

https://www.thread.com/jobs

We're a startup trying to reinvent retail so men can dress well without being subject to the horrors of the high street or having to trawl through millions of items online. We do this using a combination of powerful algorithms and human stylists.

You'd be joining a small, highly technical team with a ton of startup experience (the founders have started and sold 2 companies before). You'll be one of the first technical hires and get to build and own huge parts of the product and work on the core algorithms.

One of our ancillary goals is to build one of the best engineering cultures anywhere, and we'd love you to help us do that. We launched in October and user and revenue numbers are scaling extremely quickly. We're backed by a collection of the top investors from London and Silicon Valley as well as Y Combinator.

We're especially interested in people who are interested in founding their own startup one day. We view working at Thread as a founder bootcamp where you'll learn about all parts of starting and growing a startup.

Want to learn more? Check out https://www.thread.com/jobs and you can see some of our code at http://dev.thread.com/

Thanks!

Thread.com (YC S12) - Software engineer who loves product (Python/Django) London, England.

https://www.thread.com/jobs

We're a startup trying to reinvent retail so men can dress well without being subject to the horrors of the high street or having to trawl through millions of items online. We do this using a combination of powerful algorithms and human stylists.

You'd be joining a small, highly technical team with a ton of startup experience (the founders have started and sold 2 companies before). You'll be one of the first technical hires and get to build and own huge parts of the product and work on the core algorithms.

One of our ancillary goals is to build one of the best engineering cultures anywhere, and we'd love you to help us do that. We launched in October and user and revenue numbers are scaling extremely quickly. We're backed by a collection of the top investors from London and Silicon Valley as well as Y Combinator.

We're especially interested in people who are interested in founding their own startup one day. We view working at Thread as a founder bootcamp where you'll learn about all parts of starting and growing a startup.

Want to learn more? Check out https://www.thread.com/jobs and you can see some of our code at http://dev.thread.com/

Thanks!

Thread.com (YC S12) - Software engineer who loves product (Python/Django) London, England.

https://www.thread.com/jobs

We're a startup trying to reinvent retail so men can dress well without being subject to the horrors of the high street or having to trawl through millions of items online. We do this using a combination of powerful algorithms and human stylists.

You'd be joining a small, highly technical team with a ton of startup experience (the founders have started and sold 2 companies before). You'll be one of the first technical hires and get to build and own huge parts of the product and work on the core algorithms.

One of our ancillary goals is to build one of the best engineering cultures anywhere, and we'd love you to help us do that. We launched in October and user and revenue numbers are scaling extremely quickly. We're backed by a collection of the top investors from London and Silicon Valley as well as Y Combinator.

We're especially interested in people who are interested in founding their own startup one day. We view working at Thread as a founder bootcamp where you'll learn about all parts of starting and growing a startup.

Want to learn more? Check out https://www.thread.com/jobs and you can see some of our code at http://dev.thread.com/

Thanks!

Not to sound too much like an Amazon product page, but if you like this, you'll probably quite like "Unix for Poets" - http://www.lsi.upc.edu/~padro/Unixforpoets.pdf . It's my favourite 'intro' to text/data mangling using unix utils.

Thread.com (YC S12) - Software engineer who loves product (Python/Django) London, England. https://www.thread.com/jobs

We're a startup trying to reinvent retail so men can dress well without being subject to the horrors of the high street or having to trawl through millions of items online. We do this using a combination of powerful algorithms and human stylists.

You'd be joining a small, highly technical team with a ton of startup experience (the founders have started and sold 2 companies before). You'll be one of the first technical hires and get to build and own huge parts of the product and work on the core algorithms.

One of our ancillary goals is to build one of the best engineering cultures anywhere, and we'd love you to help us do that. We launched in October and user and revenue numbers are scaling extremely quickly. We're backed by a collection of the top investors from London and Silicon Valley as well as Y Combinator.

We're especially interested in people who are interested in founding their own startup one day. We view working at Thread as a founder bootcamp where you'll learn about all parts of starting and growing a startup.

Want to learn more? Check out https://www.thread.com/jobs and you can see some of our code at http://dev.thread.com/

Thanks!

Thanks! Beat me to it :).

Good question -- it's hard! It is partially up to the moderator, but their job is more on the side preventing people from hogging the conversation, i.e. giving the opportunity for everyone to say something. Naturally we encourage everyone to talk if they have something to contribute, but we can't force them to :).

It is a problem indeed. We found the best solution to #2 is to avoid any massively niche topics. For example, "has anyone used <specific Python library>" isn't great for a group conversation: it instantly excludes people who haven't used that library, as well as people who don't know Python. Instead we try to stick to topics which everyone can relate to (even weakly), e.g. process-related topics are great for this.

Clickable: http://www.manytomany.co.uk/

Was not meaning my comment as a slight to you at all, it's a very cool app you've got here. Best of luck with it!

Neat!

From their JS:

  readinglvl = getReadingLevel(paragraphs, sentences, words, chars);
  [..]
  function getReadingLevel (p, s, w, c) {
      var r = Math.round((4.75 * (c / w)) + (0.5 * (w / s)) - 21.43);
      return r;
  }

For a site that's (apparently) hosting an article about a security vulnerability, they _really_ need to turn debug mode off.

For those wondering what I'm on about when the site starts functioning again, I got an error page akin to a Django page with `DEBUG = True`, listing useful information as the full path to the PHP script being run, the user it's being run as, , etc.

Agree that lxml is certainly quite large and batteries-included, but I've always found I can do pretty much everything I want to just using a few select methods, namely etree and xpath.

E.g. for extracting URLs from a sitemap:

    from lxml import etree

    root = etree.XML(data)

    urls = root.xpath(
        './/sitemap:loc/text()',
        namespaces={
            'sitemap': 'http://www.sitemaps.org/schemas/sitemap/0.9',
        }
    )

    import urllib2

    from lxml import etree

    data = urllib2.urlopen('https://news.ycombinator.com/rss').read()

    root = etree.XML(data)

    for i, item in enumerate(root.xpath('.//item')):
        print i, item.xpath('title/text()')[0]
        print item.xpath('description/text()')[0]
        print item.xpath('link/text()')[0]
        print

Cool, although LXML (mature, fast, reliable, generally awesome) can do this (and more): http://lxml.de/FAQ.html#how-can-i-map-an-xml-tree-into-a-dic...

It also has the 'objectify' API, where you can access XML nodes via regular object access (i.e. `access.nodes[0].like.this`). http://lxml.de/objectify.html

I actually was about to post this -- this guide is great. As an undergraduate, this was what was given to us to help demonstrate above-introductory command line tools/pipes.

This isn't the best solution. Instead do as others have suggested and make a subdirectory of your project the webserver root.

This solutions just stops nginx (/whatever web server you're using) from displaying the file. If someone finds a remote-file inclusion vulnerability in your app, in all likelihood they can use said vulnerability to browse your .git directory -- because, hey, it's in your webserver directory, so the permissions are almost certainly set up so whatever user the webserver is running as (www-data probably/hopefully) can view it!

(Obviously if your webserver user can view important files such as these elsewhere on the system, you're still screwed -- but reducing attack surface, etc etc.)

While I'm aware this isn't the actual topic, this is just a warning to not take this thread as a accurate representation of how useful "Who's Hiring" threads really are (e.g. as compared to a recruiters/job site/googling). I say this because that's pretty much what this thread may be miscontstrued as.

Reasoning: the majority of the posters will be people saying they got a job, effectively ignoring the swathes of people who were looking for a job and didn't find one they liked on HN. Since finding a job on HN is obviously much more notable than not finding a job on HN.

It's not a keyfob, it's built into the card itself.

The security measures are pretty good actually:

- Can't pay for things costing more than £20 via contactless (have to use chip and pin, the 'normal'/old method)

- After a certain number of continuous contactless payments, it will ask you for your PIN to verify the cardholder is still in possession of the card. This 'counter' is reset to 0 every time you pay for using Chip and PIN. E.g. if you alternate between contactless and Chip and PIN, you'll never have to enter your PIN for the contactless payment.

- If your card does get skimmed, your bank will cover you for any losses.

Skimming is possible yes, but you really have to be pretty close (the article is the exception here, not the norm). Within a few cm of the card, which it's certainly possible to skim someone's card - the person would almost certainly notice.

This is almost entirely FUD, and 'the card readers rarely function adequately if at all' is just plain untrue. What makes you say the readers don't work? Personal experience?

I've seen a broken screen on a contactless reader once, however I've also seen lots of broken Chip and Pin readers -- doesn't make the system faulty.

All contactless systems I've seen are either built-in to the same unit as the Chip and Pin device (which has a display) -- or a separate reader, which also has a display. Both clearly state when payment has been requested, and how much you are being charged. The problem of '[..] or even whether you are paying the bill of the correct till.' is rarely ever a problem at all. With the vast, vast, vast majority of readers, it's instantly obvious which reader you should use (because it's right in front of you!). Besides, if it's not immediately 100% obvious which reader you should use, the cashier will point it out to you, but again, this 'problem' is not a regression on chip and pin, which suffers from this.

Contactless payment is a hugely popular choice of payment in central London. Take a look at a Pret or Eat (or indeed, M&S) at lunchtime. Consumers aren't in the least bit scared about contactless, nor do they 'express fear'. Everyone I've spoken to about contactless has absolutely loved it. It's unbelievably convenient for consumers and a huge win for businesses too.

Agree with the interference though, that is annoying. That said, anyone with any sense doesn't keep their Oyster in their wallet :). Having to hold your wallet out in your hand and place it on the sensor is just asking for someone to grab your wallet (keep oyster in separate pocket during journey, replace during wallet upon arrival at destination).

Lovely subtext in the last section.

Good on you guys for not rising to Jeff's stubborn/dismissive attitude.

If this was part of a DNS Amplification DDoS, the source address is spoofed, and is in fact the target of the DDoS attack.

I've been considering trying HFT myself for a while. I'm competent with Machine Learning and am a Software Developer by day, so I can program and can sysadmin well enough to get something up and running without any trouble at all.

But, every time I've tried to actually get started, I've always found the amount of research required before being able to begin is just staggering.

It seems like the logical course of single-programmer HFT trading being:

- Find sample data

- Build your trading program using sample data

- When you're happy: connect to live API and set your trading program loose

- Iterate.

However, the first step and the third step seem like the ones which require the most research.

Is there somewhere which has a straightforward dump of timestamped market data available to download (free or not), in order to actually develop a working program?

Likewise, figuring out what to actually trade with, and which service to use is also pretty taxing.

First impressions upon landing:

I have no idea what this site is. The 'about us' link in the bottom left is hidden enough to make it annoying (if this wasn't from HN, I probably would have closed the tab). When I do visit the 'About' page, it's a wall of text.

Your call-to-action of 'Apply to Join' should be far more apparent. (Assuming that is the CTA?)

Your tag line of 'The 11K Club - A Giant Space Ark Spreading the Seeds of Humanity Across the Galaxy. Join Us on Our Journey.' is bad for two reasons: 1) It's at the bottom of the page! 2) Sounds extremely pretentious -- far too grandoise. It also doesn't say what you do in any way.

This is not 'hacking' the application process in the slightest. You prepared yourselves well; there's a difference.

But then again, the title got you on the frontpage of HN, which was almost certainly the goal.

There's an error in his first 'Function Invocation' example, the answer is 500, not 501.

[Reason: 'this.value++;' in the method invocation refers to obj.value, since 'this' is bound to 'obj'. Only in the innerFunction function invocation does 'this' bind to the global object.]

Weeeelll:

1) As others have pointed out, the separate release of code/writeup. I wager that most people really just want to see the code. Why bother doing both? If it's just to attract attention, that's a reasonably valid reason -- but it probably has the opposite of the desired effect, people get annoyed that they can't view the code now, and therefore start disliking the contest in general.

2) Even when the code is released, the format they use makes it difficult to actually look at the code. Let's take the 2011 winners for example [1]. One would assume that clicking each entry (e.g., the top entry[2]) would perhaps show the code, perhaps annotated in a useful way... nope! Surely it must link to the code then... nope! Perhaps it links to a page that links to the code... nope!

You have to go to the 'Winning Entries' page from the main menu (from [1]), scroll down to the appropriate year, then play a fun game of matching up entrant's surnames to their entries (yes, I know the surname is in the URL of [2]).

[ 3) While not a 'real' complaint: the I-just-learned-how-to-use-a-3D-modelling-program logo really is awful. It makes the contest look juvenile, when in fact the quality of the winning entries is very high. The site looks much better without the logo -- try it yourself, delete the img node from the homepage using Inspector/Firebug/whatever. ]

In conclusion: show us the code, delete the logo :).

[1] http://www.ioccc.org/2011/whowon.html

[2] http://www.ioccc.org/2011/blakely/hint.html

The way the site is run really lets the contest down.

A 'gallery' would be much more useful, showing the same screenshot(s) in multiple themes, rather than having to look at each one individually.

Google already did this (in part), it was called 'Sesame' and allowed you to log in to your Google account (on a desktop browser) by scanning a on-screen QR code with your phone.

However it was apparently just an experiment, and unfortunately has been shut down.

For a bit more info: http://www.webpronews.com/open-sesame-googles-newest-securit...

Or just search for 'Google Sesame'.

From the docs:

'''

* Node.js [...]

* jQuery [...]

[...]

This approach has become my hammer when web scraping tasks come up.

'''

If all you have is a hammer, you may find yourself noticing that objects become more nail-like :).