839 karma · joined October 1, 2010
I’m usually at least somewhat amenable to the “but the bad actors are mostly just the outliers” position, as well. In most cases, that’s true. Again, however, not here. Anyone who read the manifesto and the “response” post by Zunger while practicing even a nominal amount of epistemological integrity would have immediately recognized that Zunger’s post was wildly dishonest, did not deal directly with the content of the post at all, and apparently even thought that fantasizing violence against the manifesto author was an acceptable way to respond. It wasn’t.
I was and remain extremely disappointed in Bay Area tech culture right now. This “manifesto” —a ridiculous and politically expedient moniker— was a crucial opportunity to have a culture-wide teaching moment and we blew it spectacularly. We could have had a nuanced, intelligent discussion about an extremely personal and difficult topic while also demonstrating to Mr. Damont why his application of the very real, widely accepted science he cited was wrong-headed and possibly even oppressive[1]. But no. We didn’t want to acknowledge the facts at all, and our aversion to doing so was so strong that a witch-hunt was executed instead. Meanwhile, we still seem largely oblivious that we made Mr. Damont’s broader point for him. And for the alt-right. They’re having a field day with this, and it’s all the more infuriating because they’re not wrong this time.
[1] e.g. https://contemporarysex.tumblr.com/post/163876071377/doing-a...
This is the kind of behavior that woke me up (in my early teens) to the dangers of adopting my values from my religious background/peers. I never thought I'd have to deal with witch hunts for wrongthink in tech.
Then why are you assuming you know what it said?
>Hiring practices which can effectively lower the bar for “diversity” candidates by decreasing the false negative rate
Is this what you're referring to?
These things _used_ to work in the Slack app. What happened?
That may or may not be true, but it's definitely a non sequitur narrative. In this situation, it doesn't matter whether or not "the establishment" is fearful of Bitcoin. All that will ultimately matter is whether or not the "winners" of this debacle end up killing Bitcoin in the process, and that will necessarily play out in terms of markets.
>And really, that is bitcoin's biggest threat.
Only if it survives long enough to truly compete at the level of "established capital".
If you're not factoring the platform cost into your product pricing, well, that can really fuck with a business.
I must have missed this. When did Gruber call the AMP team hacks?
> Turns out their "terrible work" is actually Apple's bug and the AMP team points this out both to Apple and to Gruber.
This is flat out disingenuous, unless you're talking about something other than the originally submitted DF article. There were multiple examples of why Gruber thinks AMP sucks. Are you claiming that all of them are "Apple's bug"?
In my personal opinion, this is all good work to do. One minor nit: You probably want to get out of the habit of thinking about `docker-compose up` as a deployment, and just think of it as a much cleaner, much more "prod-like" local development environment.
> * do lots of work to make the app behave inside Docker
I'm curious about this. What was the overall nature of the work? Things you would have had to figure out in a distributed platform anyway, or container-specific issues?
> * take control of AWS and IAM using CloudFormation, making it easy to set up and roll back permissions
This is amazing, I applaud you for your foresight. I wish we had known about this pattern much earlier.
> * bootstrap KOPS/K8s with CloudFormation
This is where there's going to be another giant time sink, unless you're already pretty familiar with Kubernetes' resources—Deployments, Services, PersistentVolumeClaims, Secrets, etc—how they work together, what they enable, what their limitations are, and so on. Not to mention picking a network overlay plugin, deciding on a service discovery model, and understanding how Kubernetes works. BTW I am currently working on this very knowledge, and at least for me it's been pretty heady stuff at times.
>Future work: >* set up Jenkins CI on top of K8s >* K8s deployments of the app for CI >* staging K8s deployments >* K8s in production
Everything here seems relatively sane, in broad terms. I mainly caution against moving too quickly and also against spending engineering efforts on this if you are also an IC for the applications your teams are writing.
>This has been my first venture in operations and it's been very interesting and rewarding, but at times it gets very intimidating to "be" operations with no senior guidance.
Honestly, you seem to have the right mindset for this and so far you haven't mentioned anything that I see as a huge red flag.
>I enjoy the freedom and responsibility and I feel like I at least have a significantly better grasp on this than anyone else in the company, but I wish I knew of a way to feel like my work was good in an absolute sense, like "definitely good enough".
Welcome to ops! There will never not be an operational issue that either needs to be fixed or is silently waiting to strike at 3AM on Monday morning.
TLDR of my opinions in this space: the cosmos is simultaneously deterministic and probabilistic. There is no free will. Nor are all things predetermined in the sense that most people use the word.
You seem to think this is a bad thing. Why?
- the deployment artifact is a "fresh" instance that's "booted" in a fraction of the time—as in a couple of seconds vs a few minutes—than a new EC2 instance would be
- since the deployment artifact is a fresh instance, there is no need to manipulate an existing instance already running your application as part of your deploy process (e.g. scp, ssh, unpack, run commands, restart/reload application)
- if you design your build pipeline appropriately, the actual data needed to be shipped is effectively just a diff from the previous image. In my org, that could mean the difference between shipping a 300MB vehicle to ~300 instances and shipping a 300KB vehicle to almost certainly less than 300 Kubernetes nodes
There are other things as well, but I wanted to stay roughly within the parameters of your examples.
If your organization doesn't already have a continuous integration story, I'd say it probably isn't ready for containers in production. If your cloud footprint isn't costing you let's say >= $50k/mo or so, I might argue that the engineering effort to Kubernetize your things is probably better spent in more direct ways on your product.
If you do have a CI/CD story, and you do have a very wide, expansive, and expensive cloud footprint, containers and Kubernetes are extremely compelling possible solutions.
Just last year they changed the support model to be a percentage of your AWS spend, as opposed to the previous flat rate. They even had the audacity to dress it up as a straight-up price drop.
https://aws.amazon.com/about-aws/whats-new/2016/07/aws-suppo...
Imagine you're an organization spending 100k/mo on AWS and your monthly support line item goes from $50 to $3000. Oh and by the way, the free support tier cannot create technical support requests.
If "in certain cases, the performance profile can be annoyingly different" is the outcome of a tectonic shift in the underlying hardware, it would be a significant and praise-worthy achievement.
This is completely unrelated to Uber's cultural and ethical problems.
* eyes open or closed, standing or sitting, breath or open or metta or body scanning, all are doable