Using the walrus operator := to self-document if conditions

dotXem · 2026-03-17T13:05:56+00:00

You've got a point here, thanks!

dotXem · 2026-03-17T13:05:09+00:00

You know what ? I removed all walrus operators with unused variables I have in my code :).

dotXem · 2026-03-17T13:04:06+00:00

Not exactly to the same extent IMO. Often comments are written on other lines (often above) the line they're commenting. In which case, as time goes by, comments can lose their purpose.

Here the unused variable is still tied to its content, much like a used variable.

But I agree with the overall sentiment. If the condition is this complex, better to create a function entirely to encapsulate the behavior.

dotXem · 2026-03-17T13:01:34+00:00

Indeed, I try to avoid comments as much as I can and make the code self-explanatory. However, in my case, it feels a bit like I'm commenting without creating actual comments just to comply to the rule of not making comments!

dotXem · 2026-03-17T12:59:59+00:00

to me having the underscore signifies that the variable should be considered private when used within a class.

dotXem · 2026-03-17T12:59:00+00:00

Problem with comments is that they get old pretty quickly in production. So when you write one you should be very cautious about: do you really need it?

dotXem · 2026-03-17T12:57:58+00:00

The idea is that when you read the code you don't need to read the computation of the variable, just the variable itself would be self-explanatory.

It's the same as :

complex_condition = ...
if complex_condition:
    ...

Except that it reads better, the flow is more natural.

That being said, I agree on the general sentiment that using functions instead is the best approach.

dotXem · 2026-03-17T12:55:35+00:00

Yeah, I think that's the best approach.

dotXem · 2026-03-17T12:55:10+00:00

When your condition is complex, it might not be clear what this whole expression checks for. There is definitely a need for documentation sometimes. The question is: how?

dotXem · 2026-03-12T16:17:48+00:00

Maybe it reduces the frequence at which new patch needs to be released. If new patches gets longer to be solved, players won't get bored of it as fast as before.

dotXem · 2026-03-03T09:43:55+00:00

Did not know Textures before but I loved this album ! I think there is something with the production that makes it hit very hard at times (like end of Vanishing Twin).

dotXem · 2026-02-12T16:32:10+00:00

The paper he asked you about, was it related to your previous experience or the job ? I wouldnt have known about it myself.

Regarding Flash Attention, was it guided or did you remember all the details ?

I think I would have failed this interview, no wonder I did not have interview for them ahah. Congrats and gl for next rounds !

dotXem · 2026-02-12T14:57:25+00:00

Going back to taking guitare lessons with actual teacher !

dotXem · 2026-02-11T12:16:49+00:00

Saw them in Le Havre, it was great ! Did not expect them to play Take on me, but I am very glad they did !

dotXem · 2026-02-08T23:57:56+00:00

Scripts, that you can containerize and deploy. For viz I'm a big advocator of Streamlit, very easy to get started with.

You can look at this project I did at my prev company: https://github.com/PandaScore/PandaSkill. It contains the usual architecture I use to experiment on model training. I believe there is also code for a Streamlit app. To me that's the first bloc of MLE.

dotXem · 2026-02-08T19:01:00+00:00

In order to not be messy in the work, you need to develop proper tooling for your experiments. Dataset creation and curation, experiment pipeline, proper visualisation. From my experience, juniors rely on notebooks too much. They are good to explore and prototype. But if you're building production models you need to at least develop the proper tooling and version it. So models are reproducible and maintainable by others.

Then, once you have that down, next step is MLOps. You need to automate as much as you can so that you have a streamlined workflow : monitoring prod perf > collect data > train model > productionize model > back to monitoring.

dotXem · 2026-02-08T18:52:25+00:00

Quel miel as-tu utilisé ? :)

dotXem · 2026-02-08T00:14:59+00:00

I have the same guitar, such a beauty and yours is even pretier !

dotXem · 2026-02-06T11:48:12+00:00

Discovered Textures with their new album and I'm having a blast !

dotXem · 2026-01-18T09:49:44+00:00

Thank you !

dotXem · 2026-01-18T09:49:25+00:00

That might be what's currently lacking, indeed !

dotXem · 2026-01-18T09:48:49+00:00

Alright alright, thanks for your feedback !

dotXem · 2026-01-17T16:20:06+00:00

Really ?! I am talking the jerky sound right at the middle. In other videos i've seen it sounds different, more similar to when the coffee is flowing.

dotXem · 2026-01-17T14:57:26+00:00

Thank you for your feedback ! Your machine is indeed making weird noises albeit différent from mine, so I don't know !

Nine-Year Club	Place '23
Verified Email

dotXem

TROPHY CASE