octo_t
> A few other oligarchs, and their companies, have been exempted because of their importance to the global commodities market, most notably Oleg Deripaska and his aluminium producer Rusal.
> When very harsh sanctions were imposed on Deripaska in 2018 that effectively banned doing any business with the company, prices for aluminium on the London Metals Exchange (LME) soared by 40% overnight potentially causing a price shock for the consumers of the metal. The implementation of those sanctions were at first delayed and eventually withdrawn completely
Meanwhile, Apple Maps and the OpenStreetMaps backing data has continued to get better and better each year.
If I'm an airline (and my business is dependent on the price of oil) and I think the price of oil will go up, I will hold some amount of oil futures at the current price. If the price of oil rises, my company is "hedged" against that rise. This is good for the buyer of the commodity. If the price of oil goes down, I lose on my future, but my business is fine overall.
Correspondingly, if I'm the seller of a commodity (I own an oilfield), I might short oil futures, in case the price goes down. I make less money selling my oil, but I hopefully make some back on the short
If the result of my `sort ` function is dependent on `sizeof(void )` being 8, when I compile from my x86 hardware for a 32-bit only architecture, assumptions go awry.
Note that this isn't likely with something like sort, but definitely is* likely with precomputing values/structs etc.
Things like meta-classes will drastically simplify end-user code.
Can the title reflect this somehow?
> Always build your architecture in a way that will avoid becoming trapped into a specific service. Amazon’s AWS Lambda sitting between any services and your app is a strongly recommended path!
- Build without depending on external services
- You can do this by depending on this external service
speaking as someone who does hiring at a large software company: yes, yes they do. In significant numbers.
> defining an open, community-centric governance inspired by the Fedora project
And if you're doing microseconds, why not go for the full nanoseconds?
this will very likely be calling time related system calls, especially clock_gettime with CLOCK_MONOTONIC.
The average (english) word is ~5 characters long, so most of the time, you'd be forced to check anyway.
Perhaps look into how to have the nodes split between 2 or 3 different datacenters?