• 1 Post
  • 26 Comments
Joined 1 year ago
Cake day: October 21st, 2023
  • sorter_plainview@lemmy.todaytoProgramming@programming.dev•Git Commit Creation
    1·
    1 month ago

    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?

  • sorter_plainview@lemmy.todaytoProgramming@programming.dev•Git Commit Creation
    1·
    1 month ago

    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?

  • sorter_plainview@lemmy.todaytoProgramming@programming.dev•Git Commit Creation
    3·
    2 months ago

    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?

  • sorter_plainview@lemmy.todaytoTechnology@lemmy.ml•China Intensifies Push to ‘Delete America’ From Its Technology
    22·
    8 months ago

    Yes it is not in alignment with the spirit of open source. In the “industrial districts” there is no validity for copyrights. Means if one company developed something, any other can adapt it without any restriction, even without a license. This is very counter intuitive to our capitalistic rules. But this policy essentially forces you to make progress as quick as possible, else someone else will adapt it and make a product out of it. Then you lose all the market.

    China is forcing companies to make money out of capitalistic economies, but restricts the “knowledge” or “technology” accumulation into a few mega corporations.

    At least this is the theory. But as everywhere else corruption and hunger for power screws up things in China also.