#and needed to write something to help process things

[butch-reidentified]

Pitching New Terminology: GLAP (Gamete-Linked Anatomy and Physiology)

A little while back, I remember seeing someone on here talk about 2nd wave feminist attempts to coin new terminology/alter existing terms as part of their feminism ("herstory" and "womyn" for example) + my wife and I have been talking a ton for a few months now about how language can feel so limiting, as counterintuitive as most people likely would find that. One of the things my wife brought up is that it bothers and bewilders her that "sex" can refer to biological categories, to the state of being male or female, but can also mean intercourse. She said this feels very male to her, and thinks that this word being used to mean both of these things (both of which are very charged concepts with heavy connotations - but only because of patriarchy) is not only unnecessary, but arguably harmful to the feminist cause as well.

Not only that, but sex (as in maleness/femaleness) is itself very much in contention these days - its existence itself is challenged in addition to its definition and the parameters of its categories. Even outside of gender identity ideology (GII) and the conversation surrounding transgender identities, there is a fair amount of inconsistency in what exactly people think makes a human being male or female, be it large or small gamete production, the presence of either a penis or a vagina, some sort of checklist-like combination of sex characteristics, karyotype, hormone dominance, the infamous pseudoscientific "brain sex," or something else.

I agree with Dr. Rashad Rehman's succinct statement that "sex is defined by gamete production," from his paper (which I've posted on several previous occasions and you can read at this link) refuting both GII and the catholic church regarding human sex biology & intersex conditions. As I've said countless times on this blog and he says in his paper, this manner of categorizing human beings as male or female does not require successful production of large or small gametes. Rather, it defines a human being's sex according to which of two overall developmental pathways their body follows; has your body (your anatomy and your physiology, as referenced in the GLAP acronym's A and P) developed around the "intention," so to speak, of producing large gametes or small gametes?

This is what led to the acronym GLAP (for "Gamete-Linked Anatomy and Physiology"), which I introduced in a recent reblog. She and I coined this term together to offer a more precise, better delineated alternative to "[biological] sex," and an alternative bearing zero denotative or connotative relationship to sexual intercourse.

By not only defining sex in relation to gametes, but placing the very word "gamete" at the literal forefront of the term itself, GLAP leaves little room for debate or misunderstanding when it comes to discussions of maleness and femaleness in human beings. The importance of this is well-stated in Dr. Rehman's paper, particularly in the following section containing two quotes from the writings of MIT philosophy professor Alex Byrne. The first of these two quotes references Brown-educated feminist scientist (and GNC lesbian!) Dr. Anne Fausto-Sterling, and the second cites Simone de Beauvoir's "The Second Sex."

[Please let me know if image description is needed; screen reader test worked on my end, but who knows?]

We believe this terminology has the potential to combat misinformation surrounding human biology as well as to open doors within the discourse pertaining to GII and transgender issues. We suspect - and hope - that removing the word "sex," thus removing the messiness that tends to come along with the word, could perhaps reduce tensions and reactivity in order to allow for conversations to be had that otherwise would rapidly escalate or be avoided entirely. Additionally, introducing a new term like this requires providing an explanation of its meaning and purpose, the process of which we believe will help facilitate such conversations. We also feel that the novelty and hint of silly-sounding-ness could support the goal of reducing the tension and emotional charge currently embedded in gender discourse.

[nenelonomh]

organization 101

organization is about how we gather stimuli in our environment to complete tasks quickly and more effectively. it's about arranging our surroundings, providing order, and structuring items and activities around us.

this topic can be applied in so many instances - including physical spaces, digital files, schedules, and mental clarity.

staying organized offers several benefits:

★ when you're organized, you waste less time searching for things or figuring out what to do next. this efficiency leads to increased productivity

★ clutter and chaos can contribute to stress. an organized environment promotes a sense of calm and control.

★ organization helps you allocate time effectively. you can prioritize tasks and allocate resources efficiently.

★ a clutter-free workspace (or living space) allows you to concentrate better on the task at hand.

★ organized spaces encourage healthier habits, such as regular exercise, balanced meals, and adequate rest.

but how can you stay organized?

★ start with one area of focus (e.g. closet, desk, documents, ...) and gradually expand. focusing on one area allows you to see tangible progress, and as you declutter or organize, you'll build momentum to tackle other spaces.

trying to organize everything at once can be overwhelming. by narrowing your focus, you can prevent feeling swamped. concentrating on a specific area also allows you to learn effective strategies,, which you can apply to other parts of your life!

★ keep a to-do list. you can use a planner or digital tools to track tasks - and prioritize and sort tasks by urgency. write things down promptly to avoid forgetting them.

by freeing your mind from trying to remember all of your tasks, this mental offloading allows you to focus on the present moment. you can also assign urgency and importance, ensuring you will tackle what matters most.

★ give everything a home. clutter happens when items lack designated spaces. organize your physical and digital spaces intentionally.

★ once organized, maintain order consistently by building habits and systems. regularly review and adjust your systems when needed.

maintaining daily habits can significantly contribute to staying organized.

digital files

personally, the biggest issue i have with organization is building (and maintaining) a good system for digital files. it is crucial for me to learn how to organize these well, however, as a digital creator.

here is the process:

★ create a folder structure,, and design a clear hierarchy of folders that reflect your workflow. organize files logically based on projects, departments, dates, or file types.

at the moment i sort my files as content home < links, content plan, instagram, pinterest, tumblr, youtube < scheduling, post ideas

however, sometimes i find myself with documents that don't fit any of these sections. my plan for the future is to reorganize this to be the most effective it can.

★ use descriptive file names,, and name files clearly and concisely. include relevant keywords to make searching easier

★ consider using tags to categorize files across multiple dimensions. tags enhance searchability and allow flexible organization.

this is something that i am looking to employ!

★ utilize cloud services like google drive or dropbox for easy access from anywhere.

i will forever be a notion girl,, even though it is not quite a cloud service, it allows me a similar experience.

★ make decluttering a routine. delete duplicate or unnecessary files.

★ pin essential folders to your sidebar for quick access.

physical decluttering

writing this, i was reminded of the (horrid) bedrotting trend, especially those videos where people would show their rooms with shit everywhere and mould growing on stuff. i'm aware that some people find it super hard to maintain organization or declutter - hoarding is a very real issue.

the benefits of staying organized were previously mentioned, but decluttering specifically has its own little set of positives. this includes reduced stress, improved focus, enhanced productivity, and more positive overall wellbeing.

here are some essential tips if you are struggling to get started:

choose a small area or category to begin decluttering. set a timer (15-30 minutes) and sort items in that area into 'keep', 'donate', 'trash', or 'unsure' piles.

you could also attempt a room-by-room approach, by tackling one room at a time. focus on completing each room fully before moving on to the next.

try to organize your belongings into categories (keep, donate, sell, discard) to make decisions easier.

remember - progress comes from consistent effort, and small steps lead to a clutter-free space.

further reading

i hope today's post was helpful!

as for further reading, check out these sites: ★ How to Declutter Your Home: 6 Best Room-by-Room Methods (thespruce.com) ★ First Steps to Decluttering - Understanding the Clutter - Being Minimalist ★ Productivity, Organization & Personal-Development | 101 Planners ★ Executive Functioning Skills 101: Organization | Life Skills Advocate ★ How to Be Organized - 10+ Habits - Organized 31 ★ How to Be More Organized & Productive | 10 Habits for Life Organization (youtube.com) ★ How to Be More Organized (verywellmind.com) ★ How to Organize Your Digital Files | Reviews by Wirecutter (nytimes.com) ★ Master How to Organize Digital File Management (riverfy.com)

❤️ nene

image source: pinterest

[nothingbutnowhere]

Part 2 soft!Simon x hypervigilant!reader

Part 1

You don't absolutely need to read the last part to understand this, but it's in the same universe.

Notes: domestic as fuck, Simon snores, reader is referred to as 'girl' by Simon, referenced off screen sex, teasing and banter

...

The after-sex-cuddles-but-before-bed ritual is set in stone. You both get up, Simon folds up the sex blanket (second best purchase of your life) and cleans your vibrator (the best purchase of your life), while you prep a warm washcloth. He helps you wipe down, he calls you 'messy girl' each time like he didn't contribute half of it. You still blush.

Brushing your teeth together, it often hits you how domestic this all is. Some nights it's painful and Simon holds you until you stop shaking, other nights you're smiling so hard it's difficult to brush. Tonight is somewhere in the middle. Melancholic. Quiet. He shoos you into the bedroom after you're done, turning off the light and closing the door on the way out.

Simon grabs you as soon as you sit on the bed and pulls you down into him, strong arms surrounding you, face nuzzling into your neck like a cat. But you see through the trick.

"Put your CPAP on before you fall asleep."

"Don' wanna," he says sleepily, "Can't do this w'the bloody thing on."

It's true, spooning with the CPAP sucks (unless he's the little spoon) but that's not what the current objective is.

