496 karma · joined September 18, 2016
As the credits run out the architecture reverts to the natural state - architectures tend to be the derivative of organizational structure, code base, and processes of a company.
Through this lens these decisions start making more sense. It is a reactionary process. Sometimes when you start small you bounce around like that and are lucky enough to grow for years and years until you hit a wall.
By the same token you could suggest people go to South East Asia or parts of Latin America and flash your Macbook. Yes, it works, be careful what you wish for.
The calculus and game theory of dating is interesting for nerds (for many reasons) - you might find no place is miserable for meeting women when you let go of this. Even the Bay Area.
I am trying to say this with kindness: you should introspect on how you treat people.
"(Units in thousands, Revenue in millions)"
Walmart: http://s2.q4cdn.com/056532643/files/doc_financials/2017/Q3/Q...
And so on.
Now great, you can get the weird syntax and unroll it if you squint. Why is it written like this? Isn't it wasteful to test against all three cases (15,3,5) instead of returning early?
Probably has something to do with 'thinking in arrays' and how its a cheap comparison and that there's probably matrix multiplication or bit twiddling going on under there. That's the interesting bit to me.
To get the feel for an array language. This fizzbuzz example is actually surprisingly interesting because of that.
> 1{::(('FizzBuzz';'Fizz';'Buzz';":) 1337)
Fizz
Is equivalent to: > ['FizzBuzz', 'Fizz', 'Buzz', 1337][1]
Fizz
In a language with less foreign syntax.
You can make it more familiar by putting the index on the right side of the array with '~': (('FizzBuzz';'Fizz';'Buzz';":) 1337){::~1
Fizz
This is the modulo bit: (0 i.~15 3 5|])It isn't quite there yet but things are improving on that front all the time and will be significantly better for newbies in a few more versions. In other words, it is getting there, don't worry about it.
PetSets are simply ordinally ordered container collections instead of randomly ordered.
The usual concept in Kubernetes is that a container has a name like 'thing-randomsuffix4242'. It is pushing you towards making your pods stateless and not precious so the failure handing logic is simple. If it is blown away for whatever reason can easily be replaced by the scheduler and 'thing-randomsuffix242b' is never far away.
With a predictable ordering you can actually make assumptions you otherwise couldn't. For example, perhaps you want the convention that 'thing-predictable1' is the master and 'thing-rpredictable{2,3}' are the slaves.
It is time to reintroduce some of the fanciness I used to have configured. I was looking forward to trying out Neovim but meanwhile Vim 8 has come out. Which way should I go now?
The idea to pair up worthy projects (think scientists folding proteins or doing something computationally intensive) with spare cycles is an old one.
I'm not sure how efficient this approach is. I got the impression when I tried to donate some cycles recently (spare servers) that its not widely used. Anybody has any experiences they would like to share? I'd love to hear.