There are 7 billions participants in the global economy and somehow FED pretends it has this magic ball that predicts what will happen in upcoming months. And even if it had, they have no proper tools to react on it properly.
681 karma · joined September 26, 2013
There are 7 billions participants in the global economy and somehow FED pretends it has this magic ball that predicts what will happen in upcoming months. And even if it had, they have no proper tools to react on it properly.
Of course I am joking, they simply have no idea what they are doing, since it is virtually impossible. I grew up in post communism country and I have cold sweat when I hear about price control. And somehow price of the money is centrally managed.
The closest religion to philosophy (I can think of) is Buddhism, it is basically a guide to learn about self and the world.
I think we have some sort global identity crisis because of that. Religions are not sufficient enough and science doesn't even try to answer the question of "why?" but rather "how?". In result of that, we ended up with no ideology and no tools to build one for ourselves.
This is laughably ironic, because we really want some change in the way we live and think and yet, we don't turn back and evaluate what people came out with in the history.
edit: if you want to start with it: http://philosophizethis.org/category/episode/
> The first is to be able to track each message individually (i.e. not using a single commit offset) to make suitable for asynchronous tasks. > The second is the ability to schedule messages to be consumed in the future. This make it suitable for retries.
That's a start - I'd love to see how did you solve the problem? How your solution compares to other similar products? Why should I care about stuff you are mentioning? It is not an issue of not mature product - I think one should start with defining exactly and precisely what is being solved here.
When solving a technical problem you always have to tailor your solution to a specific set of requirements and it is never like: "distributed, horizontally scalable, persistent, time sorted message queue." So please stop using such buzzwords.
- It is a turist island, but not that much crowded. It is relatively cheap to live there (comparing to Dublin/London/OtherTechHubs)
- climate is absolutely amazing (18-25 degrees all year - no rain)
- it is not a party island, it is really quiet and peaceful
- internet is decent - although expect higher pings when working on remote terminal.
- no need to speak spanish - since turists are everywhere - basically everyone speak english on level that enables communication
- perfectly safe.
- EU, Schengen.
It is not. I understand why people from Ruby really what it to be "like a Ruby", but it is a completely different language. People confuse this by not understanding the erlang runtime and end up writing really poor code.
This should be one of first articles new people to elixir should read. http://theerlangelist.com/article/spawn_or_not
The way to do this, it to publish on queue _after_ transaction, but also be sure that the action won't be lost in the process.
https://martin.kleppmann.com/2015/04/23/bottled-water-real-t...
Now, I am surprised I didn't push it forward.
- do "the right thing" (whatever you the analysts think that is)
- Let me guess - you want everything, don't you?
I highly recommend Eric's Schmidt take on this: https://youtu.be/hcRxFRgNpns?t=838
I did something similar for Erlang VM http://eddwardo.github.io/elixir/links/2015/11/04/links-in-e... (less advanced). I'd love to see comparison of these two models.
"When we asked respondents what they valued most when considering a new job, 53.3% said remote options were a top priority. A majority of developers, 63.9%, reported working remotely at least one day a month, and 11.1% say they’re full-time remote or almost all the time."
And only a few percent of companies hires remote?