Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)R

robinm

@ robinm @programming.dev

Posts
2
Comments
133
Joined
2 yr. ago

  • This Week in Rust 555 · This Week in Rust

    Jump

  • The quote (and the associated discussion) is such an important part of Rust and why I love this language so much. Anything that can be automated should at one point be automated reliably, and the sooner the better.

  • What were your misconceptions about Git when you first started?

    Jump

  • It's a question of workflow. Git doesn't guide you (it's really workflow agnostic) and I find it easier to taillor CLI to fit my exact need, or use whatever was recently added (like worktrees a few years ago). I have yet to find a GUI/TUI that I'm not frustrated with at one point but everyone has its own preferences.

  • What were your misconceptions about Git when you first started?

    Jump

  • If you use the git command line (and I do) you should spam git log --graph (usualy with --oneline).

    And for your filesystem example I sure do hope you use tree!

  • Cannot follow @pid_eins@mastodon.social

    Jump

  • Thank you! I didn’t realized that I was using my lemmy account and not my mastodon account.

  • isBooleanTooLongAndComplex

    Jump

  • I absolutely agree that method extraction can be abused. One should not forget that locality is important. Functionnal idioms do help to minimise the layer of intermediate functions. Lamda/closure helps too by having the function much closer to its use site. And local variables can sometime be a better choice than having a function that return just an expression.

  • isBooleanTooLongAndComplex

    Jump

  • Good advice, clear, simple and to the point.

    Stated otherwise: "whenever you need to add comments to an expression, try to use named intermediate variables, method or free function".

  • Most Tech Jobs Are Jokes and I Am Not Laughing

    Jump

  • A fun read but it really seems that his writting style is hit or miss!

  • Deleted

    ...

    Jump

  • I never understood why python won agaist ruby. I find ruby an even better executable pseudo code language than python.

  • Doom-htop: The classic DOOM game over htop

    Jump

  • Modern Git Commands and Features You Should Be Using

    Jump

  • It's so anoying that at $WORK we have multiple git repos with symbolic link that points above their respective .git to each other and need to be in sync. So of course git workree and git bisect don't work that well…

  • Modern Git Commands and Features You Should Be Using

    Jump

  • For those who don't know (I assume you do), you can git bisect run some_command and git will automatically run git bisect until it finds the falty commit. It's amazing.

  • Any tips to help a scientist become a better programmer?

    Jump

  • Read your own code that you wrote a month ago. For every wtf moment, try to rewrite it in a clearer way. With time you will internalize what is or is not a good idea. Usually this means naming your constants, moving code inside function to have a friendly name that explain what this code does, or moving code out of a function because the abstraction you choose was not a good one. Since you have 10 years of experience it's highly possible that you already do that, so just continue :)

    If you are motivated I would advice to take a look to Rust. The goal is not really to be able to use it (even if it's nice to be able able to write fast code to speed up your python), but the Rust compiler is like a very exigeant teacher that will not forgive any mistakes while explaining why it's not a good idea to do that and what you should do instead. The quality of the errors are crutial, this is what will help you to undertand and improve over time. So consider Rust as an exercice to become a better python programmer. So whatever you try to do in Rust, try to understand how it applies to python. There are many tutorials online. The official book is a good start. And in general learning new languages with a very different paradigm is the best way to improve since it will help you to see stuff from a new angle.

  • The Git Parable

    Jump

  • I reread that article every years for a few years. Each time my understanding of git improved significantly.

  • What was your “aha” moment when you finally understood Git?

    Jump

  • I reread that article every years for a few years. Each time my understanding of git improved significantly.

  • What was your “aha” moment when you finally understood Git?

    Jump

  • Should I file a bug report? 😀

    Jump

  • I wasn't clear enough. But in a contry where the sun rise at 20:00, the weekday looks like:

    • day 1: Monday morning to Tuesday evening
    • day 2: Tuesday morning to Wednesday evening
    • day 3: Wednesday morning to Thurday,
    • …

    And phares like "let's meet on Tuesday“ without hour indication could either mean end of day 1 or start of day 2. Likewise "let's meet the 20th” (assuming the 20th is a Tuesday) could either mean end of day 1 or beggining of day 2.

    --

    And alternative be to have

    • day 1 == Monday == “end of the 19th” to “the start of the 20th”
    • day 2 == Tuesday == “end of the 20th” to “the start of the 21st”
    • day 3 == Monday == “end of the 21st” to “the start of the 22nd”
    • …

    Which solve the issue of "let's meet on Tuesday”, but not “let's meet the 20th”.

  • Should I file a bug report? 😀

    Jump

  • The issue is that the notion of "tomorrow" becomes quite hard to express. If it’s 20:00 when the sun rose, when does tomorrow starts? In 5 hours ?

  • Which red is your function?

    Jump

  • Interesting idea indeed. I've never used async yet, but I'm always surprised at how the problem space seems to be much more complicated than what it initially looks like.

  • Which red is your function?

    Jump

  • You shouldn't, it's short and interesting