DRY and YAGNI are awesome iif you also practice YNIRN (You Need It Right Now)! Otherwise you just get boilerplate of spaghetti
robinm
joined 1 year ago
You got me in the first 3 quarters, not gonna lie!
There are cases where instead of origin/master..HEAD you may want to use @{upstream}..HEAD instead to compare with the upstream of your current branch. It's unfortunately quite unknown.
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.
Thank you! I didn’t realized that I was using my lemmy account and not my mastodon account.
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”.
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 ?
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.
You shouldn't, it's short and interesting
Looks nice. It has a very good “wooow” effect
I would have liked a link to the LKLM thread. Usually they are quite informative
view more: next ›
Yes
Definitively not.