Aside, your second point is incorrect. The SteamDB folks have a public write up on analysis of the preload system: https://steamdb.info/blog/steam-download-system/
1,850 karma · joined March 29, 2007
Aside, your second point is incorrect. The SteamDB folks have a public write up on analysis of the preload system: https://steamdb.info/blog/steam-download-system/
My high-level understanding is that they're going to run an ML model over your browsing history (locally on your device) to build a list of "topics" that you care about. Sites you browse can use the Topics API to pull a set of these interests from the browser to show you "relevant" ads. Mozilla has taken a negative position against this standard.
The monthly opex to house and power and cool those servers isn't _negligible_, but if you're doing back of napkin math comparing MRCs to Cloud you can just deduct the costs from their bandwidth charges that have been marked up 10,000%
Except when your team wanted to initially onboard with GOOPS and your request sat in Buganizer for 2 weeks waiting for someone to triage. Uh oh — we're turning down this service next quarter, you will need to go start this onboarding process again with its replacement.
Or when you needed quota in a cell where your product area didn't have Flex. Maybe you can set up a VC with your PARM? Does next week work for your launch plan? Hopefully they can do something for you!
Or when your logs access request sat in GUTS for a month because both of the approvers were on vacation and no, there's not an escalation path.
Or when you needed to change a firewall rule for a project your team inherited which for some reason runs on GCE. Make sure you bring your Ariane link when you open your request. Have ISE reviewed your code? No? ISE currently have a quarter-long backlog, so we're not sure we can grant your firewall exception.
None of these examples are contrived; the weight of the operational bureaucracy is staggering. It may well be that this stuff is felt more on the SRE/Security side around production launches than on the SWE side for experimentation or iterative development, but I struggle with the idea that Google is nimble.
It's significantly more likely that you've been keylogged or phished if attackers are actually accessing your Steam account with passwords of that complexity.
https://support.steampowered.com/kb_article.php?ref=5421-QTF...
* You used a modified client or client proxy (this was done for e.g. SSH)
* You used a remote-desktop protocol to remote into a machine with direct network access to the service
* The service got a wholesale exemption and was allowed through the firewall with ordinary IP ACLs
(descending order of impressiveness wrt the BeyondCorp philosophy and whitepaper)
Some of this is discussed in the "Non-HTTP Protocols" section of this paper: https://www.usenix.org/system/files/login/articles/login_win...
I also feel like graphics cards are one of those weird things that command a lot of brand loyalty, so it's probably going to take more than near-performance-parity to move the needle.
2016-01-26 - Levandowski's last day at Google
2016-02-22 - iMessage chatter directly between Levandowski and Kalanick about poaching more Google employees
That certainly paints the "acquisition" of Ottomotto in August 2016 in a different light, no? It's also shown in the document that Levandowski was meeting with Kalanick and other Uber execs as early as June 2015, though it's harder to divine what was happening at that time.
Agreed on the point that the deployment is only going to get easier over time.
A lot of the projects bearing that disclaimer are passion projects done 100% outside of work hours.
So your workflow would still be supported, and it would likely be more secure than exposing SSH traffic to the internet at large.
The protocol also supports session resumption in case your connection to the relays is briefly interrupted, but client support is buggy so it's been disabled for years (with few complaints)
Also: please don't spawn goroutines during init(). There's generally a better time and place, and in the event that you justifiably need a package-level background routine you can spawn it on demand with a sync.Once.
The namespace issues are unfortunately a lot tougher to address.
(I'm one of the current maintainers and we're already all over this transition)
I probably would have chosen gentler phrasing.
https://twitter.com/darylginn/status/590664399041519617 rings true.
That's analogous to visiting Carlsbad from your place in PB. I mean, except that Carlsbad is worth visiting ;-)
The norm seems to be living and working in the city unless you're attached to a large megacorp with a fleet of shuttles, or else you end up on Caltrain.
I spent years between a few healthcare startups, and I feel like there is a strong scene not only for Biotech but also in Communications and Defense. Speaking somewhat from experience: I feel like the problem is that the companies in those spaces are giant, lumbering, unappealing employers for young people. It's really hard to pitch an energetic new grad on writing Java for SAIC or Qualcomm.
Biotech stands to be an exception, but despite a strong presence by a medium-large number of companies, there just didn't seem to be enough jobs.
Now if your intent is to own a home, well, that's another story altogether. I'm generally priced out of even the cheapest areas.