akvo-flow VS sourcegraph

Akvo | Frontend developer | Remote or Burkina Faso | +- 2hours CET/CEST | Full time | https://akvo.org/join-our-team/

We believe that sustainable change will happen faster if governments and non governmental organisations become more effective, accountable and collaborative. With a team of data and development experts, a solid and scalable open source data platform, and a proven methodology, we help our partners power their decisions to achieve inclusive and sustainable impact. We support the improved management of water, sanitation and agriculture and have a strong commitment to the sustainable development goals.

Together with our diverse team, you are driven to create valuable products that enhance Akvo’s impact. You are able to figure things out yourself and know when to involve the rest of the team. You always keep pushing to understand why certain things are the way they are or what the root cause of a problem is while being willing to learn and stay at the forefront of current technologies. You do not shy away from complexity and unknowns, you take initiative, and you understand how to split things up in clever ways, so we ship step-by-step and learn from it quickly.

We value a great eye for good UI, experience with JavaScript, React, Clojure, ClojureScript, Java, Ember and a willingness to learn.

Some projects you will work on is Akvo Lumen (https://github.com/akvo/akvo-lumen) & Akvo Flow (https://github.com/akvo/akvo-flow). To learn more and apply for this position see https://akvo.org/join-our-team/, please send portfolio links, your motivation letter and a resume all in English to the attention of Daniel Sunnerek to [email protected].

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...