The article basically suggests that algos are reducing market volatility.
Algos don't try really hard to get VWAP. VWAP is REALLY easy to achieve, _beating_ VWAP is what most banks are trying to do when they trade large blocks.
A lot of the stories about warring algos and detecting each other are just that: stories. Yes, it has happened, but by and large thats not the game thats going on.
sorry, I wasn't clear. I wasn't asking WHAT velocity of money is, I was asking someone to explain the author's velocity of money argument. i.e. transfering wealth out of btc accelerates the velocity.
q, m, v, and p remain relatively constant in that transaction unless the liquidity event causes a persistent decrease in the price level (no evidence that the current BTC market could support it, but also c.f. above my comments about immature markets and liquidity).
Can someone explain the velocity of money argument to me?
The blog post seems to be:
1. If btc are liquid, everyone will want to move btc wealth out to some other store of wealth and btc will fail.
2. If btc are illiquid, then it fails by definition. Currently btc are at this stage.
Here's why I don't get it:
1. If they ARE liquid and its easy to convert btc value to other value, why would everyone want to move value out of btc? seems like people would want to move value IN to btc because of the other benefits (anonymity, instantaneous transaction). Regardless, it doesn't follow that easy value conversion predicates value drain.
2. "Bitcoin seems to be at this stage [of being unable to convert Bitcoin assets into other, non-Bitcoin assets easily now]" -- this seems to be false. There's a highly liquid market for BTC-USD (21k btc have traded so far today). Yes, its not easy to transact 500k, but thats true for most new assets including exchange listed backed equities.
nothing. anyone can. right now its mostly inefficient to allocate cpus for mining. its just not worth it for them. as more bitcoins are mined they get harder to mine.
something like that. This morning I had this thought for 2 things:
1. a python filtering function I wrote
2. how to restructure an entire django project.
Both (esp #2) are a little big for posting a code snippet. Bigger architecture problems probably only make sense within the context of the larger scope, so I'd pretty much want someone to check out the whole repository.
The SO thing would be great because SO has built in reputations so it'd help people feel more comfortable with giving away the entire project. I personally don't care, but I can imagine that being a barrier to code reviews by strangers.
Obviously, that sort of code review is a much more time-expensive request, so finding reviewers might also be hard without some sort of compensation.
I'm not super concerned about confidentiality for my code, but then again I'm not doing anything groundbreaking.
Mostly, if I cared about confidentiality, it'd be so I don't get publicly embarassed for crappy code.
Rating systems for reviewers would also let people build reputations so that reviewee's could feel more comfortable about code confidentiality.
Stack overflow already has reputations built in, so as I mentioned, it might just be awesome as a feature for SO. And another revenue stream, if they weren't already swimming in cash.
There's a balance between deliberately writing garbage and trying to start with perfection, and you choose some middle ground.
Yes, write maintainable code. No, don't accrue technical debt just for the fun of it. The post is titled as if all other things equal I would prefer paths that result in more technical debt, but that's clearly moronic.
But you have to start with step 1 (or I guess you can start with step 2...). The point for me is that I end up a lot more long term productive if I get my ass in gear on "get it done" first, because it helps me get to "test" and "refactor" a lot sooner.
That doesn't have to be true for everyone, but it seems to be true for me... this week anyways.
to be clear, i mean a space that is heavily geared towards web based startup/technology hackers.
noble tree is a coffee shop and chicago jelly meets there, but it is not a space where you can expect to go meet random hackers
pumpingstationone is nice but last i checked it didn't appear to have a strong technology startup type vibe.
i understand that curating the "vibe" of a "hackerspace" (whatever that means) isn't an easy thing to do, but i've been INCREDIBLY IMPRESSED by general assembly and hacker dojo. pumping station one is a great space, its just not quite the same. I'd consider:
nycresistor:generalassembly::pumpingstationone:"what i'm asking for" -- basically "general hacker types" (macguyver, picking locks and being generally crafty) vs "programmer hacker mindset" (hey, i wrote a really cool thing in node.js which i learned over the last 48 redbull fueled hours).
Chicago is an amazing town and there are tons of great people for it: birthplace of RoR, cofoudners of django live there, plenty of YC startups, groupon, beyond the pedway (woot, @timjahn, calling you out -- attended your "Entrepreneurs Unpluggd" event in Feb and I think that may be the best event I've attended in Chi), grubwhub, grubwithus, i think restaurant.com, etc.
However, the tech community isn't quite as unified and its a lot harder to get in touch with likeminded folk. At hacker dojo, you could turn to almost anyone to get feedback on a web app or ask for javascript advice, which I am not aware exists in Chicago.
Might be a way to encourage them to pay you, but to your prospective clients who don't know the backstory behind nonpayment, you will seem petty and vindictive. Maybe you didn't deliver as promised, or the bill just slipped through the cracks by accident by ending up in the engineering department instead of accounts payable.
The facebook/twitter route is a public record, not only for the client but for you.
Do what's right for you, not what's wrong for them.
The "in another life I could have been a spy" part of me LOVES that this can be done.
I've read that with zoom lenses and consumer level dslr you can get high enough quality images to be able to copy someone elses keys without getting within 100 feet of the key.
The article basically suggests that algos are reducing market volatility.
Algos don't try really hard to get VWAP. VWAP is REALLY easy to achieve, _beating_ VWAP is what most banks are trying to do when they trade large blocks.
A lot of the stories about warring algos and detecting each other are just that: stories. Yes, it has happened, but by and large thats not the game thats going on.