Oh! That's probably enough for one day's work (kahit na may konting overtime o mejo heavy workload)! Pwede na palang pang-remote work ito! Of course, it'd depend on what exactly you're doing, but a work day doesn't impose a huge demand on a computer all the time.
So pwedeng na ata talaga syang pang-work computer!
That looks like a sweet portable PC set-up. Obviously you can't use it on the go as laptops would allow you to, but if you've got the space, you can set it up rather quickly.
Just one question though, how long do you think it'd run when on powerbank alone (assuming your average usage)?
First OS: Windows 3.1 running on top of MS-DOS 6.2
First Linux distro: Ubuntu (forgot the version, but it was circa 2018).
If I'd count an OS/Linux distro that I've used even if not in a machine I own, it'd be Linux Mint of circa 2006.
The alien impersonator was me all along! HAHAHA!!!
I mean, seriously, I am not a native English speaker, but even with my weird English accent, it only became weirder if I try to speak fast while keeping the emphasis on that 't' at the end of "hot". My native accent also probably lends to that glottal stop taking over the 't' and merging it with the upcoming 'p' sound. It also helps that the two sounds (glottal stop and the bilabial 'p') are on opposite sides of my mouth, so I can quickly sound them in succession. The end result sounded to me like an exaggerated "posh British" rendition, as if the alien watched way too much BBC before invading Earth.
It just sounded way weirder than I otherwise would be. I can't really describe it.
NO
Neither do I self-identify as a tankie, I don't think anyone who'd identify themselves as tankies would think of me as one.
I didn't get it until I started trying to say "hot potato" in the middle of a sentence, like "Look out! Hot potato incoming!"
The 't' in "hot" became more and more like a glottal stop as my tongue started to touch the gums of my top front teeth less and less.
This isn't about content, but upcycling is a thing. You can have somewhat fashionable and stylish products made from what would otherwise be waste.
Nope, you're not alone. I sometimes write a lengthy reply, read it, reread it, and before I get sucked into that overthinking loop, press "post" and go do something else.
I then find myself returning to my reply and re-reading it, often catching mistakes in spelling, grammar, or worse, in how I stated or presented my idea. That's why a lot of my replies end up being edited after the fact, with a note saying why I felt I had to edit my response.
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:
Tagalog, my native language, has one that I've always wondered about: ‘umay.’ I would translate it as “too delicious, it's almost sickening.”
Imagine a cake that's too delicious, overwhelms your senses with sweetness, tartness, bitterness and all the good things that in moderation, would have made for a perfectly delicious cake. For example, “Masarap naman yung cake ni Maria, kaso nakaka-umay” (“Maria's cake is delicious, really, but it's a bit too much for me”). I guess one can put it as ‘too much,’ or ‘overwhelming,’ but there's this additional element of “it's actually kinda good, you know, but it went a bit too far.”
Now, I've been wondering if it's related to the Japanese 美味い (うまい), and the wiktionary entry I linked earlier has it as a possible origin. I find it kinda (morbidly) funny wondering if it got its present meaning during the second world war, when the Japanese invaded the Philippines. I'd imagine Filipinos would just keep saying "it's delicious, it's delicious," just to placate the Japanese, even if they're already too sick and tired of it.
A source close to the Pope told CNN that the phrase could also be understood as there is a “gay climate” in the seminaries.
I wonder why.... Surely it isn't because a seminary is a good place for a confused, self-hating homosexual to be in, right? Surely it isn't because being gay was seen as so anathema in Catholic-dominant societies that the seminary seems to be a sanctuary, right?
I agree about being able to grasp the gist of the message with some basic Japanese, but IDK about being able to actually read the message.
There are some parts of the message that I don't think is included in basic Japanese lessons:
If I were to translate the message with my meager self-taught Japanese, I'd probably render it as something like
Though I don't think that fully captures the nuance of the message itself.