golovast

I got contacted by our rep a couple weeks ago, who informed me of this news. I thought it was a disaster and it really pissed me off. The rep couldn't even explain the reasoning well. It basically summed up to "because we can" and "where are you going to go?". He was shocked to find out that I didn't like it.

We currently self-host on kubernets/aws. The thing that really got to me isn't the new charge per se. It's the fact that GHA has a ton of problems. I can hold my nose and deal with them when it's free. But now that you're squeezing me, at least you could have created something like GHA 2.0 and added a charge for that. Instead, there are vague roadmap promises which don't even include things that I care about. Specifically:

- Jenkins had better kubernetes integration years ago. It's crazy that GHA can't beat that.

- "Reintroducing multi-label functionality" - yeah, so they first broke it. They did supply "reasons", which looked like they never talked to a customer. [1]

- Still no SDK of any kind.

- "Actions Data Stream" - or you can just fix your logging.

There are dozens more complains, which are easy enough to find. This kind of an approach just makes me want to make sure that I don't use GHA again. Even if I end up paying another vendor, at least I'll be treated as a customer.

[1] - https://github.com/orgs/community/discussions/160682#discuss...

It will really depend on your workflows, what services you use, what risks you're trying to manage and what trade-offs you're willing to accept on usability vs security.

For some scenarios, resource-based policies can form the foundation of your auth flow. If you look at the flows described in the docs [1], resource evalutionn is simpler. You still need to solve the problem of effectively managing all of those resource policies and limitations on where they can be applied [2]. That might be an easier problem to solve then dealing with trying to express everything as an identity policy. You're then less concerned with wider permissions at the IAM level and move the responsibility to the owner of the resource.

[1] https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p... [2] https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_a...

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare. We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2940216

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standardize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Foursquare | Devops/SRE/Systems Engineering (multiple roles) | Onsite | Full-time | Los Angeles, Chicago, Seattle, New York

Foursquare is the leading independent location technology platform, powering business solutions and consumer products through a deep understanding of location. Over 1,000 clients—including more than 50% of the Fortune 100—choose Foursquare.

We are looking for multiple roles, including Lead/Sr/Manager. Our stack is pretty wide, and includes AWS, K8s, ECS, Colo, Hadoop Ecosystem, observability platforms and quite a few other things. We've recently had a merger and an acquisition and a lot of work immediately in front of us is to unify and standarize across multiple technology stacks.

We have a large AWS presence and are responsible for both the data pipeline platforms as well as high traffic consumer-facing applications.

https://boards.greenhouse.io/foursquare26/jobs/2270612

If you have any questions, email me directly: arthurf [at] foursquare.com

Factual | systems/devops/sre engineer | Los Angeles, CA | ONSITE | Full-time

Factual is a location data company. A startup, but we have been around for ~10 years. Some of the tech we use: AWS, colo, hadoop ecosystem, kubernetes and much more. Looking to expand and grow our systems engineering discipline.

https://grnh.se/2abacd4d1

If you have any questions, email me directly: arthurf [at] factual.com

Factual | systems/devops/sre engineer | Los Angeles, CA | ONSITE | Full-time

Factual is a location data company. A startup, but we have been around for ~10 years. Some of the tech we use: AWS, colo, hadoop ecosystem, kubernetes and much more. Looking to expand and grow our systems engineering discipline.

https://grnh.se/2abacd4d1

If you have any questions, email me directly: arthurf [at] factual.com

Factual | systems/devops/sre engineer | Los Angeles, CA | ONSITE | Full-time

Factual is a location data company. A startup, but we have been around for ~10 years. Some of the tech we use: AWS, colo, hadoop ecosystem, kubernetes and much more. Looking to expand and grow our systems engineering discipline.

https://grnh.se/2abacd4d1

If you have any questions, email me directly: arthurf [at] factual.com

At lot of the debate here centers on DSLs vs programming languages and I don't want to get into the weeds of that. I did use terraform extensively at a few places and generally if you want to do something simple it does a fine job. When things start getting complex and the team & infrastructure is larger...well, let's just say some warts start coming up. You more or less end up with some type of a wrapper around it.

But in another place we decided to use troposphere[0] and I liked it more (at least for AWS-only shops). A lot more flexibility and you're relying on Cloudformation to do some of the heavy lifting around states. We basically ended up with a tool based on that library which would generate deployable CF stacks (and some other things).

[0] https://github.com/cloudtools/troposphere

You might take a look at troposphere[1] too. I've used both extensively and each definitely has it's strengths. In some cases troposphere is a better fit.

[1] https://github.com/cloudtools/troposphere

Spokeo | devops engineering | Full-Time | Pasadena, CA

We are looking for a Sr Systems Engineer (devops) who understands and embraces the devops philosophy, can work closely with dev teams and is comfortable with cloud based infrastructure. If you're excited about building big data architectures and creating a PaaS then you should talk to us.

Our tech stack includes (but not limited to):

* Dev: Ruby, Python, Perl or Go

* Config Management (ansible)

* AWS (or other cloud providers)

* CI/CD

* Docker

* Monitoring

* Spark/Hadoop/Elastic Search/Cassandra/Kafka

* Netflix OSS stack, Jenkins

* IaaS/PaaS

