I imagine there's a tiny population of poets on HN. Would love to hear what they read from this.
634 karma · joined March 17, 2015
I imagine there's a tiny population of poets on HN. Would love to hear what they read from this.
The do-not-call has been fantastically ineffective for me. I imagine this could be the same. It's also possible that all of the companies strictly adhering to the FTC rules (i.e. those on the OP site) constitute a minority of the market, and spammers are getting data from other less scrupulous sources.
It's surprisingly tough to get broad, machine-readable market data for free but there are some cheaper options. Check this thread: https://www.reddit.com/r/SecurityAnalysis/comments/2ci5du/ca...
Or you could always scrape Yahoo Finance :)
Another thing that gets ignored is the the difference between a trading strategy and an execution algorithm.
Maybe the conclusion to draw is that sci-fi writing is 99% like any other storytelling in terms of how characters think, behave, and talk.
> This price represents a premium of 40% to the Company’s unaffected 10 day average stock price prior to March 3, 2016 of $21.83
Basically they took at 10-day average around a (somewhat) arbitrary date to price the stock for that 40% number. "Somewhat" because that date was when Eliott Management, an activist investor fund, bought a giant chunk of Qlik. That signaled a likely upcoming acquisition (which, as you said, the market was betting on). Thoma probably argues that signal moved the stock above it's "true" price.
The counterargument would be a defense of the efficient markets hypothesis: that the true price isn't about signals and technicals, it's just what someone is willing to pay.
1: Google is only banning developer accounts, not the violating developer themselves (policy problem).
2: Google is trying to ban the actual developer, but failing at identity assertion (technical/data problem).
And thanks for taking the time to give feedback, btw!
On one hand, I want to commend you for not using the author's clickbait title.
On the other hand, I don't want to give the author more exposure (because of the clickbait title) by increasing this post's comment score.
In the end, the first hand won. Thanks! :)
On the topic of completeness & accuracy: have you considered open-sourcing the content?
The anecdote the OP gives, "learn coding so your really boring job [no offense to OP] will be less painful" is useful. Even better for high-school kids: "learn coding so you can Instagram all day at your job while your program works for you." I'm not condoning this, and obviously it's better to actually inspire true curiosity (extremely hard), but I think this kind of message would work for a lot of kids.
[1]: https://e360.yale.edu/digest/china_anti-pollution_efforts__l...
[1]: https://technifyme.wordpress.com/2013/02/26/netflix-uncovere...
[1]: http://www.techworld.com/news/security/worlds-largest-ddos-a...
I worked on a few security consulting projects in healthcare. The HIPAA security rule is way more vague about actual controls than a rational person would assume; much more than analogous regulations on financial data (e.g. PCI-DSS). The HITECH amendment added a lot of breadth regarding which parties must comply, but did little to proscribe specific controls. Most providers, contractors, etc. use a framework called HITRUST that attempts to identify and map actual security controls to HIPAA, but even that is not super actionable.
One of the hardest problems to solve is the immediate criticality of patient data. You absolutely cannot have someone die because a nurse or doctor forgot their password and couldn't look up medical history. Makes practitioners resist adoption, and you end up with "break the glass" (emergency security bypass) functionality on a lot of sensitive systems/data.
VC, PE, etc. arguably incorporate more information about potential future (2 year, 3 year, 10 year) growth than public investors.
Maybe we should stop comparing the two valuations so equally?
Unrelated: the ads at the bottom of this site really do a masterful job of demolishing it's credibility... wow.
All but #1 have a structural incentive to make projects bigger the same way a mechanic has a structural incentive to "find new problems." The client always has final say, but people underestimate how hard it is to keep saying "no" to multiple reputable firms all warning you against going too small.
That said, this kind of swindling is far from ubiquitous. There's a philosophy that blindly upping scope is shortsighted, and you do better in the long run by actually representing your client's best interest. Where I worked, I found it pretty easy to surround myself with people who thought this way.
Also, slowing down trading doesn't mean eliminating HFT, it's a matter of what constitutes "high" frequency... I'd argue we're well past the point where incremental increases in speed result in equal gains in liquidity. And those increments now cost more than ever before.
As far as the tax: personally I'm very in favor of slowing down trading... unfortunately, what's being proposed introduces as much structural game theory as it eliminates. What's the dominant strategy for a trader faced with a rule like "any trades resting for less than 300 micros get taxed"? To be as fast as possible without triggering the tax; staying just above the threshold.
All that economic waste on low-latency tech will just be redirected to low-jitter tech. Those who can reliably land an order within +1 microsecond of the tax line will outperform those who only have an accuracy of +10.
I'd like to see more exchanges experimenting with things like random variance in speed bump size, frequent batch auctions, etc.