• I Cast Fist@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    4 days ago

    Never saw anything like that, but I more or less gravitated towards something like that. Just Intro - Point 1 - Point 2 - Point 3 - Conclusion

    • Cethin@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      4 days ago

      Yeah, this is some basic stuff, but I guess it’s good to have formalized to teach people. I don’t recall what method I was taught, but it was something similar to this. I don’t ever remember using it so formally though. Just basically outline what you’re going to go over, and then fill it all in. I think almost all formal structures like this should be abandoned once you understand how they function, and it should be adapted to what works best for you. The formal version is just a starting point.

      • MintyFresh@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        4 days ago

        I think being super formal like this method really pays off when you have to collaborate. Far easier, more efficient and accurate to say “Look a section IV.c and tell me what you think.” Rather than “that one part with the dude, ya know”

        • Cethin@lemmy.zip
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 days ago

          Most writing outlines are for yourself though, but yeah, when it’s in an organization you need something formalized, at minimum just so you can quickly find what you need to find. If every person has their own system of organizing things then it’s going to be a mess.