Mastodon: @canpolat@hachyderm.io

  • 161 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle































  • canpolat@programming.devtoSelfhosted@lemmy.worldPlex for books?
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    8
    ·
    9 months ago

    I know you said “self hosted”, but if you are interested in an Android app, Google Play Books does most of what you want, I think. You can upload your books, and read them on any device (with offline capabilities). But this is the Self Hosted community, so I will show myself out.



  • I think single account ActivityPub implementations are addressing a weakness of the Fediverse: one’s identity (handle, username) is tied to an instance they have no control over. If that instance shuts down users lose everything. With a single account instance, you take that control back. And since it doesn’t need to scale the architecture can be much simpler and can be deployed to much cheaper infrastructure.

    The demo was not straightforward, though. And I didn’t quite get how a user can follow Mastodon users, for example.


  • canpolat@programming.devOPMtoGit@programming.devDiff debugging
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    That’s explained at the end (Revisions). Fowler is probably looking for a general term that can be used to describe this specific way of debugging. Since he is aware of git bisect (and I’m sure he knows about hg bisect) there must be a reason he is not preferring “bisect debugging,” for example.

    Edit: The term diff has a clear link with version control. bisect is not that obvious. It may be ambiguous/vague in debugging context. I would still call it “bisect debugging.”





  • Apart from the historical value, the most important part of this article now is the “Note of reflection” added 10 years after it’s inception:

    If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.

    I don’t think this work flow is relevant any more even for teams that don’t do CD, to be honest. It was a messy work flow to begin with and I haven’t seen it applied successfully in practice.