"Simon," you warn.

You try to wriggle out of his arms to no avail.

"Simon Riley put it on right now or so help me god you'll be sleeping on the couch for the next week," your mock 'upset' tone is always only half serious, made even less so by the punctuating yawn.

For both your sake's you need the 'bloody thing'. For one, you'll sleep like shit if he's snoring in your ear and for two he's always in a much better state when sleeping with the CPAP. He's told you he sleeps like shit when he's gone and you tut that it's because he doesn't have access to it. He said it was 'cause he didn't have access to something else and that was the end of that conversation (he went to bend you over the kitchen counter but you slipped away giggling, only to end up tossed over his shoulder on the way to the bedroom).

"Simon."

When he doesn't move you jam your elbow back into him.

He doesn't so much as grunt at the attack, only grumbles and flips over, sitting up to flick on the lamp and mess with the machine.

You watch him as he does, muscular back on display and you resist the urge to run your hand over, lest you disrupt the process. 

He may tease you gently about your 'princess alarm clock' that wakes you up with light and birdsong, but you get him right back with references to his 'CPAP deluxe'. It's got the warm air humidifier for his 'delicate nose', all the bells and whistles.

He finishes and turns the lamp off, leaving the faint light of the street lamp to illuminate the room and him as he turns back around.

"There's my scuba diver," you giggle, tapping the mask softly.

