fargate-game-servers VS sourcegraph

AWS - GameTech

Visit https://aws.amazon.com/gametech/ to get started today!

Even if BSG came out tomorrow and publicly released their entire server topology/infrastructure, then said "here's what's consistently failing under too much load; somebody with expertise please help us fix it", there'd still be 10+ people all making blanket suggestions like "jUsT pUT iT In ThE ClOuD!!! It's this easy!", without a single iota of a nuance or a detailed solution offered. As if it's just a matter of calling fucking CDW or something and having their "experts" migrate your product into your elastic computing partner of choice over a weekend, JFC.

Also curious, maybe it was mentioned by Scott in an interview. Amazon Game Tech has many hosting solutions not just EKS.

Amazon Web Services (AWS - Game Technologies group)| Various roles | Seattle (though currently WFH) | Full-time, Onsite | https://aws.amazon.com/gametech/

I am the senior manager (skip-level manager) for these roles so feel free to email me with questions (contact info in my profile). We have multiple mid-level (experience expected) software development engineering roles open. We work on cutting edge tech that helps games and simulations run on AWS and scale in ways they couldn't alone. I am looking for people with distributed service development (we do most of this in Java), and game engine/game dev experience (preferred Unreal). We're building an all new AWS service, solving hard technical problems, and we get to have games as a customer, which is pretty awesome to me.

Links: (service focused SDE role) https://www.amazon.jobs/en/jobs/1365397/software-development..., (game engine role) https://www.amazon.jobs/en/jobs/1365399/software-development...

Game Server Hosting on AWS Fargate This repository contains an example solution on how to scale a fleet of game servers on AWS Fargate on Elastic Container Service and route players to game sessions using a Serverless backend. Game Server data is stored in ElastiCache Redis. All resources are deployed with Infrastructure as Code using CloudFormation, Serverless Application Model, Docker and bash/powershell scripts. By leveraging AWS Fargate for your game servers you don't need to manage the underlying virtual machines.

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

Despite their shitty rug-pull <https://github.com/sourcegraph/sourcegraph/pull/53345>, I do really like Sourcegraph and one doesn't (currently?!) need to be logged in to use it: https://sourcegraph.com/search and they have a handy rewrite pattern such that one can just plug the repo path into the URL for quick searching e.g. https://sourcegraph.com/github.com/JetBrains/intellij-commun...

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...