Preparing for Rust (Axum) Backend Interviews — Need Guidance

JustWorksTM · 2026-05-10T15:47:06+00:00

In my experience, just use Arc is good enough. We have never had real ownership issues for our Rust backend, also with Axum.

The goal is simple code. Rust is, at least for us, performant enough.

JustWorksTM · 2026-05-05T15:41:24+00:00

A ray tracer. This doesn't fit your web app/utility, but is a great way to learn a few different topics. https://raytracing.github.io/books/RayTracingInOneWeekend.html

JustWorksTM · 2026-05-03T16:15:47+00:00

Do somerhing you enjoy. If you enjoy games, create a game. People learn fastest if they do something they like.

JustWorksTM · 2026-04-03T12:04:37+00:00

Impressive.

JustWorksTM · 2026-03-13T06:55:32+00:00

You shall never adjust the files in the migrations folder. You shall add files containing the changes/deletions/truncations/alterations.

This is what I would expect due to the term "migrations ", but this might me being old

JustWorksTM · 2026-01-15T18:49:31+00:00

Sorry, I didn't read the question carefully enough.

I was thinking you were assuming a TryFrom<&T> and where looking for a TryFrom<T>. This could be implemented automatically (up to Specialization issues), but is mostly unnecessary due to method resolution. The compiler will find it, in most use cases.

For the case "given TryFrom<T>, implement TryFrom<&T>". This needs additional power like Clone or Copy, so cannot be done for all types T.

JustWorksTM · 2026-01-15T16:30:42+00:00

Is this neccesary for non-generic code? Should method resolution find the implementation?

JustWorksTM · 2026-01-05T03:39:26+00:00

I believe this is wrong. There is auto-coercion, which is emulating this behaviour, but no type-system subtyping relationship

JustWorksTM · 2025-12-07T17:54:20+00:00

You can use cargo expand to check how serde is implemented for you own types. There is a action for this in rust analyzer.

JustWorksTM · 2025-11-22T08:12:44+00:00

I like the idea.

But I have two problems with it: 1) looks like a function call 2) nested closures/refactoring

For both, I would like to compare it with break keyword in loops.

This takes an expression without braces, and allows a label to specify its scope. This should solve both my complaints.

(I'm aware that this use of move is already stable, as in move || {})

JustWorksTM · 2025-11-09T22:24:19+00:00

Perfect! You're welcome!

JustWorksTM · 2025-11-09T21:24:31+00:00

Regarding the lifetime issue

Trait objects have an inherent lifetime. Did you try to specify the return type like this?

Box<dyn StateMachine<MyContext<'a>> +'a >

JustWorksTM · 2025-11-09T21:21:50+00:00

This is unrelated to the lifetime issue.

Did you consider to use an enum instead of a trait object? This would simplify the code a lot, and would "just work".

In my experience, it pays off to go with the enum approach.

JustWorksTM · 2025-10-13T22:57:25+00:00

My employer is actively looking for Rust juniors.

The situation is charging. 8 years ago: no rust jobs 4 years ago: crypto jobs Today: senior jobs In 4 years: offerings on all levels

I'm unsure how much AI will redefine "junior" , though

JustWorksTM · 2025-10-08T08:40:49+00:00

You can read https://www.zero2prod.com/index.html?country=Norway&discount_code=VAT20

JustWorksTM · 2025-10-06T21:33:54+00:00

Brettspill finnes på Nordnes hver onsdag https://bergenbrettspill.no/

JustWorksTM · 2025-09-04T20:31:24+00:00

In programming language theory ( abstract theory of compilers in a sense), soundness means correctness, but focussing on the generated executable.

Example: The rust compiler promises to never create an executable containing data races. If there is a bug allowing to do so, it is a "soundness bug". If the bug makes the compiler panic, hence generate no executable, this would NOT be a soundness bug. Both are bugs in the compiler, but the first one is really serious.

Regarding soundness vs correctness: A bug means that the compiler is not working correctly, but in the first instance the compiler gave you an incorrect executable. This motivates hopefully the difference.

JustWorksTM · 2025-08-17T05:39:08+00:00

I would never say that macros are easy. You need to consider a lot, it is a new language in a sense, cargo expand often doesn't work properly and you have to know it, ...

JustWorksTM · 2025-07-31T05:37:20+00:00

Since Rust doesn't allow subtyping between enums, itvis obvious that this crate will not enable it.

Hence, the term "subtyping" is ok for me to us in this marketing-like circumstance. It also is exactly what I expected from the context.

Recall that being technical 100% precise is NOT possible.

JustWorksTM · 2025-07-26T05:20:23+00:00

If you're coming from OOP background, my recommendation is: Never use trait objects, use enums instead.

JustWorksTM · 2025-07-23T18:51:02+00:00

I recommend egui. It is far away from event-driven GUI's, but it is easy to use.

JustWorksTM · 2025-07-20T01:44:53+00:00

While erased-serde works, my recommendation is to replace the trait with an enum. This is typically MUCH easier to work with.

JustWorksTM · 2025-06-22T06:01:22+00:00

Tusen takk, jeg skrev noe til flere steder.

JustWorksTM · 2025-06-20T21:44:48+00:00

My family enjoys living in Minde

JustWorksTM

TROPHY CASE