tangram VS sourcegraph

Head over to https://www.tangram.dev and give it a try!

In this post, we will go over how we optimized our Gradient Boosted Decision Tree library. This is based on a talk that we gave at RustConf 2021: Writing the Fastest Gradient Boosted Decision Tree Library in Rust. The code is available on GitHub.

You can check out the Tangram Ruby Gem. We built it using Ruby FFI and the source is available on our GitHub repo.

We are using Rust for our web application and website at Tangram. You can view the source here: https://github.com/tangramdotdev/tangram/tree/main/crates/www. The website is at https://www.tangram.dev. We decided to write our own web framework because we needed server rendering and we wanted to use the builder pattern in creating components. Here is an example component for our Logo to get a sense of what this looks like: https://github.com/tangramdotdev/tangram/blob/main/crates/www/ui/logo.rs

Check out https://github.com/tangramdotdev/tangram.

Tangram | Senior Rust Programmer | Remote | https://www.tangram.dev

Tangram is an all in one machine learning framework designed for programmers. With Tangram, developers can train models and make predictions on the command line or with libraries for languages including Elixir, Go, JS, Python, Ruby, and Rust, and learn about their models and monitor them in production from a web application. To learn more about what the product does, watch the demo on the homepage at https://www.tangram.dev or check it out on GitHub at https://www.github.com/tangramdotdev/tangram.

We are looking to grow our engineering team with senior Rust programmers. We are currently based in Boston, MA but are looking to build a remote team. At Tangram, you'll get to work on everything from our core machine learning algorithms to writing front-end code in Rust! We are looking for developers with experience in Rust and familiarity with or willingness to learn machine learning concepts. If this sounds exciting, email me (Isabella, cofounder) at [email protected].

We chose to use Rust instead of TypeScript for the front end of https://github.com/tangramdotdev/tangram.

This allows us to:

* Share code with our server written in Rust.

I'm working on machine learning in Rust at Tangram. We currently only provide an implementation of linear models and gradient boosted decision trees but will move into exposing training of deep models in the future. You can check out Tangram here: https://github.com/tangramdotdev/tangram. You may also be interested in checking out Linfa https://github.com/rust-ml/linfa. If you're interested in the future of machine learning in Rust, check out Luca Palmieri's blog post: https://www.lpalmieri.com/posts/2019-12-01-taking-ml-to-production-with-rust-a-25x-speedup/

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