synth VS gdbstub

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.

now integrate gdbstub to support debugging code inside the emulator :)

Shameless plug, but have you considered integrating gdbstub rather than rolling your own debugger? I know a couple folks out there have successfully integrated it into their PS1 emulators with great success.

I've worked really hard to keep gdbstub panic free in its minimal configuration, going so far as to write some informal scripts that parse rustc's asm output to scan for the presence of panicking code paths.

crates.io | docs | repo

As a totally shameless plug, I'm the maintainer of gdbstub, a bare-metal, no_std, no_alloc, and size-optimized implementation of the GDB Remote Serial Protocol. One of the major changes slated for the upcoming release 0.6 is support for a new state-machine based API, which makes it possible to drive gdbstub directly via bare metal interrupt handlers (i.e: send/recv data over UART, handling breakpoints via the undefined instruction trap interrupt, etc...).

Continue working on a new API in gdbstub that'll make it easier to use directly from an interrupt handler when debugging code in a no_std, bare-metal OS environment.

I ran into almost this exact same problem while working on gdbstub, whereby I an API that allowed users to mix/match protocol features however they wanted, while also preventing users from accidentally implementing mutually-exclusive features. Moreover, I wanted to have a "zero cost" way to enable/disable API features without relying on cargo features. The solution I came up with is something I've been calling "Inlineable Dyn Extension Traits", or IDETs.

For a concrete example of how smart the Rust compiler is, I have a small writeup + test-repo that benchmarks a technique I came up with while working on gdbstub that [ab]uses the compiler's devirtualization and inlining optimizations to create runtime feature flags that are entirely compiled out if hard-coded to false at runtime.