I’m in the 1%

This whole section of the graph will be that invisible part on the left in a couple years. Going up and down is normal as long as it’s trending up.

This is going to be a boring answer but I use neovim. I do use it as my ide as well but it’s so fast and lightweight that when I need to edit a random config file or something, I just start another instance of it.

“Reapply” is rewriting it on the other branch. The branch you are rebasing to now has a one or multiple commits that do not represent real history. Only the very last commit on the branch is actually what the user rebasing has on their computer.

Always merge when you’re not sure. Rebasing rewrites your commit history, and merging with the squash flag discards history. In either case, you will not have a real log of what happened during development.

Why do you want that? Because it allows you to go back in time and search. For example, you could be looking for the exact commit that created a specific issue using git bisect. Rebasing all the commits in a feature branch makes it impossible to be sure they will even work, since they represent snapshots that never existed.

I’ll never understand why people suggest you should default to rebasing. When prompted about why, it’s usually some story about how it went wrong and it was just easier to do it the wrong way.

I’m not saying never squash or rebase. It depends on the situation but if you had to pick a default, it should be to simply merge.

That is absolutely not what rebasing does. Rebasing rewrites the commit history, cherry picking commits then doing a normal merge does not rewrite any history.

Does windows not have the concept of “recents” so you can find things you were just messing with easily

Vampires don’t show up in mirrors because they don’t exist in that other dimension

Maybe I’m not an amazing perfect person. Maybe I should try some introspection and look critically at my own thoughts and actions.

Fuck the wolves

Cuddle the wolves

I agree but with more and more users, that will happen naturally.

As someone who uses Django every day, I can tell you that the code is almost secondary to the amazing documentation. The documentation is such a core part of a framework that I don’t see how it can be usable without really good and up to date documentation.

The fact that spring boot’s documentation is so bad that it’s impossible to even find a reference for a class you’re using is, I’m sorry to say, garbage.

I know some people don’t have the choice but if you do, please choose something better. That garbage does not deserve your effort.

I’ve been using ivory, it’s nice

Even if it’s good, their long term goal will always be to appease their advertising customers, not you. Google has the ability more than anyone else to make the perfect search engine but they’re not spending their time and resources on that because that’s not what will increase their revenue. That model is just fundamentally broken.

I love kagi. I use it mainly for work, where it gives much better results. It even has a programmer lens so that it shows results that are relevant to programmers. But its image search didn’t work that well for me. Not sure if I’m just not formulating the queries right though.

Yeah I guess it was hyperbole but I wasn’t sure

Is it really that bad? I haven’t used it in years so I’m not following it. Do they literally have a built-in keylogger?

Hello it’s me muscle memory have an e

Sometimes I miss that though. I remember seeing a tweet a while back that said something to the effect of “twitter is boring until the unemployed people wake up at noon and start their shit”. Unfortunately, it looks like everyone on mastodon is a normal employed adult, which isn’t as fun.