GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Tek say resist (tek@freeradical.zone)'s status on Friday, 11-Nov-2022 18:44:47 JST Tek say resist Tek say resist

    How to Hold a Good Meeting: Rusty’s Rules of Order: https://www.iww.org/resources/rustys-rules.pdf

    Angry? Had enough? Ready to organize and make a difference? Here’s a set of well-tested social hacks, brought to you by the IWW, to help you herd a roomful of cats. Make your meetings shorter and more productive so that you can spend your efforts on actions instead of endlessly arguing about them.

    In conversation Friday, 11-Nov-2022 18:44:47 JST from freeradical.zone permalink

    Attachments


    • Embed this notice
      Fubar (fubar@freeradical.zone)'s status on Friday, 11-Nov-2022 18:44:46 JST Fubar Fubar
      in reply to

      @tek We had consensus minus the twat for meetings, it was pretty effective :P

      In conversation Friday, 11-Nov-2022 18:44:46 JST permalink
    • Embed this notice
      fu (fu@libranet.de)'s status on Friday, 11-Nov-2022 18:45:40 JST fu fu
      in reply to
      • Fubar
      @tek @fubar I'd like to see the documentation on this
      In conversation Friday, 11-Nov-2022 18:45:40 JST permalink
    • Embed this notice
      FilesWithThreateningAuras (iaintshootinmis@infosec.exchange)'s status on Friday, 11-Nov-2022 18:46:29 JST FilesWithThreateningAuras FilesWithThreateningAuras
      in reply to
      • KillerBean ✅

      @tek @KillerBean i like this one a lot as well.

      I saw a toot previously that said something like "stop scheduling meetings to hold me hostage as a rubber duck." Or something to that effect

      https://en.m.wikipedia.org/wiki/Rubber_duck_debugging

      In conversation Friday, 11-Nov-2022 18:46:29 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: upload.wikimedia.org
        Rubber duck debugging
        In software engineering, rubber duck debugging (or rubberducking) is a method of debugging code by articulating a problem in spoken or written natural language. The name is a reference to a story in the book The Pragmatic Programmer in which a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by-line, to the duck. Many other terms exist for this technique, often involving different (usually) inanimate objects, or pets such as a dog or a cat. Many programmers have had the experience of explaining a problem to someone else, possibly even to someone who knows nothing about programming, and then hitting upon the solution in the process of explaining the problem. In describing what the code is supposed to do and observing what it actually does, any incongruity between these two becomes apparent. More generally, teaching a subject forces its evaluation from different perspectives and can provide a deeper understanding. By using an inanimate object, the programmer can try to accomplish this without having to interrupt anyone else. This approach has been taught in computer...
    • Embed this notice
      Tek say resist (tek@freeradical.zone)'s status on Friday, 11-Nov-2022 18:46:30 JST Tek say resist Tek say resist
      in reply to
      • FilesWithThreateningAuras
      • KillerBean ✅

      @KillerBean @Iaintshootinmis Also, “what’s the output of this meeting going to be?”

      In conversation Friday, 11-Nov-2022 18:46:30 JST permalink
    • Embed this notice
      FilesWithThreateningAuras (iaintshootinmis@infosec.exchange)'s status on Friday, 11-Nov-2022 18:46:31 JST FilesWithThreateningAuras FilesWithThreateningAuras
      in reply to
      • KillerBean ✅

      @KillerBean @tek i do this sometimes by replying Am I expected to provide a deliverable for this meeting? Or, am I being consulted or informed?

      If you can tell me what you need via email, I'll use the meeting time as a working session on my calendar to produce the deliverable. (A report, etc...)

      If I'm being consulted, please provide any foundational information and documentation so i can knowledgeably assist. Along with any direct questions.

      If being informed, please provide the following in one to two sentences each.
      What is happening?
      Why is it happening?
      When is it happening?
      What should I do?

      This is usually enough to convey that I'm not attending nonsense meetings when I could be learning, or building cool stuff, or solving Ops issues, etc...

      In conversation Friday, 11-Nov-2022 18:46:31 JST permalink
    • Embed this notice
      KillerBean ✅ (killerbean@freeradical.zone)'s status on Friday, 11-Nov-2022 18:46:34 JST KillerBean ✅ KillerBean ✅
      in reply to

      @tek for years I just don't attend meetings without an agenda. If asked why I wasn't there I say, "There was nothing for an agenda. I had more important things to do than nothing." Only asked 2-3 times.

      In conversation Friday, 11-Nov-2022 18:46:34 JST permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.