17
Working as a Rust dev (linux.community)
submitted 2 years ago by to c/rust@programming.dev
12 comments fedilink hide all child comments
 

What essential skills/knowledge would you say are/is required to work as a Rust dev?

I did couple of small/mediumish personal projects in Rust using axum with sea-orm and later tauri with leptos. That's on top of many years of experience working as a Java/Javascript dev and occasionally touching things like Python or Flutter. Most of things like databases and web stuff is transferable but what strictly Rust concepts are required to work as a Rust dev? In what fields it's used the most?

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 years ago (1 child)

Necessary skills:

  • Development processes: advanced git usage (like fixing history after a bad rebase, merging multiple completely divergent branches, etc), issue tracking
  • Devops: continuous integration, continuous deployment, Docker (also, how to build your own Docker images out of Rust projects), Kubernetes
  • Social: how to interact with coworkers without creating enemies for life
  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 5 points 2 years ago* (1 child)

    Don't forget debugging! Throughout my carreer, I never really forced myself to just go with debugger (especially since when games are considered, where you are dealing with tens of instances running the same Update, so manual breakpoints are usually harder to use than just scrolling through printed values in a lof) and over-relied on debug logging.

    It was a mistake, and took me several years to realize that conditional breakpoints are a thing. And once you get into profiling, memory optimization and what-not, you will be greatefull that you've spend the time getting comfortable with all the debugging tools you can use.

    Trying to learn a debugger or profiler as you go through solving a problem at a job sucks. Am currently in the process of having to debug and solve shader performance issue, and oh boy that's a lot of terms and tools I've never seen before, and most of the colleagues are as dumbfounded as I am, since when porting games you usually don't need to deal with low-level rendering.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    I'm comfortable with debugging, but I rarely use it with Rust. With the language being so strict in everything, it's clear most of the time what's happening, and most situations can be resolved by simple logging of variables.

    In JavaScript, I have to use the debugger all the time, since variables can get some really weird invalid values with the completely wrong type.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago

    That's my favorite part about rust. Each step of the program is so well defined. No wondering if something will be uninitialized, throw, be null, or worse, what type of data you are working with in the first place. The option and result types have made working in languages without them a slog.

  • permalink
  • fedilink
  • source
  • parent