fool

Obligatory Linux comment (Lemmy moment):

Windows is used often for its compatibility and defaultness but Linux is interesting in the sense that everything is patchable, everything is tinkerable and configurable. The low resistance to tinkering makes lots of Linux users tinkerers -- including tinkering via code.

I'm not saying wipe your hard drive or even dual-boot. Maybe an older computer or VM could help, depending on what you have. But just in the past week I've screwed around in low-to-medium-difficulty Linux projects that configured my lockscreen with C, that implemented mildly usable desktop GUIs with TypeScript, among others -- just not-too-committal stuff that has a return value I literally see every time I lock my computer.

Windows equivalent projects can be harsher on the beginning-to-intermediate curve (back when I first tried out Linux Mint, I'd been struggling to make a bookmark inspector in Visual Studio -- ended up Pythoning it instead) -- not to say that Windows fun is by any means out-of-reach.

My friends Leetcoded and Codeforced quite a lot. Advent of Code is up there too, with the interesting caveat that Advent of Code also teaches you refactoring (due to the two-part nature of every problem).

However, when I was younger I had contempt for the whiteboard-problem-esque appearances of these, but everyone is different.

If you look hard enough there is always a project at medium difficulty -- not way too hard, like a huge project you feel won't give you returns -- not way too easy, like some cowsay clone. Ever tried making a blog? You can host for free on most Git pages implementations (codeberg, github, gitlab...).

As for programming books, consider trying security books like Art of Exploitation -- in the same strain, CTFs can use a decent amount of code, and they're fun in terms of raw problem-solving. I started with the Bandit wargame, which does Linux problem solving from any machine that has SSH.

I'm not by any means a l33t hax3r but I found them pretty fun in my learning journey.

Despite the downvotes I'm interested why you think this way...

The common Lemmy view is that morally, papers are meant to contribute to the sum of human knowledge as a whole, and therefore (1) shouldn't be paywalled in a way unfair to authors and reviewers -- they pay the journals, not the other way around -- and (2) closed-source artificially intelligent word guessers make money off of content that isn't their own, in ways that said content-makers have little agency or say, without contributing back to the sum of human knowledge by being open-source or transparent (Lemmy has a distaste for the cloisters of venture capital and multibillion-parameter server farms).

So it's not about using AI or not but about the lack of self-determination and transparency, e.g. an artist getting their style copied because they paid an art gallery to display it, and the art gallery traded rights to image generation companies without the artists' say (although it can be argued that the artists signed the ToS, though there aren't any viable alternatives to avoiding the signing).

I'm happy to listen if you differ!

Isn't that because the peers also write stuff? So it's not just a fixed delay on one-by-one papers, but a delay that goes between peers' periods of working on papers too.

I... don't have ADHD (relatively confident) but I've used both of your hacks before and they've measurably helped me.

The templating thing slung me over its shoulder and carried me through battlefields. Procrastinate 'til the last hour? Assignment must be in LaTeX? Don't worry, everything is already formatted, just add the double-dollar-signs and equate!

Bored? Need to get this article done but it'll be even more boring? Watch random dubbed animations or something while hitting the keys -- low-pressure colors and music cushions the harder-thinking part. Somehow the perceived expenditure of I Need To Focus mutes itself!

(Footgun if the side-video is too interesting.)

First thing I'd ever seen on the darknet was this bad boy. (Not that it was a terribly efficient way to get an epub.)

Such a bottom-up book. Almost gave up back then, thinking I wouldn't be able to handle assembly, but then what would the point of reading about the hacker mindset be?

Lmao it's not Lemmy without Linux

~noh8~

Oh, you're right. You just pass the -d detach flag. I stand corrected!

According to tab autocomplete...

$ git
zsh: do you wish to see all 141 possibilities (141 lines)?

But what about the sub options?

$ git clone https://github.com/git/git
$ cd git/builtin
# looking through source, options seem to be declared by OPT
# except for if statements, OPT_END, bug checks, etc.
$ grep -R OPT_ | grep --invert-match --count -E \
"OPT_END|BUG_ON_OPT|if |PARSE_OPT|;$|struct|#define"
1517

Maybe 1500 or so?

edit: Indeed, maybe this number is too low. git show has a huge amount of possibilities on its own, though some may be duplicates and rewords of others.

$ git show --
zsh: do you wish to see all 489 possibilities (163 lines)?
$ man git-show | col -b | grep -E "^       -" --count
98

An attempt at naively parsing the manpages gives a larger number.

$ man $(find /usr/share/man -name "git*") \
| col -b | grep -E "^       -" -c 
1849

Numbers all over the place. I dunno.

Huh, TIL.

To be fair, git switch was also derived from the features of git checkout in >2.23, but like git restore, the manual page warns that behavior may change, and neither are in my muscle memory (lmao).

I'll probably keep using checkout since it takes less kb in my head. ~~Besides, we still have to use checkout for checking out a previous commit, even if I learn the more ergonomically appropriate switch and restore.~~ No deprecation here so...

edit: maybe I got that java 8 mindset

edit 2: Correction -- git switch --detach checks out previous commits. Git checkout may only be there for old scripts' sake, since all of its features have been split off into those two new functions... so there's nothing really keeping me from switch.

It probably is, but I think their main point is the protest against the age-old delineation into "GUI vs CLI" camps. I'm not saying that you're elitist, even if your statement might be interpreted as such (it's hard to communicate tone online but the quotations around "their workflow" could appear mocking), but regarding the structure of your statement, I had a "Windows users are all button-presser noobs" phase and would've typed something similar about the Git CLI if time was decently rewound (sans the kindness of a "use what you like" statement). They could be interpreting your statement as a propagation of the anti-GUI stereotyping.

Evidently they prefer GUI but can effectively use the CLI -- no one disagrees that the CLI is more functional.

You prevent them from waking up earlier, huh? Youngsters definitely have infinite energy at the odder times. I sure did my fair share of waking up early to increase the fraction of the day I gamed for.

This is a pretty convincing stance in favor of timers, actually. The idea of transferring video-watching from the iPad to the television is a friendly way to prevent an unchecked iPad-kid situation. My opinion shifted a little. :P

Do you have timers on the iPad for any mobile games, or just YouTube?