Let's break these down in more details, and remember: If you ever need a hand with this, just get in touch, we're happy to help! Qualities of a good first challengeĬhoosing a good first project with Rust is all about finding something big enough to give you real data, while being small or isolated enough to limit the total amount of time and effort invested, in case it doesn't pay off on your first try. How can we maximize the learnings from the first trial?.
How can we maximize rewards (reliability, efficiency, developer happiness).How can we minimize cost or risk to projects and timelines?.On the search for a first Rust project, we aim to answer these three questions: This is directed both at managers as well as engineers starting this process on their own. Picking the right first project can be hard! Since we have experience helping teams with this process, especially in selecting projects that are specific to them, we wanted to share some of our common guidance. The right "first project" aims to solve a problem in Rust that's isolated and compact, but still poses a realistic test case to assess whether Rust fits a team's needs. Instead, we suggest finding a good first project to take Rust for a test drive, so you can try before you buy. We don't generally advise folks to dive in head first, or to rewrite everything from scratch in Rust. Sometimes their engineering teams have started using the language unofficially and they'd like some help making it official, and other times we are approached by CTOs or Engineering leads who are interested to see if Rust can help their development team. At Ferrous, we often help folks who are in the "getting started" phase of using Rust.
0 kommentar(er)
