Just an ordinary myopic internet enjoyer.

Can also be found at lemmy.dbzer0, lemmy.world and Kbin.social.

  • 0 Posts
  • 108 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle

  • I’ve tried to discern the context in which you’re asking this question, but based on the OP and their replies, I think it’s not so much about outlining than it is organizing details and thoughts before writing the initial rough draft. I might be wrong and that the OP‌ already knows about what I’d laid down below, but I hope even if it doesn’t help the OP, it might be of help to someone.

    Outlining is basically trying to organize your thoughts and all the details mapped out before writing. I assume that all the details are already laid out in one form or the other, and now it’s time to put them into order. What order things would be put into depends on what is being described or being explained.

    If I were to describe a house’s interior, I might go from the main door, then proceeding as if I’m physically walking through the house, and then describing objects I encounter as if I’m panning the camera.

    If I’m describing a person, I might go with the basic biographical details first, then an overview of their achievements, then personal life. Within each heading, for example, their personal life, I might go chronologically.

    If I’m describing a process, I might go with an overview of what the process is for, what are its inputs, steps needed to prepare the inputs for the process, and then the process itself in chronological order. Within each step, I‌ might go into the reasoning behind having to do this step, or why this step must go before (or after) some other step.

    If I’m describing an idea, I might go for a general definition first, then go more specific, discussing what makes each specific definition different from the others. I might then go for a quick historical overview of how this idea came into being, what ideas have led to this idea, and the thinkers that have contributed to building up this idea.

    That is, there’s a lot of approaches you can use to organize your ideas. You can organize your ideas or details based on location. That is, organizing details spatially, like describing a house’s interior. You can organize your ideas based on time, which came first, which comes next, like describing a process. You can also organize your ideas from most general to the most specific (or vice versa, though starting with the most detailed first might require more concentration on part of the reader). One can use these and any other methods of organization you can think of so long as it makes sense given the context.

    How you might organize your ideas or details would depend on what you’re trying to achieve in the first place, and some methods are more suited than others depending on the topic. Lengthier works might even require a mix of these techniques. For example, if I were to describe a city for a D&D campaign, I might describe its layout first, laying out the details as if I were walking through the city. Then, I might describe its government structure from the widest in scope to the narrowest. Is it part of a kingdom? How is the city itself governed? Are there any districts, if so, how are they governed?. I would then give an overview of its history—in chronological order, of course. Any other detail that might be of use (for the DM or the players) can then be listed in order of most prominent or well-known to the least.

    Now as a demonstration, I’ll attempt to outline this response:

    • Foreword and disclaimer
    • Basic overview of outlining
    • Examples
      • Describing a house
      • Describing a person
      • Describing a process
      • Describing an idea
    • Organizing detail
      • Based on space/location
      • Based on time/chronology
      • Based on generality/specificity
      • Combination of approaches and others
    • Demonstration


  • This might pale in comparison with all the other replies here, but one incident really made me uneasy.

    I was seated inside a train minding my own business. I was wearing a loose shirt and an even looser pair of walking shorts. The shorts were made of thin and glossy material. It wasn’t thin enough to expose my underwear but it readily shows any bumps or whatnot.

    The train wasn’t that full, and there were lots of empty seats. The train had longitudinal seating (two rows of seats facing each other, with some standing space in between. There’s also an area where the train can “bend”. This area has no seats of course. I was seated next to this “bendy area”.

    I remember having difficulty staying awake and was seated in an increasingly loose way. I caught a glimpse of a guy standing in front of me. He was leaning against the train walls and was on his phone.

    Now, the train isn’t the most quiet, but I distinctly heard an unmistakeable camera sound which jolted me awake. Selfie cameras on phones wasn’t yet a thing back then and the way his phone is oriented, I can see the phone’s camera lens pointed at me. The guy, noticing that I noticed the sound, quickly put the phone back in his pocket.

    I might be wrong, I hope I was wrong, but I thought a stranger took a photo of me just a meter or two away from me.

    That’s it. Kinda underwhelming, I suppose but I was kept wondering why that guy, if it’s indeed the case, took a picture of me.


  • Before, I use Active for my subscriptions, and Top Day or Top Week for the All feed. Currently, I use Scaled for my subscriptions and All feed unchanged (Top Day or Top Week). I just like how I can take a peek at All and looking at the day’s or week’s top posts while mostly keeping to my subscriptions.

    I sometimes look at Top 12 hours or Top 1 hour in my All feed, but rarely.







  • Yeah, that’s a good point, but the readmes that I’ve seen written by those who wrote the code themselves are not much better. Sure, they know what it’s all about, which is precisely why it oftentimes isn’t much help for a user.

    What’s needed is someone who’d read the initial readme (written by the guy who wrote the code itself) and ask questions about the parts that were “too straightforward” to be included, or weren’t explained clearly enough, or to bring down the general overview back to Earth.

    And if there’s yet another person who’d go over this second pass, and keep it from being too dumbed down, even better. Keep it to the level of the average user. That requires knowing the kind of person who’d likely use the program.





  • It takes a certain kind of a skill set and experience to be able to translate this “consumer view” into something that can be acted upon by a developer.

    Sure, the skill set can be developed, the knowledge (about software development, the available technologies, and having an idea of what is and isn’t feasible in the first place) can be built up, and the experience (communicating with developers) can be accrued, but that really stops a lot of people from even thinking of contributing.

    Perhaps a subset of the (open-source) community can help in developing these (skills, knowledge, experience) among interested people. Teach people how to look for issues, bugs, or come up with feature requests; teach them how to put these into a form that’s easily understood and appreciated by the developers, and finally, teach them how to communicate with developers without losing the “non-techie user POV” which makes their feedback valuable in the first place.

    IDK though, having read what I’ve just written, it seems to be quite a task.


  • Oh, yeah, I hear you! My go-to for those “I feel too lazy to cook something substantial” would be ramen because fried rice can actually be pretty hard work, lol!

    Also, thanks for the tip about fried eggs. We usually don’t add much to our fried eggs here, just a bit of salt and a bit of all-purpose seasoning if we’re feeling fancy. Otherwise, it’d be an omelette with onions and tomatoes and all that and it’s already become a dish of its own.


  • If any dangerous pathogens are kept out or killed, I guess more power to the you? However, I’m just thinking: “Why not make fried rice out of that?” Heck, you’d just need some oil and garlic and letting that day-old rice cool and dry out a bit.

    Fry the egg first, then using the same oil the egg is fried in, then once the garlic is almost golden brown, take it off the oil and add the rice. Let the rice heat up and then add the chili paste, the garlic, the pork fu and/or whatever else you might have on hand you fancy adding. Season to taste and cook to desired “doneness”. Some like it cooked to the point of the rice gaining that scorched and crunchy layer.

    And that’s just basing off your recipe. A lot of dinner left-overs can be added to next day’s fried rice, and it’s just basically a way of dealing with left-overs (and rice) and cooking a one-dish meal out of it…


  • Yep, poaching an egg (or a couple) in the ramen as it’s about to finish cooking is one of the ways I add eggs to instant ramen. Another is a technique similar to egg drop soup: stream pre-beaten eggs while stirring the ramen (also just about the ramen is done cooking).

    But I default to adding soft-boiled eggs. I cook the thoroughly washed eggs in the same water I’d cook the ramen on. I take the eggs off (put them into cold water if necessary, or I can just take them a bit early and let the residual heat take it the rest of the way), then cook the noodles. While waiting for the noodles to cook, I peel the eggs and then put them back into the noodles just before serving.