notabot

It’s always fun to get your offset slightly wrong, and jump into the middle of an instruction.

That’s a fantastic shot. I think it belongs in !accidentalrenaissance@lemmy.blahaj.zone too.

Instructions may have been unclear, but you got the gist of it.

Git itself is that for the DVCS part, it’s easy to host and is decentralized. I haven’t used it myself, but hubzilla seems to support wikis and forums in a distributed way. If you needed to, you could manage issues in forums, although it feels like there should be somethings.

That depends on your team composition. Decoupling story points and hours means that the points indicate the complexity of the task; each developer might take a different amount of time to deliver that depending on their ability and expertise in that part of the system. The points give you a simple metric to show how much complexity the team have left to deliver, and tasks get assigned to whoever is best placed to deliver them at the time.

“Gelatinous tuna mold concoction” is a concept I don’t want to have to think about ever again, and I ate similar things when I was a young’un.

Fastration?

The joys of distributed algorithms. You can now get more errors, more quickly than before!

I remember writing a chat system in assembler, for DOS, using, IIRC, IPX networking. When it went wrong, one or more machines would just freeze, with the string “NETWORK ABEND” in the middle of the screen.

I should fork vim and call it ‘death’, so I can shout “give me vim or give me death!” any time someone suggests a different editor.