He sighs, knowing he can't make a convincing comeback with the mask on- you'll only laugh at his attempts- and lays down on his back. You immediately snuggle up against his side, hugging his arm, leg thrown over his. His hand cradles your face for a moment, thumb sliding over your lips as a good night kiss before laying his hand over yours on his chest. 

It's peaceful like this. Before you needed silence to sleep but you've gotten used to the CPAP. Mostly because it means Simon's home. And now when he's gone you have to put on white noise to sleep. Nothing your princess alarm clock can't handle. There's been lots of big and small changes since Simon wedged in to your life with his puns and banter and menacing figure but it's been more than worth it.

"Love you," Simon mumbles through the mask.

"Love you too."

...

Part 1

A/N: I made this account to write smut and here I am with the softest slice of life blurb. Oh well. Maybe I'll write the bit after the 'access' comment, there's lots of fun places that could go.

[its-all-stardust]

Hey, so first of all, I love your work, it's absoluteley amazing!!!

I saw that your requests are open, so I thought that I would ask for a Matt Murdock x reader oneshot? You know, just something cute and fluffy?

Maybe I'm gonna sound a bit stereotypical but how about a reader that owns a bakery and wants to try out a new recipe. Matt tries to sneak a taste from time to time while "helping out" (honestly, he's just teasing and making reader's job probably harder [affectionaly]). Just domestic fluff? Maybe please?

You don't have to if you don't want to, but I thought I'd give it a try :)

Thank you!! I'm glad you like my writing!! 🫂

I'm worried with this one that I tweaked things just enough that it's not exactly what you wanted anon, but I did my best and wrote what inspiration gave me!! I'll be honest, it could be fluffier, but I'm also not offended by my own writing so that's something lol I hope you like it!! ❤️❤️

Check out this post for request guidelines

Masterlist

Matt Murock/GN!Reader

Word Count: 964

Was turning your residential apartment into a glorified bakery after you moved in with your boyfriend legal? According to Matt, a very good lawyer, it wasn’t technically illegal, so you did it anyway and prayed your landlord never found out.

It wasn’t really a bakery, not in the traditional sense. You didn’t try making it into a storefront, nor did you want it to be one. You did, however, take specialty orders through your website. You mainly baked for small events or private parties. You weren’t touching a wedding with a ten-foot pole unless you made the cake or just one of the cookies for the snack table.

It wasn’t enough to pay the bills on its own—you still had a full-time job—but you enjoyed it, and the small amount of extra income it generated was nice.

Matt enjoyed it, too. So much so that you often joked he had ulterior motives for dating you.

But even though baking was a passion, it still came with challenges.

You let out a frustrated sigh and leaned against your elbows, bent over the counter, and buried your face in your hands. 

This is the worst part about baking, you thought.

“Do you need help?” Matt asked, hand suddenly on your shoulder. You jumped, letting out a small gasp. “Sorry. I tried calling a couple of times.”

“It’s fine,” you sighed, turning to wrap your arms around his middle, leaning into him, and pressing your face against his neck. “I just hate this.”

Matt huffed a laugh. “It can’t be so bad. You say that about every new thing you try.”

“But I really mean it this time!” you whined, though you actually didn’t.

