799 karma · joined March 11, 2014
Personal email: my username at gmail.com
there have been plenty. facebook even launched one
I love your dock icon as well. I was trying to build a custom version of that but for my tmux line, but rescuetime's API doesn't provide realtime info.
Will you open up some APIs for the data? I'd love to be able to do my own analysis and build my own tools. I'd also like to backup the data to s3
i can't speak for the first two points, but those seem simple enough to avoid with tests, really. most issues are.
the third issue is something you have to decide on. i'm sure the tooling around go is much better than it was three years ago, but you're not going to have everything in a pretty package like you do rails.
honestly the choice is probably inconsequential, unless you have some actual reason why the language choice matters for your application (which it almost always doesn't).
also if you're in fintech and doing bitcoin, i've heard the node ecosystem has the most BTC support, so that's a consideration
I had already dropped out when I took it so it was a no brainer for me. If you've already dropped out or decided to I don't even know why you're asking - at worst it's free money.
If you're asking whether or not you should drop out, that's a pretty opinionated thing and depends entirely on your circumstances, but I'd recommend you go for it (fellowship or not). As morgante said, you can always go back to college. 10 years from now sillicon valley might not be so friendly to us tadpoles
My breakfast this morning was coffee with butter and MCT oil
If you're in production using it and still sad, or if you're not in production and not using it and still sad, move to the next step.
Seems like relying on low network latency for critical safety features is designing a fundamentally flawed system.
Is this really how driverless cars are being made or is the author just pulling things from his ass
Crystal (Kemal) CPU 1.85 Memory 11.2 MB
Node.js (ws) CPU 38.95 Memory 906.3 MB
impressive
Check out https://github.com/facebook/dataloader
We use it to do cross service joins in the form of bulk requests in a very transparent way.
Regarding the legacy thing, I think it's both. If you look at a lot of new tooling coming out that has to store UI state, people are still using XML
instead, let me give you my unsolicited opinion:
if you need to represent both the structure of your data and characteristics within that structure, xml is great because attributes are a really good way to do that. there's a reason most UIs are represented as XML.
if your data is just - well, data - use json. or better yet use edn