home.social

Search

16 results for “teamtype”

  1. Imagine a protocol like , but for adding real-time collaboration to existing text editors. It would allow to edit a , or peer-to-peer pair programming between and !

    We've come up with our own little protocol like that (for Teamtype), but we'd like to open up the discussion:

    That's why we're inviting everyone interested to an initial online gathering on Feb 26, 19:00 UTC, to gauge interest for working on a protocol like this together!

    md.ha.si/collaborative-editing

  2. Currently, I'm often and couldn't really keep up to @teamtype's development speed for the plugin. My little 14 year old laptop cannot really run IntelliJ anymore. Really annoying how much RAM it consumes.

    My desktop PC can: with waypipe and wayback-x11 one can run it remotely. Here is a sketched CLI invocation:

    wayback ssh user@host wayback-session idea

    I must use wayback-session because of isn't merged into mainline, yet.

  3. We (CompSci/Engineering folks which have no issue in principle with LaTeX) had a bit of a discussion of buying an #Overleaf subscription or license, which I’m highly critical of, partially because nobody could tell me yet how much it costs.

    Oh, and which problem it solves. “Everybody else is using it” also applies to cocaine, so it’s mostly not having git merge conflicts, it’d seem. No one seems to be using simultaneous editing, though.

    Investigation ongoing. @teamtype + LaTeX when? 😇

  4. We (CompSci/Engineering folks which have no issue in principle with LaTeX) had a bit of a discussion of buying an #Overleaf subscription or license, which I’m highly critical of, partially because nobody could tell me yet how much it costs.

    Oh, and which problem it solves. “Everybody else is using it” also applies to cocaine, so it’s mostly not having git merge conflicts, it’d seem. No one seems to be using simultaneous editing, though.

    Investigation ongoing. @teamtype + LaTeX when? 😇

  5. We (CompSci/Engineering folks which have no issue in principle with LaTeX) had a bit of a discussion of buying an #Overleaf subscription or license, which I’m highly critical of, partially because nobody could tell me yet how much it costs.

    Oh, and which problem it solves. “Everybody else is using it” also applies to cocaine, so it’s mostly not having git merge conflicts, it’d seem. No one seems to be using simultaneous editing, though.

    Investigation ongoing. @teamtype + LaTeX when? 😇

  6. We (CompSci/Engineering folks which have no issue in principle with LaTeX) had a bit of a discussion of buying an #Overleaf subscription or license, which I’m highly critical of, partially because nobody could tell me yet how much it costs.

    Oh, and which problem it solves. “Everybody else is using it” also applies to cocaine, so it’s mostly not having git merge conflicts, it’d seem. No one seems to be using simultaneous editing, though.

    Investigation ongoing. @teamtype + LaTeX when? 😇

  7. We (CompSci/Engineering folks which have no issue in principle with LaTeX) had a bit of a discussion of buying an #Overleaf subscription or license, which I’m highly critical of, partially because nobody could tell me yet how much it costs.

    Oh, and which problem it solves. “Everybody else is using it” also applies to cocaine, so it’s mostly not having git merge conflicts, it’d seem. No one seems to be using simultaneous editing, though.

    Investigation ongoing. @teamtype + LaTeX when? 😇

  8. #TIL 🤓 There is a concept called "Architectural Decision Record" #ADR, see adr.github.io/.

    ADRs are used to document architecture decisions in software project to facilitate discussions in the (far) future.

    I think with the same motivation also non-software-related important decisions in teams and other collaborative groups should be systematically documented.

    Thanks to @blinry and @zormit who talked about this topic within their @teamtype talk at recent @clt_news

    Record of the talk, see

    fosstodon.org/@teamtype/116306

  9. #TIL 🤓 There is a concept called "Architectural Decision Record" #ADR, see adr.github.io/.

    ADRs are used to document architecture decisions in software project to facilitate discussions in the (far) future.

    I think with the same motivation also non-software-related important decisions in teams and other collaborative groups should be systematically documented.

    Thanks to @blinry and @zormit who talked about this topic within their @teamtype talk at recent @clt_news

    Record of the talk, see

    fosstodon.org/@teamtype/116306

  10. #TIL 🤓 There is a concept called "Architectural Decision Record" #ADR, see adr.github.io/.

    ADRs are used to document architecture decisions in software project to facilitate discussions in the (far) future.

    I think with the same motivation also non-software-related important decisions in teams and other collaborative groups should be systematically documented.

    Thanks to @blinry and @zormit who talked about this topic within their @teamtype talk at recent @clt_news

    Record of the talk, see

    fosstodon.org/@teamtype/116306

  11. #TIL 🤓 There is a concept called "Architectural Decision Record" #ADR, see adr.github.io/.

    ADRs are used to document architecture decisions in software project to facilitate discussions in the (far) future.

    I think with the same motivation also non-software-related important decisions in teams and other collaborative groups should be systematically documented.

    Thanks to @blinry and @zormit who talked about this topic within their @teamtype talk at recent @clt_news

    Record of the talk, see

    fosstodon.org/@teamtype/116306

  12. #TIL 🤓 There is a concept called "Architectural Decision Record" #ADR, see adr.github.io/.

    ADRs are used to document architecture decisions in software project to facilitate discussions in the (far) future.

    I think with the same motivation also non-software-related important decisions in teams and other collaborative groups should be systematically documented.

    Thanks to @blinry and @zormit who talked about this topic within their @teamtype talk at recent @clt_news

    Record of the talk, see

    fosstodon.org/@teamtype/116306

  13. We're at the of the @PrototypeFund today, where @zormit will be in a panel on local-first software! :)

  14. We confront Tom, who tries to manipulate us. Then we choose what our truth is, move on and we live happily ever after! Hope you enjoyed this game as much as I did, and that you are also #TeamTyler 😁

    youtu.be/vMqIpny44fA

    #TellMeWhy #Gaming #Youtube #FirstPlaythrough

  15. Zo, vandaag voor het eerst aan de kust geweest en mijn favoriete tramtype voor het eerst (en laatst) in éénrichtingsversie gezien.
    Ik moet zeggen: ze zijn lelijk verbouwd, maar in het echt niet zo lelijk als ik had verwacht.

    Het achterbalkon is wél supergaaf! Dat zou een mooie zithoek zijn!

    #kusttram #BN #LRV