85 karma · joined March 23, 2013
https://en.wikipedia.org/wiki/P-18_radar
Increase the wavelength and triangulate with multiple P-18s and you have a very visible nice slow moving target.
1. Moores law partytime is over. Performance matters again and the language has significant upper limits on speed.PyPy is not fast enough and further splits the user base.
2.As performance matters again concurrency matters more,concurrency in python in horribly implemented.
3.AsyncIo, What the hell am I even looking at? Gevent is vastly simpler than this.
It is a pity as it is one of the cleanest languages around and a joy to code in. But programmer productivity is more important than speed you say? We in many cases that is true but languages like go and Julia can offer both so why program in a slow language which you may have to replace later when its almost as easy to take another option and have everything?
“Worldly wisdom teaches that it is better for reputation to fail conventionally than to succeed unconventionally.” Keynes
As far as meteor/node goes,having the same language on the server client is great. Having javascript as that language is not so great. Web apps are generally a front end to something bigger and I never want to do any serious data wrangling in javascript if I can avoid it.
I will propose two theories. The board required a more experienced hire, the directors bent over. They are growing and got greedy,this is an equity grab.
The attitude displayed by Alex is healthy for his own psyche however this is not in anyway a good thing. Effectively he was cheated out of his startup investment.
What i learnt was: Forget about all this dog inherits from Mammal bullshit(it doesn't work that way,its just wrong!). OOP is good for a few things. 1. Sharing state between a collection of functions(call them methods if you want to use two names for the same thing). 2. Code reuse (inheritance)
Im rather amused that test driven development forces you to simplify OOP as much as is humanly possible,thereby going against the advantages of a shared state,which is one of the reasons you would use an object in the first place.
An excellent chapter about market making in here,however you would have to adjust it quite a bit for bitcoin.
to quote.. """, it allowed the transactions of users to be skewed, allowing malicious users to cause other users to essentially lose money, or worse yet, put them in a potential dispute, and ultimately, cause our product to lose customers."""
report to the regional financial services authority. Create anonymous story about how company x is causing massive user vulnerabilities etc.Send this information to the companies clients.You could cause massive damage and come out looking like the good guy if you spun it right.
More seriously consider something like http://sphinx-doc.org/ Code is not static,your documentation should not be either.
The real trading problem when we look at access and information asymmetry is not HFT but dark pools.HFTs typically all compete for the same pie anyway.
HFT is not very profitable anymore.There are a fair number of companies in the field now.
HFT tends to be algorithmically simplistic.This is not because stupid people are working there but its very difficult to have algorithmic complexity and speed,and speed is more important.
It is very much a winner takes all game,profits are not evenly distributed,being fast is VERY important.
However good you are you are not a trader.You are a codemonkey. You will never be rewarded or compensated as a trader in most of these firms(some firms like Rentech are an exception to this,but rentech is not typical high frequency).
Your hourly rate will probably not be worth it. When you factor in variable compensation(ie bonus) which is not guaranteed and horrible working hours you would in most cases be better off with some boring bank java contract for compensation.
You can consider a low carb diet as well(provided its clean),humans are normally perfectly adapted to eat carbohydrates but he might find it easier if he has problems with insulin regulation. And he should stop working already,time for health related retirement.
If you understand a hammer and chisel fully it does not make you Michelangelo.
Your example of buyer and seller also makes that point indirectly unless the bit coins are instantly convertible to dollars someone is going to loose out in any price move.
The cheapest way to pay someone in dollars is to actually pay them in dollars.
Didier Sornette has some interesting theories(and dubious models) about bubbles,well worth a read.