You strived for perfection, but new recipes were always daunting. Either the first few batches didn’t meet your standards, or the very first one did, but the subsequent batches often failed. You thought once or twice about not adding anything new to your menu, but you needed to keep a refreshed list, or else you risked losing repeat customers—the ones who made this business possible for you in the first place.

“We can do it together,” Matt offered, lips brushing against the top of your head. “Will that make it better?”

You considered it for a moment. Matt’s taste was impeccable. You often used him—and Foggy and Karen—as guinea pigs, and he was always able to offer you the best advice. In another life, he would have been a fantastic chef. You’ve never baked anything with him before, only handed him the finished product.

If he helped you now, as you were putting everything together, it could make the whole try, try again process you had going significantly shorter, if not bypassed completely.

“Yes, actually. I think it will,” you answered, lifting your head up. 

The only problem: Matt was a complete and utter nuisance.

He wouldn’t do what you told him, at times completely forgoing your instructions—the one you found in an old cookbook that wasn’t like anything you found online—and adding either the incorrect amount of something or adding something that wasn’t even on the list of ingredients.

No matter how many times you told him baking was an exact science and the time for experimentation was after you followed the recipe to a T and tasted the finished product, he refused to listen. You thought he did, at first, but then you caught him tossing in almond extract behind your back, and things only went downhill from there.

“Would you please stop sticking your fingers in the bowl?” you practically begged after you caught him helping himself to the cookie batter for the fourth time.

“How else am I supposed to taste it?” he asked with a playful smirk. He seemed to enjoy the fact he was making you want to pull your hair out.

“With the spoon I specifically set out for that purpose!” You picked it up and thrust it at him. He ignored it and stuck his finger in his mouth.

“But I’m blind. How am I supposed to know where it is?” 

You raised an eyebrow, not fooled. “The same way you find the bowl even after I move it.”

Matt shrugged. “Fair point. But if I used the spoon, I couldn’t do this.” He stuck his finger in the bowl again.

“Matthew, I swear to—”

He stuck his finger in your mouth, not far but enough for the batter to touch your tongue, before he pulled away.

“—God,” you couldn’t help but finish as the first notes of the batter processed. Brow furrowed, you focused on the taste, brushing your tongue against the roof of your mouth, trying to make it last while you sorted out the different flavors. It was…

“That’s amazing,” you said, stunned. “What did you put in there?” You pulled the bowl toward you, forgetting the spoon in your hand as you dipped in a finger from the other. It wasn’t what you were trying to make at all, and you needed another sample.

“I tried telling you it just needed a few extra ingredients.” Before you could stick your finger in your mouth, Matt took your hand, wrapping his lips around your batter-covered finger. His tongue lapped gently against the pad, almost teasing. “Now it’s perfect,” he said when he pulled away.

“I think I need you in the kitchen more often,” you said, wheels already turning in your mind.

Matt beamed at you and tried leaning in for a kiss. You, however, didn’t notice and stepped away to find your phone, leaving him confused.

You opened your notes app and said, “Quick, tell me what you did before you forget.”

Matt could only shake his head in amusement before he dutifully listed everything he had snuck into the batter.

[neverevan]

Inspiration Saturday ☔️

Phew, I haven't done one of these in months! But hoping to actually get inspired and also to prove that I am working on that last chapter and because I think I actually finally know how to get through that last bump, here's a little tease from the last chapter of the mudslide fic:

The hours leading up to that felt heavy. Eddie could feel Buck’s worried looks on the back of his neck all throughout, sticking there like he accidentally rolled into flypaper. Eddie couldn’t blame Buck for it much, but by god, did it make him feel like shit; like some fragile porcelain doll that couldn’t handle the pressure without snapping.

And he could handle it, damnit. He’s done this before and he’ll do it again.

After coming back from his first tour in Afghanistan, they sent out dates and locations for all upcoming funerals and Eddie had spent five days driving around in his old truck, wearing his cheap suit, sweating yellow stains into his white shirt and trying to get to all the places that he could afford the gas money to.

That was the one time of Eddie being selfish and leaving Shannon to deal with Christopher alone, that she never rowed up for him and he was still thankful for that to this day.

Those funerals were different, however. Most of those soldiers he’s never met or only so briefly that he probably wouldn’t have recognized them on the street — after that, he made a great effort to commit their faces into his memory, by staring at their framed smiles at ceremonies day in and day out.

This time, he was attending the service for someone who, inadvertently so, but saved his life and Bosko’s. Ramirez made the ultimate sacrifice and the least Eddie could do was to honor his memory.

✨Tagged by and tagging the wonderful @sunshinediaz @spagheddiediaz @jeeyuns @exhuastedpigeon @honestlydarkprincess @excuseme-greentea @disasterbuckdiaz @daffi-990 @diazsdimples @sunflowerdiaiz @watchyourbuck

