sorter_plainview

I think I got the idea. So essentially a new copy of the file is created and stored only if there is a change, else it just refer to the older SHA. Am I right? Now I understand why LFS was needed for binaries, else it createds a lot of storage problems, but not the huge monorepos.

I'm not a developer, but a design person who covers much more including architecture. But in my org I happen to teach developers how to use Git. Strange, I know. But that is the case. It gave me a good opportunity to learn Git in depth.

I went through your blogs and patch stack workflow. I have to say that I have not been happy with the branching workflow and I always felt that is not the best (I agree to the point about "unjust popularity"). The patch stack workflow makes more sense to me. Unfortunately we won't be able to adopt, since getting everyone to Git itself was a huge effort. Also developers are not that keen into creating good code, but just working working code. I'm extremely frustrated with that.

Also your blog design is really good. I love it. I always wanted to create something like that. But never managed to sit down and do it. Can you give me a brief about the tech stack used for the blog?

Do you use RNote for diagrams? The style looks familiar. Or is it something else?

Aah. I assumed linting was part of the build also. My bad. I did understand the idea you were mentioning. Just that assumptions kind of threw me off.

I wanted to ask something related to that. As you mentioned, git takes a snapshot of the repo on every commit. So splitting up the bug fix and other activities means you have 3 or 4 commits instead of one. Let us say we are dealing with a very large repo. This does not look ideal in that context right? So do you think the way you proposed is only suitable for smaller repos?

Oh, never heard of amnezia. Never needed actually. But it looks like a good improvement on Wireguard. I will need a separate setup to test it out and currently I'm away from home with no clue when I will return. If I happen to find anything, I will definitely ping you.

In the HN page you linked many people mentioned v2ray. Have you tried that? How good is it?

Have you considered having Headscale on a cheap VPS? We are actually doing that and it is pretty capable. IIRC, you can configure not to use the tailscale servers at all, and use your own public VPS for coordination. Bonus point, tailscale hired the Headscale developer and maintainer, and they are allowed to work on Headscale while on their payroll. The team looks very much into FOSS.

It was originally created for the satire book Our Dumb Century: The Onion Presents 100 Years of Headlines from America's Finest News Source

This is some next level meta.

So this bit confuses me. The article says in the intent and scope section that the entire process of bug fixing, in the included example, is literal bug fixing, clean up toggle, correct lints, correct duplication. That point to linting issues.

The earlier section says that a commit should be 'buildable' and 'testable'. So if there are linting issues, the commit won't satisfy this criteria right?

What am I missing here?

Unfortunately that is not how those graphs are plotted.

I found this in their GitHub repo.

Just out of curiosity, and I don't know anything about testing.

Is uuv is equivalent to Playwright + Cucumber?

Tried neovim a couple of times. Stopped after 10 or 15 mins. Anyone has useful tips to get used to vim/neovim?

I would say exactly that is what you have to describe. As I said certain things cannot be changed with therapy. It can only help you to get in terms with it.

Regarding the last point you mentioned. You are not giving up on her. Exerting constant pressure can't change certain realities. It is like thinking you can drain an ocean with a bucket and a lot of time.

You have to accept that there is nothing 'wrong' with your partner. If she is asexual there is nothing to 'cure'. You must build your life around this fact to be happy.

This does not mean that your needs should be discarded. In the same way you accept and respect the fact that she is asexual, she also has to take a mature stand and work on finding common grounds or compromises. That is how relationships work, isn't it?

You start therapy. Remember that you will need to find a suitable therapist. So don't hesitate to change therapists until you find one you are comfortable with. Maybe the therapist can help you on how this topic needs to be discussed with your partner. That may slowly open up new ways to improve the conditions.

No no.. Don't blame yourself. You did nothing wrong here. Very scientifically speaking we still have no clear answer on how the sexuality of a person is determined. So far there is a consensus that there is a biological factor also in play.

It is not your failure as a partner. These are things beyond your control. She also can't do much on this. Therapy won't change the underlying reality. It will just help you to cope up with the hard realities that you are facing.

I highly recommend you take individual therapy if you haven't done so far. You may have to untangle decades of experiences to get in terms with it. It's never late, and the right therapist will definitely improve how you handle this.