QuizzaciousOtter

curl is obviously fantastic but for more complex ad-hoc requests I usually prefer httpie.

3 is not related to using git in any way. I’m not really sure what you mean in 4. I didn’t mean making a lot of changes, I meant that you should not wait with committing until you have a finished feature / fix / whatever. Commit after each refactor, commit after adding a new testable unit. It’s always better to have more checkpoints. If your team does code review, they will appreciate atomic commits too.

1. Use git for any code you write. Yes, even a simple script.
2. Commit and push often. More often than you think is reasonable. You can always rebase / fixup / squash / edit but you can’t recover what you didn’t commit.
3. ???
4. Profit.

Seriously, once you commited something to the repo it’s hard to lose it. Unless you delete .git. But a this point frequent pushing has your back.

I know git can be hard to grasp in the beginning. It was hard for me too. I highly encourage everyone to put in the effort to understand it. But if you don’t want to do that right now just use it. Just commit and push. It will pay off.

I mean, I am applying various kinds of science but I’m not actually doing any science so I’m not thinking about myself as a scientist. What I do is solving problems - I’m an engineer.

As a huge NixOS enthusiast I wholeheartedly agree with you. It works amazing for me but only because my autistic ass hyperfixated on it to the point of tinkering with it every afternoon for months.

I would love to be able to recommend NixOS to people but unfortunately, the lack of good documentation is a huge problem.

Wow, this is so fucking pretty! Unfortunately, I don’t really have a need for local music files player, but I love it.