[orcelito]

I think I cried harder today over my dad's jackets than I did at his deathbed. That was a miserable time of course, a memory that will likely be seared into my brain until I die, but I cried... I think a normal amount, all things considered. More than I ever usually do of course, but I typically don't cry At All. All this free crying is certainly surreal.

The jackets, though. I was put in charge of doing his laundry, because we don't want to pack up dirty clothes. I was expecting it to be unpleasant bc my dad's dirty clothes - gross. But really, it was much more unpleasant in that... those were his. It felt wrong to touch them. Felt wrong to treat his jackets as gross. Because they were just his jackets. They weren't even in the hamper. And then I was remembering him wearing them, and then I was crying. Again. And again. Weeping over these damn jackets.

Then I found a shirt on his bed that still smelled like him. It smelled like a Hug From Dad. And that set me off crying even harder.

In total, I think I cried like 6 times within 40 minutes. It took me that long to finish sorting the damn clothes bc I just. Was a wreck. Like, what are you supposed to do when you're living life like normal, vaguely hopeful bc you're taking steps to secure your own happiness, and then 4 days later you're sorting your dad's laundry because he fucking died. Suddenly. Without a goodbye.

And you have to worry about his lack of a will (even under an ideal situation, only 2 heirs and no conflicts between us, probate's a fucking Bitch), and arranging the funeral, and prepping his obituary, and picking out pictures, and writing a speech bc you want to talk at his funeral, of Course you want to talk at his funeral, but even just thinking about anecdotes you could share has you crying yet again.

I've cried more times in the past 3 days than likely the entirety of last YEAR. And that's WITH my cat, and uncle, and family friend dying. Those all hurt, my uncle most of all, & I was real fucked up over it. But this? This was my Dad. Likely the person I'd have named 2nd closest to me in my life, second only to my sister. He wasn't perfect, but he did so much for me throughout my entire life. All he wanted was to raise us to be happy and independent. And he accomplished it, we're getting by without him, but we still wanted several more decades with him. He was only 57. We should've gotten several more decades with him.

But here we are now. Playing investigators to his life, digging into all his shit, trying to find documents and take inventory of all his things, and learning Many things about him in the process. In his lockbox of sensitive documents, like his SSN and birth certificate and all that stuff, we found an old letter. About a decade old now, written in my hand. Right at the very top, we found that he'd kept the letter I wrote to him telling him frankly about my struggles and the things I wanted him to do better. He kept it. He tried to take it to heart. He looked at it again, sometime more recently than all the rest of the documents. That was on top.

His love for us is evident everywhere. The pictures he has hanging up all over the place, majority of them with us in them. The old fathers day cards placed on display in his bedroom bookshelf. The gifts we gave him, even stupid little knick knacks, placed around his apartment with pride. I wish we'd taken more videos of him. I don't want to forget the sound of his voice. I don't want to forget his smell either, the smell of a Hug From Dad, but I still tossed that shirt into the wash even though it felt like saying yet another goodbye.

It's the suddenness that hurts the most, I think. We were planning on having him help me finally get my license this year. My final words to him, the last thing he would've seen from me, were messages asking up on whether he'd called his car insurance company to make sure there wouldn't be problems. I should've called him more. I don't know if I'm going to learn from this.

I cut my 2 weeks off early to have time to grieve and to work on things for the funeral and settling the estate. The last thing I'd wanna do right now is selling fucking bubble tea in a job I already decided to leave. So here I am without a job, though with potentially two life insurance policy payouts to come. Inheriting half his 401k. Inheriting couches, knickknacks, keepsakes, paintings, art pieces, maybe even his guitar and other furniture if we can figure out what to do about space (I don't have room for this furniture, I don't know if I even have room for the couches, but God do I want to keep so much of this furniture). It has me even considering keeping one of his guns, just one. A tiny little revolver, it sits so comfortably in my hand. I don't even want to use it for anything. I just want to have it, keep it stored in a drawer with its ammo kept separate. I don't like guns, but this is a part of him. He loved collecting guns. He was about as responsible with them as someone can be, keeping them locked in a lockbox and impressing upon his children the importance of gun safety (I've known the basic gun safety rules ever since I was a little kid. Of course, of course, of course.) It reminds me of him. It's horrifically easy to have a gun in Indiana. I apparently don't even need a permit to carry anymore. (I have no intention to ever carry this in public.)

