TimMurnaghan

Interactive brokers is real

Fourth you must bet big.

No. You must bet right - and it depends on how right you are. Look up the Kelly criterion. Bet 1 - 2*probablity of losing of your current pot - will maximize expected return (but is a bit volatile for some tastes)

The only source for the "I refuse to see a pimp in the mirror in the morning when I shave." quote that I can find is Drucker hmself.

The German Ambassador didn't resign in 1906. Maybe it was a deputy or a different country, or it's just made up?

They're a (quite sour) eating apple. Bramleys are better cookers.

Nice try to bring in some EU bashing. But Switzerland isn't a part of it.

Obligatory counterexample, comedies. A quickfire screwball classic like "His Girl Friday" has lots of smart lines per minute where recent Hollywood ones will have two jokes in 90mins that they've had to put into the trailer, and slow build ups so that everybody can get the lame joke.

It's not so much the language as the horrible layout - with all the navigation at the left leaving the text so small.

The reported lower vitamin D levels in more severe RA are more likely to be consequence than cause. Our data do not support vitamin D supplementation as a direct therapeutic intervention to modify RA outcome,

Vaguely competent financial management is by no means assured. I suggest reading Tim Geithner's "Stress Test" to to see how hard he had to fight to get some basic things done.

Agreed if you're making a web page.

However there are lots of us writing applications which are delivered by browser. With that lens you're completely wrong. Then I do want to send json from the backend and have lots of behaviour in the frontend viewing that in different ways.

So basically it's the differences between web pages and applications.

Truth is that there aren't many other sensible ways to deliver applications any more. All big companies still have windows machines - but MS broke all of the ways of writing applications on windows so going to the browser makes sense and you get some cross platform ability - plus you get to move it to the cloud.

No. Every golang stdlib proxy I've tried to use is a toy. They very inefficiently copy the message body and the memory behaviour is just horrible. Try posting a 10MB message. (That's actually not a lot for modern technology) and it will grind to a halt.

Nice try millenials. But the boomers grew up in times of lower car ownership and general road traffic - so while there was leaded petrol - the exposure to lead wasn't necessarilly so high. What do we call the generation of around 1980? Late Gen-X? They're probably the ones at most risk.

Nice to see some love for wavelets. They're great for many more things. Robust volatility measurement, galerkin methods for numerical solutions to differential equations in finance. Just please don't use a Haar wavelet for anything other than teaching.

I'd really like some kind of architecture picture describing what runs where. Regardless of whether it's promoting the cloud service why would I want that to run a rPi service? A picture might explain that.

Not very like gravity. They explicitly say "outperforms gravity models". Also the economic concentration laws behind this would often follow power laws - so maybe the inverse square is just a 2nd order approximation rather than a real fundamental principle.

Bit of a leap of logic there. Using proprietary cloud services is the decision that causes lock-in, not the tool you use for managing it. Terraform and Pulumi do a resonable job of making similar APIs for the variations of cloud providers - but it's not their job to provide an abstraction layer as you need to be able to pull all of the underlying levers. Kubernetes IS an abstraction layer so where you choose to roll you own stuff you can make it somewhat portable to another cloud (at the cost of writing the config).

On the choice of cloud services, I'm happy enough using cloud databases (they can do fast I/O and high-availability at a reasonable price). I'm much less happy with their packaged stuff. Tried out cloud composer this week. Turns out that it can't be easily scripted in Pulumi and wants bigger infrastructure than our main application so not the painless composition of services of the marketing brochure.

I never got to the article as I gave up after 25 "no" clicks on the cookie form. (I know I could block better - but sometimes I like to see the state of the bad ui design). Websites like Forbes and The Condé Nast ones don't exist in my world as I don't go there.

As to Apple maps I gave up when the dumped us in a field in Norfolk (England). It was about 5 miles from the proper destination, and no clue how to get to a road going there.

Houses in Cornwall need Radon surveys. https://www.cornwall.gov.uk/environment/environmental-protec...

This isn't Citibanks UI design. This is about Oracle's core banking software Flexcube. It's way deeper than UI. The loan entity didn't support the update they needed to make so they tried delete and re-create - which involved paying off the first loan - but the counterparty didn't agree with the "re-create" bit. Take the "U" part of CRUD seriously people.

In the end this could work out well. People go where the stuff that they want is. I occasionally dust off an old twitter account when I want to reach an org which is otherwise hiding any means of human contact. So if scihub does manage to make a meaningful presence somewhere like mastodon that's all for the good - and just hastens the decline of twitter.

Not seeing it on my watch. Just a fairly uninteresting solar graph. Maybe it's not available on my watch - but shows a real problem in modern UI design. The "shadowban" school of UI. The problem with that is discoverability. You'll never know if you're looking in the right place.

Next year they're planning to hold the conference in Scunthorpe https://en.wikipedia.org/wiki/Scunthorpe_problem

It's 25 years since that problem was identified and people are still using dumb block lists, you do sometimes have to despair at the state of the software industry

"Nature will castigate those who don't masticate." https://en.wikipedia.org/wiki/Horace_Fletcher

Shame that there isn't a review in this rambling incoherent article. Academic writing at its worst. Wonder what grade it'd have got if turned in by a student.

Does this give a better space saving than a gyrator? https://www.sites.google.com/site/roelarits/home/gyrator

That's true - but where do you put the function? In a complex system I can end up with loads of these totalling functions scattered about. I might have gross and net versions of the total and, given human nature, they get created near the use of them. The variants then get duplicated. The objects give you a modular structure which means you can see the interface.There is a disconnect when you have to shift to the object - but you can also see when to refactor.

I'd also position this as being up against openshift which is in the managed k8s/hybrid cloud space.

Hybrid cloud is definitely a thing as you scale up. For a big enterprise with a significant base load you're paying 5-8 times the cost of on prem for that in a public cloud, so being able to run your own infra for production base load but scale up to the public cloud for dev and burst is a real win.

By Betteridege's Law - no of course not.

For a slightly better answer we need physicists rather than philosphers - and need to consider at what scale the quantum measures work - and what scale they're observing at.

From TFA "... it brings Python on par with PHP"

Faint praise indeed

Thunks can be an anti-pattern. They encourage multiple dispatches to redux which can leave people designing "set data" style reducers rather than more meaningful ones. Parent comment suggests sagas and that's much better. An action in a component dispatches one thing and the saga can co-ordinate all of the logic.

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.