Pasadena, CA - Spokeo (ONSITE) Spokeo is a people search service that organizes information about people into simple and comprehensive online profiles that are accessible to consumers, businesses and non-profits. We are looking for a Sr Systems Engineer (devops) who understands and embraces the devops philosophy, can work closely with dev teams and is comfortable with cloud based infrastructure. If you're excited about building big data architectures and creating a PaaS then you should talk to us. Our tech stack and role includes:

* Dev: Ruby, Python, Perl or Go

* Config Management

* AWS (or other cloud providers)

* CI/CD

* Docker

* Monitoring

* Spark/Hadoop/Elastic Search/Cassandra

* Netflix OSS stack, Jenkins

* IaaS/PaaS

http://www.spokeo.com/careers

Pasadena, CA - Spokeo Spokeo is a people search service that organizes information about people into simple and comprehensive online profiles that are accessible to consumers, businesses and non-profits. We are looking for a Sr Systems Engineer (devops) who understands and embraces the devops philosophy, can work closely with dev teams and is comfortable with cloud based infrastructure. If you're excited about building big data architectures and creating a PaaS then you should talk to us. Our tech stack and role includes: * Dev: Ruby, Python, Perl or Go * Config Management * AWS (or other cloud providers) * CI/CD * Docker * Monitoring * Spark/Hadoop/Elastic Search/Cassandra * Netflix OSS stack, Jenkins * IaaS/PaaS http://www.spokeo.com/careers

Pasadena, CA - Spokeo

Spokeo is a people search service that organizes information about people into simple and comprehensive online profiles that are accessible to consumers, businesses and non-profits.

We are looking for a Sr Systems Engineer (devops) who understands and embraces the devops philosophy, can work closely with dev teams and is comfortable with cloud based infrastructure. If you're excited about building big data architectures and creating a PaaS then you should talk to us.

Our tech stack and role includes:

* Dev: Ruby, Python, Perl or Go

* Config Management

* AWS (or other cloud providers)

* CI/CD

* Docker

* Monitoring

* Spark/Hadoop/Elastic Search/Cassandra

* Netflix OSS stack, Jenkins

* IaaS/PaaS

http://www.spokeo.com/careers

This is definitely on point. I've worked for a fairly large regional MLS at one point and interacted with a fair number of other MLS's and what I've found out about this business was pretty mind boggling.

Vast majority of them are stuck in the past (think 1990s) and their only competitive advantage is restricting access to information. A typical real estate agent (with very few exceptions, I'd guess <5%) is adding little to no value to the transaction and is simply taking a middle-man fee. They are in general petrified of places like Redfin, Zillow and Trulia and they do anything in their power to maintain the current business model. Generally it involves limiting access to "their" data and coming up with whatever legal roadblocks they can use to defend against other sites.

The agents

However, they are sitting on an absolute treasure trove of data which would be amazing in the hands of the right people.

I work at Riot and it's great what you've been able to do with LoL. At the same time, I would say that finishing your CS degree (or becoming a better developer) would be definitely worth it in the long term. It's possible to manage both. I know many people who play a lot (not pros) and combine that with their engineering careers.

Also, somewhat relevant post on the question:

http://community.na.leagueoflegends.com/en/c/miscellaneous/P...

That's not true. Maybe that's the impression it gives off, but it's a very good package that blows Nagios out of the water. It's UI/UX needs work and some things are a bit quirky (to say the least), but it scales well, works quickly out of the box (basic level), has decent and improving API, integrated graphs, etc.

It's not perfect and suffers from the same problems as other monitoring systems, but given the options it's better then most systems with similar scope.

P.S. I am not affiliated with them in any way shape or form. Just used it for a little while.

Keepass is a decent option for a smaller company (http://keepass.info/). It's a bit limited in a sense that it doesn't support multiple users that can view different password tiers, but it does an ok job at syncing changes by multiple users. I am sure there are plenty of decent commercial options.

I've seen some companies hack a homemade solution based on Truecrypt as well, though it's probably not very efficient.

You're right, my eyes were hurting from reading it. I had some time today and banged out a better and a more readable translation.(I hope).

http://mindend.com/index.php/interview-with-the-creator-of-n...

I spent a couple of years working for a company in a market research space. It's an interesting business of which I knew very little before I worked there. But the answer is that you could do a survey for a fraction of that cost. SurveyMonkey has the same product and so do a few others.

As an aside, google launched this about 6 months ago and pretty much has everyone in that business scared. Ultimately it all boils down to having profiles on a lot of users and selling access to them. Google's user base (and what they know about them) dwarfs what everyone else has combined. If they wanted to, with a bit of effort they could own that market in 6-12 months.

There isn't a great way to make it easy for the user. Assuming that the password is "something you know" you need to add either "something you have" or "something you are" to the mix. That will mean tokens/cell phones/computers/other physical objects or effective biometrics. There are some creative ways to deal with this, but no matter how you look at it; it still is an added inconvenience for the user.

Reminds me of this soccer match in 1994. Somewhat a similar situation, but it was treated as ridiculous, rather than unsportsmanlike. I think it was widely agreed that the rules were to blame instead of the players.

http://en.wikipedia.org/wiki/Barbados_v_Grenada_(1994)#Match