It's all a cycle. Business, grief, thoughts about my future. Round and round, like the most nauseating carousel in existence. I don't know how I'm still so functional. My skills with compartmentalization have been my lifesaver.

And im just thinking about the story my dad's best friend shared today. About a friend of theirs who lost her father. She reached out after hearing about my dad to share his words with her: "it's okay to grieve, but don't make his death your life".

He explicitly referenced himself in this, saying if he were to die suddenly that he wouldn't want us to define ourselves by it. Grief is expected, but he wants us to be able to move on. He's always wanted us to establish ourselves and make ourselves happy. He wouldn't want to be a weight holding us back from that.

So every time I start to feel guilty for thinking about having nicer furniture or using his life insurance payout to fund the rest of my college, I remind myself of that. Thinking about the material isn't a bad thing. I'm only human. And in the end, he'd Want me to be thinking about it. He never intended to die, certainly not without warning like this, so he would've only encouraged me being pragmatic about it all.

He only ever wanted us to be happy. So I need to do what I can to live up to that.

I love him. I miss him already.

[oscill4te]

It is genuinely so hard to concentrate on a recipe when it has a million of ads and makes you lose your place where you're reading -_-

[babylon5]

some people on here are so fucking vile to beginning writers especially younger ones and i hate it. contrary to popular opinion no one exits the womb with a perfect understanding of creative writing (actually the concept of this is highly subjective anyway but!!) or grammatical structures. it takes Time to build these things!!!! i love being a hater but when you're hating on, like, traumatized teenagers writing about icarus or whatever because they don't know how else to put what they're going through into words, that's just being an asshole i think lol

[dallonwrites]

lately my only goal w my writing sessions is just to do whatever i need to feel good and set myself up for success w the next writing session and it feels kind of like basic advice but i seriously never gave specific focus to that and it's kinda life changing lol

[quietmarie]

What is Async Anyway?

Explaining async/await and general concurrency concepts in programming languages.

A lot of modern languages have async/await syntax built directly into them, and the construct can be extremely useful. Examples of languages that include these concepts are JavaScript, C#, Python, and Swift, and even modern relatively low-level languages like Rust have this syntax. Even though it's usually thought of as a more advanced feature, I think it is really not that hard to use once you get the hang of it, and it is super useful and rewarding when you really understand it.

This is going to be a bit of a long and pretty technical post, but I hope it can give you some confidence to know what async/await really does when you use it, and maybe it can help you use it more effectively. Keep in mind that I will not be able to go over everything in super deep detail, and that I am going to simplify stuff, but it should give you an idea how these systems work.

I am a little curious about eventually following this up with a post looking at how these systems compare under the hood in different programming languages, so let me know if you'd be interested in that.

Big post under the cut.

Parallelism and Concurrency

Computers today can do many things at the same time. And I mean that literally: in one instant, a modern CPU can be working on multiple instructions. That's because a single CPU has multiple cores that can all execute code (mostly) independent from each other. This is called parallelism, and the way we as programmers interact with that is through threads. Most programming languages, especially "lower level" ones, have a way for programmers to create a thread that will run some part of your code. Creating a thread is telling the computer that it can, and should, run the code in your threads in parallel (although various systems such as the OS still have discretion over when and if that actually happens).

Parallelism is not quite concurrency tho. Where parallelism is about your computer literally doing multiple things at once, concurrency is about your computer doing multiple things, but not at once. With concurrency, you kind of pretend you're doing a parallelism. But in reality, stuff doesn't happen at the same time. Instead, your system (runtime) does some work on task A a bit, then on task B, then maybe again on task A, etc., but doesn't work on the two at the same time. So, in a concurrent system it might look like task A and B are progressing simultaneously from the outside, but work actually only happens in sequence.

Let's Talk About I/O

I/O stands for input/output and describes data in your program that comes from elsewhere, or that gets sent elsewhere. So for example, user input is I/O. And similarly, a web request can be I/O, whether you send it or receive it. So let's use that as an example: you send a web request to some API to fetch you the cutest bunny images and facts:

But the service is taking its sweet time to respond.

Fact: Loading bunny fact…

With how we did it here, we halt execution of the entire thread until the response comes in (at least in most languages, more on that later). In this case, we call get a blocking method because it, well, blocks the thread without actively doing useful work.

What if we could instead use the thread for other tasks instead of just sitting there, twiddling our thumbs and waiting on the server? This smells of concurrency…

Callbacks

Callbacks are a way for programmers to avoid that period of thumb twiddling. The new getWithCallback function now returns immediately, but it doesn't return a value. Instead, we have to register the code we want to run once the server responds with the function:

