And for anyone interested in a template:

top 39 comments

sorted by: hot top controversial new old
[–] 91 points 9 months ago (21 children)

What we need is some sort of distributed version control system.

I’m not quite sure how it will work yet, but it would have the entire codebase and its history mirrored onto every developer's computer. Instead of requiring a central repository, developers could share their changes directly with each other.

  • source
  • hideshow 21 child comments
  • [–] 29 points 9 months ago (5 children)

    but seriously, we need project management features that are decentralized: issue tracking, kanban, code reviews w/ comments, and ways to extend functionality without relying on a git forge.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 9 months ago

    For issues tracking there's the venerable git-bug, although development has sadly slowed way down in the last years.

    And I am always jealous of the way fossil repositories just have a complete front-end and wiki baked in, would love something like that for git.

  • source
  • parent
  • [–] 28 points 9 months ago (4 children)

    Maybe something on the blockchain??

    JK JK don't burn me on the public place!!

  • source
  • parent
  • hideshow 4 child comments
  • [–] 15 points 9 months ago (3 children)

    git itself is really not far from a blockhain. Blockchain is fine, it only has a bad rep because of ponzi schemes that use it to create crypto, but the technology and trustless consensus mechanisms are interesting.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 9 months ago (2 children)

    I think blockchain also has a bad rep because every chance is mirrored to every copy of the blockchain? Thus wasting a lot of power and bandwidth for most use cases. Unlike git, where you only push what you want, and everyone only pulls what they want.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 9 months ago (1 child)

    The waste of power is often associated to the proof of work consensus, but that's not a requirement of blockchain. There are other ways to create consensus.

    The bandwidth requirements really depend on what's being stored, but it's usually very manageable for a server. And clients not running validation don't need to store or transfer that much data.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 9 months ago (3 children)

    Is this sarcasm about git/svn or are you serious?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 25 points 9 months ago* (2 children)

    It was mostly a joke/irony.

    Git is already a “distributed version control system” that does exactly what I’ve described. On the other hand, relying on centralized systems such as GitHub means that the “distributed” nature of it doesn’t make it any more resilient to failure.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 9 months ago

    We need better distributed connectivity. It wouldn’t be that hard to build a project management system (issues, etc) on top of Git, but DVCS only gets you so far without a way to connect directly to the other contributors.

  • source
  • parent
  • [–] 34 points 9 months ago

    we are out of claude tokens

  • source
  • [–] 32 points 9 months ago

    "AWS is down".

    "And so is half the internet..."

  • source
  • [+] 29 points 9 months ago* (1 child)
  • [–] 13 points 9 months ago*

    Or in my case: Spending limit for GitHub Actions reached!

  • source
  • [–] 8 points 9 months ago (1 child)

    I briefly wrote Blackberry apps circa 2010 (yes, I knew RIM was dying a quick death). The development process was insane: any module from the framework that you incorporated into your app had to be digitally signed by RIM servers every time you tried to compile your app and deploy it to a device, even if you had only made a one-line change to the code. On good days, this would make the compilation take 5-10 minutes; on bad days it would be upwards of an hour or never happen at all. Some wags had even set up a special website that would tell you whether the RIM servers were down or not (long gone now, of course). I got in the habit of making a large number of code changes before attempting to run and test stuff, which is obviously not the ideal way to do things but it certainly teaches you to be careful. It also make me think long and hard before including a new module into my code. As one example, for my GUI I needed to use trigonometry functions which were naturally (lol) part of one of the cryptography modules which took an especially long time to get signed. I ended up writing my own sin() function in Java just to avoid the hit of including that module.

    The great part of this was that I always had a ready-made excuse whenever I felt like taking a long lunch or going shopping or going home early. "Sorry boss, the signing server is down" and I made damn sure they never knew about isthesigningserverdown.com. It also helped that it was Blackberry circa 2010 and it didn't make a shit bit of difference whether I got the app done or not.

  • source
  • hideshow 1 child comment
  • [–] 6 points 9 months ago

    Cleaned up the template a little and also removed the job role specifying "programmer" to make it even more of a flexible template:

  • source
  • [–] 6 points 9 months ago

    For me now it's that Anthropic services are down :/

  • source
  • [–] 6 points 9 months ago

    The new one will be "claude is pondering"

  • source
  • [–] 5 points 9 months ago (2 children)

    I've not worked anywhere that didn't own/maintain their own source control. Even privately I self host gitea.

  • source
  • hideshow 2 child comments
  • [–] 1 point 9 months ago (1 child)

    Git was designed specifically so people could work independently and not have to rely on a server. GitHub is not git. GitHub is an attempt to control the marketplace for code and exploit the network effects to lock people in and control them. It's facebook and linkedn for programmers. We never needed that and many of us never wanted that.

    You can do distributed development with git without any centralised infrastructure. It's what it was made for.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 9 months ago

    A classic. I sent this is general chat at work the last time that GitHub was down.

  • source
  • [–] 1 point 9 months ago

    "StackOverflow is down" is the more common cause where I work

  • source
  • [+] -6 points 9 months ago (2 children)

    Good thing about ai is it's never down. Code much better with it than stackbullshit

  • source
  • hideshow 2 child comments