224 karma · joined May 6, 2015
Part of the reason why it’s hard to learn (unless your job depends on it so you are forced to persist) is that the syntax is very terse. Check out this Java API for example: http://kx.com/q/c/kx/c.java. Yes, that’s the actual code you copy-paste into your Eclipse to get started.
It was rather refreshing at a time when I can't stand reading more than a paragraph of a typical press release of a BigCo written by lawyers or PR specialists. Unlike this essay, those are intended to obfuscate, not to inform.
One thing to keep in mind is that the higher your trading frequency, the smaller the price moves you can hope to capture, which limits how much capital you can deploy in your models. This is why HFT models are usually small in size but have high Sharpe ratios. As you reduce your trading frequency, you can expect to capture larger price movements and deploy more capital but you’ll also be exposed to more of the vicissitudes of the general market, so your Sharpe ratio will decline. Market participants usually carve themselves a happy spot on this frequency spectrum and stay there. I don’t know of any firm who is successful at every spot.
That said, I think everyone would benefit by reading a bit about these subjects, whether or not they’re developers. We seem to have a built-in tendency to underestimate the effect of randomness in life (see Fooled by Randomness and How to Lie with Statistics). To counteract that, I find statistical methods (e.g., hypothesis testing, confidence intervals, etc.) to be very useful tools to keep in mind. Having basic familiarity with such tools may not necessarily make us better programmers but it'll probably make us more rational decision makers in the general sense.
"It is not because of the few thousand francs which would have to be spent to put a roof over the third-class carriage or to upholster the third-class seats that some company or other has open carriages with wooden benches ... What the company is trying to do is prevent the passengers who can pay the second-class fare from traveling third class; it hits the poor, not because it wants to hurt them, but to frighten the rich ... And it is again for the same reason that the companies, having proved almost cruel to the third-class passengers and mean to the second-class ones, become lavish in dealing with first-class customers. Having refused the poor what is necessary, they give the rich what is superfluous."
Few months back I got jealous and installed Snapschat myself. It conveniently scanned my contacts, and found that none of my friends are on it. (I’m late 30s.) To this day, the only snap I received is the default welcome message they send to everyone.
They’re doing a good job of confining their appeal to their target age group. The minute I and my peers appear on Snapchat, it's time to get worried.
And then there's snapchat.com, which is another enigma. I consider myself a reasonably competent technologist but Snapchat makes me feel like an ape trying to figure out a mysterious monolith.
I was curious to learn more about his work a while ago and had looked up his PhD thesis. Here's a link: http://www.princeton.edu/mudd/news/faq/topics/Non-Cooperativ....
What struck me was that it only had 2 references to prior work! That's how you know you're doing innovative research.
I worked out of WeWork’s SoHo office in NYC for a while and was pleased with the details they got right to make themselves attractive to startups (no pesky sales team, short notice to cancel, no nickel and diming on Wi-Fi, printers, etc.).
Before WeWork, I also worked in a Regus office (their competitor mentioned in the article) and they managed to get all the same things wrong. Perhaps they have adapted since. I’m unaffiliated with either company but wish WeWork well. It was a fun vibe they cultivated and everyone seemed to enjoy working there.
This ratcheting theory is straight from Warren Buffett's annual letters, and it's a good illustration of the results of perverse incentives, considering that board members are often nominated by the CEO so there's peer pressure to "play nice" and not to antagonize the CEO.
An important risk factor for career-oriented married men is total abdication of social efforts and leaving it to the spouse "to manage the social calendar." In the long run, this causes men's own friendships to atrophy. Then, if your spouse divorces you (or pre-deceases you), you find yourself without any functional support structure, which could trigger depression or worse.
I learned this from a book I read a while ago ("Lonely at the Top"), which tries to explain the causes of male suicide, especially among successful men. I vowed then, that if I get married, I'd make a very deliberate effort to maintain those friendships I had before the marriage. It's quite possible that someday, those friendships will be all that you may have left to rely on.
The reverse OTOH seems more challenging. I’ve seen many CS graduates who tried to self-study their Black-Scholes, but rarely do they achieve anything more than a superficial understanding of the underlying theory.
[I’d except HFT from the above. That specialty seems to reward programming skills more than math skills.]
Conversely, if you are a recluse, perhaps taking up drinking on your own won't be too beneficial, if at all.
Similarly, if I were a defendant on jury trial, I wouldn’t prefer a new law grad to represent me. I’d filter for an older, experienced attorney, with good track record in the courtroom.
I think the above is common sense. But somehow most people get it completely backwards in our field of software. Why is it that people’s mental image of a competent developer biases towards 20-something whiz-kids as opposed to older devs? Doctors and lawyers have verifiable track records; is it because that most developers, especially in big corporations, don’t build such auditable track records that attest to their competency?
I’m very curious about this. A 60-yo surgeon who continues to operate every day, is revered, has job security, doesn’t worry about ageism, outsourcing, obsolescence, etc. A 60-yo dev who hasn’t moved onto management bears stigma of failure. (Not my thinking, just the common attitude I see in society.) Something is broken somewhere.