The function we pass to getWithCallback is called the callback, and it gets called by the client* only once the response arrives. Oh look, here it is:

Fact: A rabbit's life span is about 8 years, though sterilized rabbits (those who are spayed/neutered) can live as long as 10-12 years.

*"The client calls it" is a big simplification, there might be a lot more stuff happening here. But the important bit is that the client magically does not need to block to wait for the response.

Promises and Futures

What JavaScript calls Promises and what a lot of the other languages call Futures is essentially sugar sprinkled on callbacks - it makes our callback code a little nicer. Callbacks can commonly create a concept called "callback hell", where you have to call a function that takes a callback inside the function that takes a callback inside the function that takes a callback…

(Code modified from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises)

To avoid this, functions now can return a Promise instead of taking a callback. Promises represent the promise that, while a concrete value might not exist right now, it will in the future. Once the value exists, we say the Promise resolves. The code above with Promises would then look like this:

It still doesn't look perfect, and there are things you can do to make it look a little nicer, but it's so much less nested. The callback in the then function will be called once the value is ready, and the callback itself can also return a Promise. The then function then returns a Promise which will get resolved once the future from the callback is resolved. Many other languages have a concept similar to JavaScript's Promise, and it's often called something like Future or Task (because it would be too easy to have consistent naming across languages).

Now keep in mind neither of those solutions above are really "concurrency" in the definition we used above. This is because the thread we call, for example, getWithCallback on still completely belongs to us. We could keep using it, and we would not get interrupted to execute the callback. Depending on the language and runtime, the callback might get executed on a different thread, or the runtime might have to wait until we are completely done with what we were doing to then use our thread to call it. The same thing goes for the callbacks in the then method of promises.

Async/Await

And async/await is just some sugar and magic fairy dust on top of Promises (or Futures or whatever). It makes our code look like it should be blocking, but in reality it isn't. Here's what our bunny image code looks like with async/await:

So here, a couple things happen. First, the Promise is created and the web request is initiated. Then, the Promise is awaited. For that, (if the Promise is not resolved at this point already,) the task first yields, meaning it tells the runtime that it is not doing any useful work at the moment, and that the thread it ran on can be used for other tasks. The runtime then makes a note of where to continue execution when that Promise resolves, and looks around for other tasks that currently need executing to put them on that thread. After a while passes, the Promise resolves, and once the runtime has some resources available for us (maybe because another task just yielded), execution on our original task is continued with the API response.

Fact: A rabbit's teeth never stop growing! Many people believe they need to chew to keep their teeth short. While they do enjoy chewing, it's the normal wear from where their top and bottom teeth meet that keeps a rabbit's teeth short.

This is more in line with the concurrency we sought out above. We can interleave other computations while our task is still running, but during times where it is not doing any useful work. (Still, because you may have multiple threads your tasks can run on and move between, it might not always be 100% technically accurate to call this system concurrent.) This is also why it is important to not block for long in async contexts: if you're hogging the thread for too long, you're stopping other tasks from progressing and throwing a lot of the benefits you gained from doing it concurrently in the bin. Most async runtimes will give you some option to run expensive or blocking code elsewhere, so that you can keep the benefits you gain from async.

So that's the explanation what async/await does, and the broad strokes of how it works. If you have any more questions regarding the topic, feel free to ask! I think it'll be fun to occasionally write a longer post on interesting things I've learned, so if you have topic suggestions, don't be afraid to tell me!

Further links and sources

Don't Block The Event Loop! - Why you should avoid blocking in Node.js, and what pitfalls to look out for.

I got the bnuuy images and facts from the animality API. The licenses on the images are not super clear, but I'll assume it's okay for me to use them here with credit because it's an open API.

I lifted the definitions and some of the explanation for parallelism and concurrency from Steve Klabnik's talk on Rust's Journey to Async/Await. The talk is more technical and very focused on Rust, but it's a great talk.

I referenced the mdn web docs at various points, they're a great resource.

I created the code screenshots using the carbon app.

[stormlit]

lads i found d.ark e.yes transcripts i can finally actually remember what happens in molly's canon (and then choose to disregard most of it)

[eudico-my-beloved]

I fucking hate my culinary class table group soooo bad i should be allowed to hit them with carrots i think

[reimenaashelyee]

Campaign to make The God of Arepo an award winning work and win a literal brick as a trophy for the authors and for Tumblr community as a whole (SUCCEEDED!!!! Update below)

As the artist for one of The God of Arepo comics, my version is up for consideration for the Ignatz Awards for Outstanding Online Comic.

