HN user

datr

339 karma
Posts0
Comments105
View on HN
No posts found.
O Holy Crap 4 years ago

I've run into this issue with jeans. They develop holes around the crotch six months after buying a new pair.

A decade ago I'd buy jeans and they'd last years. Unfortunately my waist line has since increased and none of those survivors now fit me.

I started with Levi 511s and -- when they started failing -- moved to Nudie Jeans (2x price) as they offer free repairs. When I tried to get them repaired though I was told there was a six week waiting time which seemed excessive.

Next I went with a local atelier (3x price) figuring if I spent more that would solve the problem but it happened again.

We considered doing something like this on a project once but we had concerns about performance. How much latency does your API proxy add in for responses with thousands of tokens?

Additionally we found that this broke any sort of database indexing. Let's presume that Lyft would need to tokenize the start and end points of journeys (otherwise it would be quite easy to de-anonymise someone) then just doing simple queries like I want to know how many journeys happen in this area either become incredibly slow or you have to have anticipated needing this type of query and providing a non-tokenized "area" field which can be indexed (but is sufficiently coarse not to leak data). Were you able to come up with any sort of solution for this issue?

This is actually very similar to a question I was asked when interviewing to read Maths at Oxford. In the Oxford version, your brother and you are also playing a game. You have a 2-dimensional block of chocolate with a poison piece somewhere in the block. The poison piece is bright green to the eye. You each take it in turn to break off some chocolate (you have to follow the rows and columns of the chocolate, and the break must be a single break). To win you must avoid eating the poison piece and end the game by handing it to your brother. You have the choice of going first or second? When should you choose either?

Funnily enough I was looking into this stuff recently as I was wondering what would prevent Niantic from showing adverts in Pokemon Go. Imagine playing outside a Starbucks and getting a notification that Costa is nearby and offering a discount.

My guess is that they could also claim nuisance.

I've worked places where we will always deploy a feature request to an ephemeral environment. I find quite a lot of bugs are actually caught by this.

But I've never deployed a feature branch into production like the blog post suggests. I had my own questions about this lower down in the comments.

That's true but it would seem like there would be other disadvantages to.

For example, when do you do testing? If we test as soon as the pull request is opened, we know that master is going to change a lot between now and when we finally deploy this code so the tests might not be valid.

If, on the other hand, we wait to test just before we deploy to live we risk locking up the queue for too long. This might not be an issue if you're test only take a couple of minutes to run but if you have lots of integration tests (like facebook for example [1]) then it could become a big issue.

Is the solution to this, you just accept that the codebase you're testing won't exactly be the same as what's deployed to production and the risk that comes with that?

[1] https://developers.facebooklive.com/videos/561/big-code-deve...

I know what you're getting at but to be fair that probably is a slightly trickier question than it seems. You need to factor in how absorbent the walls are (are you using unfinished drywall?), what colour the walls currently are (Is it very different to the paint? You'll probably need multiple coats.), what's the brand of paint you're using (I've seen different brands range between 350 - 450 sqft / gallon).

Cambridge does this as well and I can't say I was a fan. In mathematics, three years of learning ends up being evaluated through five three-hour exams administered over the course of a week. All it takes is one to fall ill for that week and all of a sudden you don't get a grade. The best case scenario is you can convince the examination board your illness contributed to your performance and they might award you a DDH (Deemed to have Deserved Honours) which no one will really understand.

The 64GB HDD on the Chromebook is quite limiting too though. (Especially if you develop with multiple virtual machines.) I suppose you could use an external hdd but that seems bulky and I'm not sure it would be as quick.

I might try and hold on to my x220 for another year and see if 2016 offers any better ultrabooks.

This definitely isn't the norm in my experience. I have friends in many of the magic and silver circle law firms in London. All of them have shared private offices for their junior staff and individual offices for the senior staff.