Home
Artists
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Register
Partychan Telegram ThePornDude
Home Artists Posts Import Register

Book Stuff | We need more quotes! About a few different things! (Patreon)

Published:
2023-05-08 20:36:21
Imported:
2023-05

Content

Hello Brains!

<Update as of 5/11/2023> 

Thank you all so much! We think we have what we need so for now the link to the form has been deactivated. If we find that we end up needing more, we shall let you know. <3 

</Update>

<Update as of 5/9/2023>

Update 1: A new question has been added! Feel free to re-submit a new form to answer the new question if you'd like! (You do not need to re-answer questions you've already done. <3)

Update 2: We weren't getting the answers we were needing for one of the questions, so we've removed questions we have enough quotes for, and updated one question so it's more clear for everyone! Feel free to re-submit if you would like :D

Update 3: We weren't super clear on what we were looking for in regards to our question regarding volunteering, sharing resources, etc, etc. We changed that! We hope! :D If you already answered that question but want to make sure it's in-line with what we're looking for, feel free to check out the form again, and feel free to re-submit!

</Update>

We have some areas where we could use more quotes about specific things, and since I'm not the only one handling these quotes (in fact, I'm the quote gatherer not the quote picker!) I figured there was a faster way for our back-end process to work.

So instead of commenting here in Patreon, please go to the following link and fill out the form there! The only information stored by this form is the information you type into the form. :) Email address is not required -- but your Patreon name is, just to make it easier to reach out if we do need to ask you for something!

If you have any questions please let me know in the comments to this post.

Click here to fill out the quotes form!

Thank you so much! The help you all are providing is tremendous and honestly, it's been so incredibly cool to see just how many different ways we all experience not just individual symptoms, but our strategies as well. :D

You all are fantastic!

All the Best,
Harley L.
Community manage

Comments

Suzanne Strickland

Which subjects need more quotes? Do we need to copy/paste our Patreon quote comments to the form? Thanks for the answers

Scott & Sora
>>108129273

The form has specific questions to answer. I didn't recognize them from previous questions, so I think these are all new. But there are several of them this time, so a form makes more sense, I guess.

How to ADHD
>>108129273

Honestly, the form is just to make the answers easily accessible to everyone on the back end. As before, I (Harley) was pulling them from here and copy/pasting them into a document due to the other individual working on quotes not having access to our Patreon. And I currently do not have time to do that without pulling a ten-hour day. 😅 As I'm also helping in other book-related areas. - Harley, Community Manager

Anonymous

When will you stop accepting responses? I wanna make a reminder so i dont forget

How to ADHD
>>108189925

The exact timeline is still fuzzy, but I can say for sure within the next 24 hours. Maybe the next 48. &lt;3

Anonymous
>>108190074

Okay, thanks!! I'll set the reminder for right after this appointment :)

Todd Holdsworth

Just a note for anyone doing this on a phone: I have to copy the questions into OneNote because I get busy and when I come back to it the page reloads and my responses are gone

Blake Chambers

SAD FACE! I just finished an answer to the question about working memory,,, I'll leave it here in case it's useful to someone: As a software engineer, my role frequently involves extensive testing of interdependent systems. The best practices of software development would say to decouple complex dependencies so you could have simpler and targeted integration tests. An unfair, overgeneralized take on the culture of the companies I've worked for so far is that quality, or as I like to call it, basic documentation and functional pipelines for building and testing our work, isn't worth the time if you could instead code something really fast that kind of works, but might definitely work on the next try, and fix it only as needed. This is why we depended heavily on a large simulator, which needed hundreds of settings to be configured, along with the latest versions of various applications from multiple teams. This simulation phase was a crucial step in our process, and I found ways to manage it. I bookmarked all the necessary pages to access the most recent application names and saved a template for the settings that changed less frequently. I also kept links to simulations run by my peers as examples for my own setup. Despite this being a "minor" part of my job, I think I wrote more notes for running these simulations than actual code. My colleagues often seemed perplexed when I asked them for the latest settings, not understanding why I couldn't remember the half dozen or so weekly changes. My solution was a mix of constant note-taking, creating snapshots of examples for future reference, and relentless questioning of my teammates. However, the most daunting challenge was the simulation run time, ranging from 2 to 6 hours. If a test failed midway and I wasn't actively monitoring it, I'd lose the chance to make adjustments and rerun it within the day. This constant vigilance ate up my working memory and executive function. My solution was to break down the task into smaller, more manageable phases, each with its own time frame. I crafted a 'cheat sheet' that tracked the simulation's progress at different time intervals. Then, I would set timers to go off when I needed to check on the run. Although I was finally freed from having to remember the entire process and where in the process I currently was, it still didn't make multitasking any more real. However, I now had windows to catch configuration issues and restart the sim. This freed my mental bandwidth, allowing me to work on other tasks rather than constantly overseeing the simulator. In essence, through exhaustive note-taking and reminders, the simulation run was actually manageable. And one teammate actually found it useful.