For those of you who don't know the Ignatz is one of the highest industry awards that "recognize outstanding achievements in comics and cartooning by small press creators or creator-owned projects published by larger publishers".

The thing is, winning the award means winning an actual literal brick. Because the mascot is a brick-throwing mouse. So they have to make a bit where the trophy is a brick. Like. Look.

For a long time I thought it was just plain bricks they were handing out, but my friend who won a couple of bricks two years ago had theirs stamped (I saw the bricks in person at their house). So now I am obsessed with the idea of The God of Arepo winning an Ignatz trophy. It will have the honours stamped. On a freaking brick. That's the most Tumblr level meme trophy this comic/story could win (which is also a legit high honour industry award on its own btw don't get me wrong). But wilder than that, the brick allows me to do something. It allows me to smash that break into 5 pieces and ship one of each to the authors plus myself. Writing Prompts, sadoeuphemist, ciiriianan, stu-pot and me will get a piece of clay in recognition for our work with the farmer who built a temple out of stone. The full circle moment.

Imagine the value of this win to the lore of this Tumblr sacred text/folklore. This brick will be smashed and given to the creators, but as a collective folklore, it's also dedicated to all of us on this hellsite too. AWARD WINNING. If The God of Arepo wins I will document the entire process of smashing that brick here.

But we have to make this happen. We need to gather our collective energy and make this campaign work. Please help make The God of Arepo an award-winning story and vote for it in the Outstanding Online Comic category (link). You will need to request a ballot, then submit your vote. I recommend checking out the other nominated comics too. The Ignatz really shortlists good stuff. The voting closes September 8 2023 . LET'S GET THE GOD OF AREPO A BRICK FOR HIS TEMPLE!! LET'S GO!!!! REBLOGS HELP TOO!!

[david-watts]

I will not fall into the trap of rewriting everything because my writing skills have improved since starting the work

[sniffanimal]

tbh the most valuable thing I'm learning as an adult is everything takes a whole lot of time. things cooking, stuff growing, people returning calls, habits forming, medications working, healing, aging, learning, all of it takes time, and lots of it. slowing yourself down and practicing patience is the one thing that helps you make peace with this. and learning that patience will take time

[byoldervine]

How To (Realistically) Make A Habit Of Writing

To clarify: Works with my autism. WORKS WITH MY AUTISM!!! I’ve been meeting my goals since I made them my New Year’s resolution! Anyway I’m so sick of all those ‘how to’ guides that don’t actually tell you what the process is they’re just like ‘just do it, but don’t burn yourself out, do what’s best for you!’ because you’re not telling me what I’m not supposed to be burning myself out over but okay, so I made my own. Hope this helps

1. Choose your fighter metric. What works better for you as a measurement of your progress; time spent writing or your word count? Personally I get very motivated and encouraged by seeing my word count go up and making a note of where it should be when I’m done, so I measure by that. At the same time, a lot of people are also very discouraged by their word count and it can negatively impact their motivation to write, and in that case you may be better off working from how much time you spend writing rather than where the word count is

2. Choose your starter Pokémon time frame. How often can you write before it starts to feel like a chore or a burden rather than something fun you look forward to? Many people believe that they have to write daily, but for some people this can do more harm than good. Maybe every two or three days? Weekly? Figure out what fits your schedule and go with it

3. Choose your funny third joke goal. Now that you’ve got your chosen time frame to complete your goal in, what’s a reasonable goal to aim to complete within that time frame based on the metric you chose? If your metric is your word count, how much can you reasonably and consistently write within your chosen time frame? If your metric is time spent writing, how much time can you reasonably and consistently spend writing within that time? Maybe 1000 words per week works, or maybe 10 minutes per day? The goal here is to find something that works for you and your own schedule without burning you out

4. Trial and error. Experiment with your new target and adapt it accordingly. Most people can’t consistently write 1667 words per day like you do in NaNoWriMo, so we want to avoid that and aim somewhere more reasonable. If you feel like it’s too much to do in such a short time frame, either give yourself less to do or more time to do it in. If you find yourself begrudgingly writing so often that it constantly feels more like a chore than something fun, maybe consider adapting things. And if you think that you gave yourself too much wiggle room and you could do more than this consistently, give yourself more of a challenge. Everything needs to suit you and your pace and needs

5. Run your own race. Don’t feel like you’re not accomplishing enough in comparison to others or not working fast enough to satisfy some arbitrary feeling of doubt. Everybody works at their own pace and slower work doesn’t mean worse work. You could be on one word per day and you’ll still see consistent results, which is still one word per day more than you could originally count on. All progress is progress, regardless of its speed