knite

Systems administration and operations are tightly scoped. DevOps is, in my opinion, an umbrella term representing all non-core engineering work: servers, build pipelines, on-call response, infrastructure, and more.

The tricky part is that a lot of these areas are relatively new, and the older ones like server admin have changed dramatically over the past two decades.

DevOps hasn't failed. DevOps is in its infancy and is going through technical, strategic, and philosophical growing pains.

You literally wrote: "the story is almost a word for word translation of a story that's been circulating for years in Chinese".

This a great point, surprised you received no follow-up comments!

There are too many different tools in the space. I've been heavily researching workflow / ETL frameworks this week, and even after culling the ones that seemed like poor fits, I'm still left with:

- https://github.com/getpopper/popper

- https://docs.pachyderm.com/

- https://github.com/lyft/flyte

- https://aws.amazon.com/step-functions/

- https://github.com/spotify/luigi

- https://docs.metaflow.org/

- https://github.com/dagster-io/dagster

- https://github.com/argoproj/argo

- https://github.com/prefecthq/prefect

I'm about to book a LV visit for late March, which hotel offered you free nights?

Location: San Francisco (no east/south bay)

Remote: open

Willing to relocate: open, especially New York

Technologies: devops, Python, Terraform, Ansible, architecture, infrastructure, SRE

Resume: https://www.linkedin.com/in/pikeas

Email: [email protected]

Experienced devops lead looking for eng manager / director opportunities.

It sounds like NLB passes through source IP - does that mean outbound flows are through the IGW?

Individually yes, organizationally not that I know of.

As a former Cognitive and Inscape employee, @mikeryan is largely correct. Note that fingerprinting happens on the TV - no actual content was sent back to us. Still absolutely creepy.*

* Not the opinion of my (former) employer.

This is my old company! Cognitive Networks, acquired by VIZIO and rebranded VIZIO Inscape.

What sort of bulk work is this? If margins are this good, it sounds like a real market opportunity!

From the article: "The impossible challenge with Docker is to come with a working combination of kernel + distribution + docker version + filesystem. Right now. We don’t know of ANY combination that is stable (Maybe there isn’t any?)."

What combination of Docker version + distro + kernel + filesystem are you running, and how stable is it?

Congratulations! Will you be sharing details on how your salary negotiation went? Reference: http://www.kalzumeus.com/2012/01/23/salary-negotiation/

I've seen many glowing references to Feynman's Lectures on Physics, but this is the first time I've seen them called a failure. Could you share a bit more about why they're considered a failure?

Could we get "Python" in the title?

Member of the peanut gallery here, and I fully agree with Renner1. I occasionally do front end development work, and the pace of change makes life very difficult.

Imagine someone who last wrote a Python/Ruby/C/Java application 5 years ago - they could hit the ground running and learn a few new best practices and tools in 1-2 new weeks.

Compare that to someone who wrote a JS app 1-2 years ago - they have months of catching up to do. It feels like the JS landscape is changing so fast that keeping up with things is a full-time job.

I've recently started looking into Ember - which of their framework decisions do you dislike?

I'd also love to chat about this, when you add your email to your profile. :-)

kube-aws is great! When do you expect to update to Kubernetes 1.2?

Can we get "(2015)" on the title?

A, but there's a catch! I've asked for a company's range many times, and they have yet another non-answer answer: "we don't have a firm range in mind, we're confident compensation won't be an issue for a top candidate".

It's a game of chicken. The best counter I have is "what is the top of your range if we have a perfect fit?", but even that doesn't always work.

At this point, I'm sick of games. If a company refuses to disclose a salary range and/or insists on getting me to quote a number, I lead with $2X0 and see what happens. 80+% of companies aren't willing to hit that high, and the other 20% have been more interesting roles at higher quality companies.

I've wanted to share my thoughts and experiences regarding the "never be the first to quote a number" strategy for some time, but I usually see these threads when they're too stale to comment on.

My background: I'm a senior-level engineer in my early 30s, in SF. After a consulting stint, I interviewed heavily in 2013, and again in the second half of 2015, and currently speak with 1-2 recruiter cold calls per week to keep my options open. My sample size is many dozens of intro calls, across startups ranging in maturity from 1st engineer through some of the unicorns everyone knows.

In short, I agree with p4wnc6. A very relevant fraction of recruiters, say a third, will refuse to proceed until you quote a figure. This is true for internal and external recruiters. No amount of push back works with this group, they'll see you as difficult or otherwise not worth pursuing, and would rather end the discussion than proceed number-less.

This leaves the two-thirds of recruiters who are willing to play ball. Now there's another problem - not quoting a number is only a good idea if you want to avoid being low-balled - it's a tremendous waste of time if your desired compensation is above the expected range.

For transparency and knowledge sharing, I'll be specific: my background is in operations and infrastructure ("devops"). 90+% of the roles coming my way pay in the range of $130-180K base. My base is above this, and very few companies will be willing to pay a premium of 50% more than they expected to. No amount of wishful thinking about "your payroll is a drop in the bucket" will bridge the gap if it's too large.

Which brings me to a question I'd love the answer to: other than working for the big ~6 (Google, Facebook, Uber, Apple, etc), how can I push my comp up to $2X0 (or even $3XX!)? I feel like I'm near max, so I'm biding my time until the right VP/Director/etc of Ops role comes along. Is there anything else I can do?

These seem a lot like JWT (JSON web token)?

JWT is mentioned in passing near the end of the article, but it would be great to see a description of what makes macaroons different or better.

I would love to migrate away from NVAlt, really hoping that Quiver is the answer. NVAlt is great, but the combo of no tags + no iOS version has been a thorn in my side for years.

Knowledge stewardship. The world's knowledge is growing exponentially, much faster than the tools to aggregate, catalogue, and filter that knowledge.

Khan Academy is a good start. And Google is, well, Google: you can find what you need, if you ask the right question. We need the 21st century library-teacher-guided learning system.

Can you share why and how these Cycle.js users were burned by the framework? I've been considering it for a project and would love to hear about how it's gone wrong for others.

Which two?