These sort of unfortunate accidents happen every day but any self-driving vehicle will be scrutinized. If the driver was in control and ran a red light, they're obviously at fault. If the AP went haywire and caused this, who is legally culpable?
6,947 karma · joined February 24, 2011
These sort of unfortunate accidents happen every day but any self-driving vehicle will be scrutinized. If the driver was in control and ran a red light, they're obviously at fault. If the AP went haywire and caused this, who is legally culpable?
How many other individuals in this clearly legacy organization have the knowledge and experience to take over your "superior" variant of technical debt once you get sick of the job and move to something trendier?
The hard part of ETL for me has always been gracefully handling the outliers, the data that you need to look at within the context of multiple rows (e.g. duplicate rows that aren't exactly the same so it's not a simple SELECT DISTINCT) in order to make the correct decision, or the entity matching/mapping/categorization that often is necessary. Having the lookup tables that often need manual oversight when new entries show up that haven't yet been properly tagged. Or if you're ingesting address data and you want to normalize it through a geocoder, where exactly does that occur in these SQL-templating "pipelines"?
I feel like these are basically focused on moving data between different DBs and generating group-by queries to populate some rollup tables?
T&C's have absolutely no bearing on publicly accessible information [1][2][3]. They only apply to registered users accessing login-required portions of your website or application. Browsewrap does not represent a legally binding contract, no matter how much you pay your lawyers to write up your irrelevant T&C's.
[1] https://www.eff.org/deeplinks/2018/04/scraping-just-automate...
[2] https://www.eff.org/deeplinks/2018/04/dc-court-accessing-pub...
[3] https://www.eff.org/deeplinks/2018/01/ninth-circuit-doubles-...
That's quite the leap. Twitter is not a representative of the federal government.
For this reason, many frameworks ignore the default $_GET structure and instead access the raw URI query in $_SERVER['QUERY_STRING'].
Gotta fall back to wireshark for 100%.
Russia has been attacking critical infrastructure in the US for years. This is at best an incredibly latent response from a government who in many cases welcomes these attacks.
[1] https://en.wikipedia.org/wiki/Russian_interference_in_the_20...
[2] https://www.nytimes.com/2018/07/27/us/politics/russian-hacke...
There's zero validation to this data. If you feel it's too high, just submit a lower data point: https://www.levels.fyi/addcomp.html
If you want to get paid more, find a position where your work has a direct and measurable impact on revenue or profit and your compensation will flourish. And if you're already doing that without the pay, then it's time to find a new employer.
[1] https://www.nps.gov/subjects/legal/upload/Proclamations_and_...
If you look at his comment history, you'll notice he mentions Snowflake at every single opportunity. Snowflake raised $450M last October (~$1B valuation), so they have a nice warchest for strategic acquisitions.
[1] https://techcrunch.com/2019/02/19/google-acquires-cloud-migr...
[2] https://technical.ly/philly/2018/11/07/stitch-acquired-by-ta...
It's a whole lot of work to be legally compliant.
e.g. if you write 1 million 10KB files per day to S3, you're looking at $150/mo in PUT costs. If you instead write 1,000 10MB blocks, you're looking at $0.15/mo in PUT costs.
Due to S3's support of HTTP range requests, we can still request individual files without an intermediate layer (though our write layer did slightly increase in complexity) and our GET (and storage) costs are identical.
Edit Response: I've always used the partitioning conventions they suggest so not sure what sort of impact you encounter without.
Also just a word of warning, if you do have a lot of files, and you're thinking "let's transition them to glacier", don't do it. The transfer cost from S3->Glacier is absolutely insane ($0.05 per 1,000 objects). I managed to generate $11k worth of charges doing a "small" test of 218M files and a lifecycle policy. Only use glacier for large individual files.
[1] https://docs.aws.amazon.com/AmazonS3/latest/user-guide/creat...
And that's assuming perfect conditions and ignoring the rest of the normal latency encountered online. It's physically impossible to have a latency lower than ~480ms with geostationary satellites.
Getting an office lease is a huge process with a stack of contracts, pushy agents, ridiculously long leases, misleading prices, hidden costs, furnishing, and establishing all the necessary services. And if you're a small company, the owners are expected to personally financially guarantee the lease.
In total there were 18,375 cars registered in March compared to 11,106 in February '19 and 14,401 in March '18. If you back out the Tesla Model 3 impact (-5,300), you're left with 13,075 vehicles registered last month.
[1] Data source: https://ofv.no/bilsalget/bilsalget-i-mars-2019-1
So maybe I'm missing a ton of awesome features that github/gitlab provide?
What is risk in this context and how is it quantified as a dollar amount? Is that an amount allocated for returns/chargebacks/fraud?
Had you bought $100,000 of $AMZN in 2010, it'd be worth $1.35M today (and $1.6M in September) which would go a long way toward evening things out in a similar manner.