I guess "the firings will continue until morale improves?"
2,558 karma · joined December 10, 2011
I guess "the firings will continue until morale improves?"
Good times.
[edit]
Oh I see it looks bad in Firefox on mobile. Fair enough.
https://www.theguardian.com/us-news/2020/jun/18/police-found...
I see kubernetes as more useful when organizationally you have more heterogeneous services and separate dev/sre groups. This allows them to divide up responsibilities more easily.
For the last 12 years or so I've worked extensively in all arrangements and here's what you need to know.
Outsource: Generally this conflates 2 actions. One is paying for a cheaper labor market. The second is paying for less skilled people. Most of the projected cost savings come from the latter. Most of those projected cost savings don't appear. I remember folks hiring $10/hr DBAs in India and the result was about what you'd expect. India is full of great DBAs and they ain't charging $10/hr or at least they haven't for a long time. It is the case that you can access a cheaper labor pool. Most people do this and then negate that savings by not creating a remote-first culture and introducing massive language and time zone barriers and friction due to multiple companies interacting.
Offshoring: The key difference here is that these are part of your company. In the US it's totally possible to set up an office in central/south america in-timezone and staff it with amazing people and save some money. Well, except for most of those folks who are willing to relocate will eventually accept offers with FANG companies either locally or relocate. So it's a nice scheme while it works. (Hi to all my tico friends now at Google and Amazon)
Remote: this is what most people confuse for the above two things. Remote is about doing 2 things.
1) Expanding your hiring pool beyond a 30 minute commute from your office (turns out that the other 99.99% of the world's population also has some great folks).
2) Making your company culture remote-first. But that's synonymous with writing things down and documenting things.
Sure interpersonal relationships can be trickier to bootstrap and that's a real cost. But see #1, nobody talks about that cost.
The final thing to keep in mind is that for most big companies, there's no way to avoid the remote cost. As soon as you open up an office in another location you're a remote company. Hell, as many people can attest as soon as you ask people to attend meetings on another floor or an adjacent building you find out you're a remote company.
Their overall quality feels like it's gone down and their non-netflix content feels incomplete (many movie series are only partially available). In that way Netflix has replaced basic cable for me.
Whereas HBO and Amazon Prime still produce shows that have a certain wow factor in terms of quality.
I've seen a great org mode webapp here, but Google drive permissions means you are forced to grant the webapp read/write to everything (not just a folder or mimetype).
In spite of that I still use it because I've never seen anything like it in terms of functionality.
https://retrocomputing.stackexchange.com/questions/11533/why...
I wish most applications offered 3 boxes:
1) Don't send telemetry
2) Send data needed to catch bad rollouts (think SRE style status code and latency metrics).
3) Send anonymized data to help improve the product.
4) I want to be a beta tester/insider, you can capture my logs.
But realistically if you're not doing .NET on windows, you're still an early adopter who's going to run into weird issues that you won't have to deal with on java.
Across the Walmart.com websites I didn't see anything from jet tech. The only thing I heard talk of was essentially reporting to push Marc's basket economics passion.
I believe Jet's acquisition was essentially a way to buy Marc Lore as eCommerce CEO.
I've met with many Jet folks and they are an awesome crew to work with, but Jet didn't really operate at Walmart scale.
Finally many platforms like docker, in the past, will spin up userspace proxies (docker-proxy) which is even more expensive.
> If Tesla has provided you with a face covering, you are required to wear it unless otherwise told by your local leadership. If Tesla has not provided you with one, you may bring or make your own following the Center for Disease Controls guidance.
Removing fsync is generally referred to as "running with scissors" mode, although postgres now supports it better with unlogged tables.
If their load balancer is smart enough it can call the dispatcher, and make use of something like https://zaiste.net/nginx_x_accel_header/ to figure out where to forward the request. Unfortunately this still requires uploads be proxied through the dispatcher.
You could get crazy and involve a CDN (akamai or cloudflare or fastly) that could do some smart logic, especially if you can emit your dispatcher as a lookup table that's updated frequently. I don't know what bandwidth costs would be for that though. Probably high.
It's an interesting problem space and I'd love to talk to these folks about it.
Unfortunately, crypto libraries have a history of having a terrible UI and defaulting to ECB. Years ago I ran into this with pycrypto. I worked on a team that joked about how important it was not to do ECB and it turns out they had done ECB. https://www.dlitz.net/software/pycrypto/api/current/Crypto.C...