TimMurnaghan

I get the motivation of what you're saying - but I'm going more towards splitting the back end from knowing too much. Do authentication in a proxy layer (can deploy as a sidecar if suitably containerized) and then have a bearer token between the proxy and the app server. Yes it's a lot of "architecture" for a newby but it generalizes well to the byzantine Oauth cases without requiring too mach app rewrtiting and this kind of service split is pretty do-able given a Paas.

It still looks wrong. There's still some of the floating/stuck-on head feeling about it. Or is that just because we already know it's fake from the headline? (... and the way that the flag moves is totally wrong .../s).

What grinds my gears is hard-coded magic timeout numbers. Somehow microservice people seem to think that these are good (e.g. for circuit breakers) without seeming to realize the unexpected consequences of composing like this. Your timeout is not my timeout. So firstly - don't do it. Time is an awful thing to build behaviour on, and secondly if you ignore that then make it a config parameter - then I've got a chance of finding it without wire level debugging (if you document it).

See Gramsci's work on hegemony. Or (slightly easier) Tressel's "Ragged Trousered Philanthropists" which makes exactly the point about how the poor become convinced that it's better to give more things to the rich.

Anybody know a good way to get your data out of fitbit? I've got a year's worth of decent data and it's obviously at risk if google shutter it. Also I don't want them to have it - so I guess I'm in the market for something independent.

> people in those countries tend to (strictly speaking incorrectly) refer to the timezone as GMT all year round. Not really. I've found that mistake much more common in Americans. Calling the time in London GMT got baked in to some software (ing Outlook) but locals perfectly well understand BST.

Yep. Reads like an american (got the exchange rates the wrong way up), so should have said get reasonable amounts of holiday.

This model assumes hiigh availability of spaces - and that's not what I see very often outside the wide open spaces of America. A better model would include time to find a free parking space. Searching and queuing time can quickly dominate under high utilization. Taking the first available space is very far from "meek" when you have to struggle to get it.

It is an interesting piece of history. This dates back from when MS thought that all networking should be peer-to-peer (and that 640K was a lot of memory). IBM knew better and built domain controllers into OS/2.

As an anecdote - I worked on the team that was sub-contracted by IBM to write this. The spec was considered super secret and so had to be kept under lock and key. IBM security would confiscate any loose documents and leave a red card. One red card is a warning, two and you're off the project, three and the project is cancelled.

We'd just had a red card so were on alert when, late one evening, we discovered an unlocked cupboard on the final sweep. So we saved the spec in another cuprboard and for a joke left the old red card behind. The PM, who's spec it was, came in early the next day - obviously before the devs who left late the night before, found the red card and phoned security to get it back.

The ensuing "YOU'VE LOST THE SECRET SPEC!" conversation spiralled around like crazy until we came in and managed to calm everybody down. The PM still had to do a lot of grovelling. Moral of the story - probably best not to attempt a joke with anything security related.

Nice to see wavelets in here - but it's a shame that he seems to be encouraging people to actually use Haar wavelets. They're fine for teaching - but there are usually better choices in real life. Daubechies are a good default

We're still waiting for an explanation of what Godot is ...

I'd look at any long term medication as a factor.

PPIs can definitely affect magnesium. https://www.gov.uk/drug-safety-update/proton-pump-inhibitors...

On the other hand if your heartburn causes reflux then the PPI can help sleep. https://www.ncbi.nlm.nih.gov/pubmed/24942514

This became obvious a few years ago. I went to a startup pitch event (actually to get pointers on how to write my own) and was genuinely horrified at what all of the ad-tech guys were up to. There is no reason to assume any moderation or morals here. The naked greed of surveillance capitalism is such that all of the precautions that might have looked like the province of tinfoil hat wearers are now justified.

> Look at Material’s Updates No! If you're thinking about your enterprise application like an android app then you're starting in the wrong place.

Absolutely. My characterization of Mongo is that it's the back end choice of front end developers. The only possible justification for it could be time to MVP (and that's being kind). It's bad for all of the reasons that back-end people make back-end choices - non-functional requirements like operability, clustering, etc.

Hopefully this is the start of it being removed from any infrastructure uses. I spun up an openstack instance the other day and was horrified to find Mongo in there.

The original VIX used to to be that. But for some time now (approx 2009) it's been a synthetic variance swap made up of a weighted sum of the "bunch of options" (weighted by square of the strike). The huge advantage that this makes over an actual implied vol is that it becomes replicable. And it's close enough to being the "fear index" of the popular press.

Don't forget the Americans with the Patriot act

Kew is awesome (and a nice river trip), but it's a shame that after the first 5 clicks I've got a symposium and some more questions. Anybody got a summary?

If you're using a small subset why on earth is it the right language? I had the misfortune to try to mentor a new quant who felt they had to write C++ "for speed" . But refused to use the STL as they were going to use a subset. So they wrote Fortran-like C++, array as the only data structure, bad lookup algorithms and leaked like a sieve.

Things are in the language for a reason - if you've got the issue then you use the feature.

I hardly ever recommend C++ these days as it's not worth the slower dev time. There are a few cases where run-time really does trump everything else and it's still appropriate.

In that case the code will be templated to within an inch of its life, because that's how to write real C++.

nhanq is a one day old account posting fake news. Let's hope that the trolls don't take hold here on HN too.

There are many valid criticisms of these kind of surveys, but crime, which is the hook that the anti-migrant posters like to use, is one of the criteria - so the idea that "It's getting bad there" is the one that needs rapid rebuttal.

Funny how it's just become the first european city to top the economist liveability index.

https://www.bbc.com/news/business-45174600

There always are people who vehemently disagree. Read Tim Geithner's memoir "Stress test" and his fights with the "fundamentalists". Luckily he won enough of the arguments and the bail outs meant that the US recovered more quickly than those economies who kicked the can down the road.

What about the question of no-shows? If your assistant can make bookings easily - you can make a load and then choose where you actually go later. That's actually one reason why restaurants like phone booking - because if you've had the human interaction of talking you're less likely to not show up. The likely upshot is that the industry will have to move to paying for bookings.

Do people actually like Material for browsers on desktops? I tried it - as it would be great to have an opinionated design language with good framework implementations but it seems to make the same mistake as Windows 8 in trying to treat everything like a phone. That really isn't nice on a desktop.

... wiring the organoids to robots ... = daleks

Too much from the latimes today. Which is a shame as they are particularly crappy at GDPR. I know it's hard for US-ians to care, but if a large proportion of the articles are inaccessible it will damage hacker news. Better not to put these stories that want to stay local on the front page.

Bloomerg also use the keyboard as a "non-tariff barrier". As a systems integrator trying to work with their systems in the 90s they insisted that we buy a batch of a specific pantone gold colour for our keycaps.

So for people looking for easier to use data sources - even with more modern data feeds they're heavily license restricted and there's a lot of proprietary lock-in.

Not really that much in the article except for some OK advice on sizes and superscripts.

Overall I was left with an impression of how American it looked. It was like a plastic woodgrain dashboard. I guess that shows how much design aesthetics come into it - but that's OK if you know you want to look American.

And subject to gaming. Morning Star might be a nice cooperative environment - but when corporates try "360 review" it can get nasty. I've seen investment banks where people treat their colleagues as competitors for the bonus pool. If the review forms part of the bonus assessment why would people play nicely?

> DEC64 is intended to be the only number type in the next generation of application programming languages.

Intended by whom? A lone voice (however correct), a standards body, or an industry consortium? This article should really carry some authorship information.