synth VS sourcegraph

SEEKING FREELANCER | London | Remote

Synth (YC S20) [1] is an open source declarative data generator written 100% in Rust.

We are looking for someone with prior experience writing Rust in production for a 1-to-3 months contract to work with us on our core open-source project.

- Proven experience writing production Rust code, preferably in a large code base

- Knowledge of PostgreSQL at a level sufficient to design and build reliable integration

- Strong knowledge of data structures and algorithms

- Track record of contribution to open-source projects, preferably on GitHub

- Ability to work quickly and rigorously in a fully remote setting

If that sounds interesting, we want to talk to you! Shoot me an email at damien [at] getsynth.com!

[1]: https://github.com/getsynth/synth

Synth | Rust Software Engineer | Full Time or Part Time | London | Onsite(London)/Remote

About us: Synth is an open source declarative data generator (https://github.com/getsynth/synth). We are building Synth with the intention of solving, once and for all, the problem of generating realistic data for testing - helping big companies and small developers avoid the use of production data in testing.

Our mission is to build amazing developer tools that solve data privacy without forcing users to compromise on productivity. We have a few exciting products in our pipeline and we're backed by YCombinator and other great investors. We're based in London and building a remote-friendly culture.

We work exclusively on open source software. This is great because our community is not confined to just our core team and the users, but also includes our contributors - we believe it is way more fun this way.

We're using Rust for our main line of products - and what we would like to see ideally is:

* You have some experience with Rust that has connected you with at least one of: asynchronous I/O, meta-programming or common patterns for concurrency. Having been involved in an open-source Rust project is a bonus!

Take a look at this rust library (which works very well with python modules which generate data in certain formats): https://github.com/getsynth/synth

Putting the finishing touches on a procedural macro to bind Rust code to koto we want to use in synth. Also a blog post about it is on the way.

I'm working on synth https://github.com/getsynth/synth . Also working on a personal project, implementing the tcp protocol in Rust for the fun of it.

We use Rust to build synth, the open source declarative data generator.

Hey HN! We're Synth - a bunch of engineers out of Europe building tooling for developers. We're very excited about what we're working on and wanted to share it with the community.

We've been quite frustrated with the status quo of test data generation - after speaking to tons of other devs we've realised that many people are struggling when it comes to generating realistic looking test data.

Also, where people don’t want to copy sensitive production data to testing environments, data obfuscation can be a huge time-sink.

Enter Synth: a declarative data generator (see our website: https://getsynth.com/, github: https://github.com/getsynth/synth)

Synth enables devs and dev teams to have their application data models as code (basically a hierarchy of files) in their repos. These files can then be used to generate data for a local dev environment, automated testing in CI or even for sharing across organisations. The parameters of generation can also be tweaked to push the data model to its limits for QA, and even scaled for load testing / performance testing.

We're now working on taking the next step, and building a DSL around Synth. The Synth DSL will enable users to concisely define what data should look like and get going.

We're open source and written 100% in Rust. We believe that by making test data be as easy as using production data, we can improve the security and privacy for all of us. We'd love to get more early users as the initial feedback is positive but limited.

Thank you and looking forward to any feedback / ideas about how we can build a better tool for you!

P.S. Synth [launched on HN a while back](https://news.ycombinator.com/item?id=24198114) as an ML solution to create realistic (and safe) copies of your sensitive production data as a service. This approach quickly hit several limitations which couldn't address the use-cases we are trying to solve, happy to go into more details on this if anyone is interested.

I'm currently trying to improve the vtable dispatch in koto (because I want to use it in synth).

Luckily, not all Rust jobs are crypto jobs. I'm in my third Rust job working on synth right now and am 100% happy with it.

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