#And I am like soooooooo happy i can't contain myself

[ladybingley]

hehehe

[jessythebunny]

💐 Welcome to my fandoms house 💐

Finaly you made it here and i'm so happy because you decided to follow me and i hope you enjoy your stay🐰✨

Everybody is welcome here except Homophobes, racists, Pedophiles, Proshippers, Gacha heaters, and all the nasty people in general

So in this blog i make a lot of things here like memes, arts,edits, ect, sometimes they look good, sometimes they look cringe🙂🙂

Also i'm in love with James. He is the one who will be more present in this blog, sorry not sorry!!

And also these things here bellow👇🏻👇🏻:

I can do:

Tweening/animation

Drawing arts(even with bases or without them)

SFW (make characters kissing,marking echothers, moaning...)

Drawing simple backgrounds

Art requests

Art commissions

Things i can't do:

Gacha heat

Gacha cringe

Drawing diffecult backgrounds(like forests/cities/beaches, i really need Pinterest so bad😭)

Drawing animals(don't worry I am learning now)

Animate eyes

NSFW (18+)

Letting my oc's naked

🚫 But this blog is also contains swears, yeah a very ✨MOROCCAN✨ swearing, yep i like swearing a lot (But not to this degree), so if you have nothing nice to say here just leave my blog or block me IDFC 🚫

🎧°•My bio and information•°🖤:

🌺Name: Jessy the bunny or Jess in short🎧

🎧real name: N/A🌺

🎧age: 17 yo🌺

🎧birthday: December 1st🌺

🎧nationality: Moroccan🇲🇦🌺

🎧Zodiac: Sagittarius♐🌺

🎧Pronons:She/her/they/them🌺

🎧Gender: demi-girl🌺

🎧MBTI: INTP🌺

🎧sex: asexual💜🤍🩶🖤🌺

🎧hobbies: drawing/cooking/reading books and manhwas(especially the yaoi/yuri ones👀💦)/doing Gacha videos and art/writing stories🌺

🎧favorite shows: Thomas and friends, happy tree friends, dragon ball, smurfs, south park, lazy town,Hazbin hotel...🌺

🎧fears: dark, insects, social phobia, bullying (yeah i'm weak),being ignored🌺

🎧likes: Chocalate, cookies, sleeping, Science and Biology, English, watching videos or makIng them, anything sweet🌺

🎧dislikes: butter(i'm allergic),Maths and physics, Injustice and insult, school(yeah i hate school soooooooo much because of those fucking classmates), Sports, thomas and friends AEG,making friends irl because they are treacherous,spicy food, not getting enough attention🌺

🎧features: Nervous, introverted, depressed, funny, shy, autistic, ADHD, Have a short tempere🌺

🎧I'm a young artist, plz don't judge me!!!🌺

🎧my DMs are always open, but mostly for commissions🌺

🎧I'm also calling someone who's older than me by mr or miss as a respect for them🌺

✏️°•Extra Information and rules•°✏️:

💚I'm a little bad at English, so you may find some spelling and grammatical errors, so I sometimes use a translator

🖤Don't ask me hateful or disgusting questions, otherwise I will block you

💚I swear a lot, but it's not because I'm rude or something, it's because I'm nervous and I don't control myself, but that doesn't mean I'm mad or upset with you, so don't get me wrong

🖤I don't interact with many people, including: kids (under 13), NSFW bloggers, Zionists, Jews, proshippers, pedos, gacha heaters...

💚Don't spam my inbox, if you ask me very much or asking me something multiple times, I'll ignore it and I'll never answer it!

🖤don't steal/repost/copy/use my art without my permission, if you want to use my art as a pfp, ect, ask me first and credit me

💚I have Instagram, Youtube, Tiktok, Pinterest, whatsapp channel,Facebook and discord, so if you saw my art in another social, tell me immediately I will deal with it

🖤I still have some difficulties in drawing, so sometimes I have to use drawing bases to practice, so don't attack me please!

💚Although I like to draw cute things, on the other hand, this blog contains mature content, such as blood, cursing, and some chaotic thirst so be careful.

🖤for the art trade, if you want to do an art trade with me, you must be my mutuel, if you're not I won't accept to do an art trade with you.

💚as for commissions, If you want to commission me, you must be genuine and honest about it and not deceive me, otherwise I'll block you!! But if you'll be late in doing it or don't have the capabilities, there is no problem!

🖤if you're being rude to me, you're not welcome and I'll block you

💚Don't ask me about face reveal in private, even if you're close to me, I won't do this because I won't feel comfortable

🖤In this blog, you have the right to express your opinion, but don't interfere with mine because everyone has their own opinion and we must respect it!!

⚠️°•TW•°⚠️:

Swears

Gore/blood

Sexual themes

Violence

Bad grammar

Cringe behaviors

SFW (safe for work)

Vent

Simping (uhm fuck)

🤍°•FAQs•°💛:

🌟Q:what's your favorite fandom?

A: thomas and friends and this blog will be based with it thank you very much✨✨

_

🌟Q: what's your favorite characters from your favorite fandom?

A: James, Duck, Thomas, Gordon, Percy, Oliver and Toad, Donald and Douglas, Marion, Skiff

_

🌟Q: As for the engines, in their human form, can they fuck or reproduce?

A: Unfortunately, they can fuck whatever or whenever they want but they can't reproduce or have kids because they don't have biological hormones or DNA or whatever it's called like a normal human being

_

🌟Q: what are the ages in your Au?

A: 3 years until 60 years, There are those who are older than this, but I limit myself to these ages because I want them to be limited

_

🌟Q: what are your self insert's sexualities?

A: Every self insert into a random fandom has its own sexuality, for example my versions, I can't let all my versions being Asexual, bc if I let them it'll be boring so I tried to diversify their sexualities, for example Soft Jessy is lesbian, Bad Jessy is trans, Galaxy is pan, ect...

But fo the other fandoms I usuelly let them bi or pan or even straight to make sure that everyone has its lover/soulmate/partner/boyfriend/girlfriend...

_

🌟Q: how did you make your Oc's and are they real or imagined?

A: I made them randomly so that I don't feel like I'm filming the videos alone and that they aren't real people, I made them according to their personality, their life, the story of their past, etc.

_

🌟Q: who are your besties?

A: 🎧@miasonyson🎧

💞@lovable-chica💞

💎@asktoyokoakemi💎

💜@viktuurishipper96💜

🎀@bertramtheoldwarrior🎀

🌠@blueskygirl22🌠

🎩 @jammyjams1910🎩

💖@just-an-emily-existing💖

💟@prometheus2007💟

🐾 @thefluffyrailway-official 🐾

👁@tttemeetsthestarskys👁

_

🌟Q: are you doing art requests?

A: yes I do them,like if someone asks me to draw anything about TTTE Au or other fandoms Aus, But for their Oc's they just have to wait until June because it's summer and i will be active anytime

_

🌟Q: Are you gonna do art commissions?

A: Yes, I do them and I really want to, because I need some money to help my parents, so now I am waiting for someone to ask me

_

🌟Q: How tall are the engines?

A: Well, in terms of height, the shortest is Toad and Percy is the second shortest engine and he's almost 5’8ft,and the tallest engine is Gordon, The flying scottsman, Spencer and Diesel 10.Their hight is 7’11ft because they're big and tender engines

_

🌟Q: What are your favorite ttte ships?

A: None, I'm a multishipper XD, but here are some of them:

❤James x Emily💚

💙Thomas x Rosie🩷

💙Gordon x Rebecca💛

💚Duck x Oliver💚

💚Henry x Hiro🖤

💙Edward x Molly💛

💙Sir Handel x Peter Sam💚

🧡Rusty x Duncan💛

💚Luke x Millie💙

🖤Diesel x Mavis💛

....

_

🌟Q: Does Lady's magical dust have any benefit or any influence on the rest of the engines?

A: Yes, it definitely has a benefit for the engines. Thanks to it, it can save them from becoming victims of scrap, or if something physically harms them in their human form, it comes and treats them because ordinary doctors cannot treat human engines

🎀°•some basics of my Au•°🎀:

🌟some of my oc's transform into their true forms for many special reasons, for example demons, wolves, rabbits, etc., but the duration of this transformation is specific

🌟These reasons in particular may be either psychological, such as sadness, shame, and the desire to feel lonely and calm, or physical reasons

🌟The characters are distinguished from each other by their superpowers and magic, which makes them 100% different from ordinary humans

🌟Each one of us has his own personality, and this is the result of their personalities and feelings being different

🌟Characters can fuse and create new characters, but only if three basic conditions are met: If the two characters have a relationship of love, brotherhood, or strong friendship, If these conditions are not met, they will not be able to fuse

🌟ech character has a rival with another character, The reasons are as follows: Either he had a bad past, or that person was famous and forgot about his friend, and so on

🌟as for the humanized engines, their blood is a bit darker than a normal human being, and also if they lost anything or got cut like if they lost their arm or their leg or anything, don't worry, Lady is here for help

🌟and also they can eat, drink, wash their teeth,taking shower, and almost anything about humans, but the only thing that they don't do in their human form is breeding and reproduction, and the engines in their human form become even more stronger so they can done their jobs very fast and easely.

💗🌟Thank you so much for your time and reading this and i hope you enjoy your stay here again ^^🌟💗

✍����°•My Au's headcanons+Refs+ Stories•°🩷 :

❇️°•Commission info•°❇️

🌟°•Original oc's•°🌟

🚂°•Original engines•°🚂

🌹°•other social medias•°🎧

💞°•Official ships•°💞

♡__________________________♡

💫°•Some fandoms i drew•°💫

🖤°•Douglas and Oliver headcanons•°💚

🌈°•original face expressions+color pallet chart•°✨

💐°•Self inserts•°💐

🎀°•Some random ttte headcanons•°☁

♡__________________________♡

🚂°•The main 12 steam team•°🚂

📖°•ttte fanlore/AUs/fanfics/crossevers/series•°📖

💚°•the emo controller•°🖤

🖤°•Casual emo controller•°💚

🚂°•the narrow gauge engines•°☁

💙°•the Gresley family•°☁

🚂°•the diesels•°⛽

🪄°•Magical/ghost engines•°👻

🤍°•Other ttte characters•°🤍

✍🏻°•About my humanisation•°✍🏻

♡__________________________♡

✏️°•Some simple tutorials•°🖌

💙°•Original stories/lore•°📖

😌°•This could be useful•°😌

🎧°•Artist profile•°💚

🌠°•Unrelated ttte stuff•°🌠

♡__________________________♡

⭐°•Side blogs•°⭐:

☆• @sodormagicalworld (my ttte historical fiction AU) •☆

☆• @thesillybunny58 (a shitty blog where I can reblog some random posts ehe) •☆

[krakenartificer]

When I got my ADHD diagnosis, I looked at the questions on the screening form and thought, "If this result comes back positive, then I'm definitely not the only person in my family who has it." Questions like

"Have difficulty finishing one activity before starting another one" and

"I finish others' sentences before they can finish it themselves" and

"have trouble staying on one topic when talking"

...I thought were just weird quirks of my family, but no. When I got my results, I contacted my cousin, and she contacted her sisters and mother, and .. .. yeah. Basically everyone in my dad's side of the family is ADHD.

Now there are some problems with that, obviously, (getting family reunions to stick to a schedule is lol no) but there are some really fantastic perks. For one thing, no one in that family minds if I interrupt them while they're talking ... everyone's happy to keep 3 conversations going at the same time .... and no one minds if you fidget constantly.

But the best perk -- at least that I've found so far -- is that all of our parents have coping mechanisms, and passed them on to us. When I found myself unable to handle tasks with more than one step, my father didn't say "WTF are you talking about? It's easy! Just do the thing! Stop being lazy!" No, he could relate completely, and he sat down and taught me how to handle that.

So today, I'm going to pass on to you the coping mechanism my dad taught me for handling the "cannot put tasks in order / cannot get started / forget what I'm doing" problem. You'll need to adjust it for your own needs and your own struggles, but hopefully it'll be helpful in setting up your own process.

I'm going to walk through it with a big project I'm doing at work, just to have a concrete example. That will make some of the discussion specific to computer programming and technical writing, but I do the same thing for all my projects, so hopefully it'll be generalizable.

So to set the stage:

I was supposed to modify this piece of code -- we'll call it "Rosetta" -- to make it handle call data as well as what it was already doing. I did that.... but we now need the code to be able to handle calls (if that's wanted) but also to be able to handle NOT having calls (if THAT'S wanted).

Which is just .... ugh. So much. SOOOOOOOO much.

So. Break it down.

Step one is to get some recording mechanism - pen and paper, whiteboard, blank computer document, whatever

(Technically, this is a different coping strategy, so we'll just take a quick detour: WRITE THINGS DOWN. Your brain is shit at remembering things, and anyway you've already got limits on your working memory; why would you choose to tie up some of that limited resource in something that could be accomplished with literal stone-age technology? Don't even try to remember things. WRITE THEM DOWN.)

I like sticky notes: they're readily available in all offices, they're pretty cheap, and (most importantly) they can be rearranged if it turns out that I forgot a step or put the steps in the wrong order (which, like, let's be honest, I am definitely going to do). But they kill trees and create unnecessary methane emissions, so I've recently switched over to using virtual sticky notes. That's the format I'm going to use for this example, but you can use anything that meets your purposes.

So, you've got something to write with, you're ready to start.

The first question is: what are you trying to accomplish here? What would "done" look like? What is our goal?

I need to end up with a version of Rosetta that will make the correct results if you don't want calls, and will also make the correct results if you do.

The goal here is that you end up with a statement that you can definitively say (a) Yes this is what I wanted or (b)No this is not right because _______

In this case, in order to do that, I'll need to define "correct results" for both call- and non-call versions. But if I have that nailed down, then this statement meets that criterion: I'll be able to say "Yes, this is what I wanted: see, it makes the correct result for calls, and it makes the correct result for not-calls". Or else I'll be able to say, "No, this is wrong: see, it makes the correct result for calls, but on not-calls it does X and we wanted Y."

I have a clear, definitive standard about what I need to do and whether or not I've done it.

But there was a prerequisite there: I need to define "correct results".

So that goes on a sticky note: Create test that will compare my results to existing call!Rosetta-results and to existing not-call!Rosetta-results.

[ID: Two blue boxes, one on top of the other. The top one says in white text "Create test to compare my results to call!results" The bottom one says "Create test to compare my results to not-call!results"] OK. So now we know what we want. The second question is: what do we need to do in order to get that? Here's where the sticky-note recording system really shines, because you don't have to answer this question sequentially. You just start writing down every single thing that is not the way you want it to end up.

I need it to remove commas in the python script, not the bash script

I need to delete the first part of the get_runs() function, which doesn't do anything

I need to delete the rest of the parameters passed to build_query_script() function, because runs encompasses all the others

while we're on that subject, runs doesn't even need the group_variable, so let's pull that out of the parameter document

we also have a dmf defined, which the bash script demands but doesn't use; let's change that demand

since we're changing the structure of the parameter document, we don't need to pull new metrics for each run, so let's move that outside of the runs() loop and only run once

right now the parameter document is ALMOST but not quite "one row per template". Make it so it's actually one row per template.

among other things, that's going to require making it possible for a template to be followed by nothing at all, since it's the assumption that a template will have a metrics block after it that makes it not quite one row per template. So make it possible to publish a template with a null block

the other thing that's weirdly hard-coded is the definition of what a block looks like. Would it make more sense to separate that out into an input file, like the parameters document? On the one hand, that would make it much more flexible; on the other hand, that's another piece that can break. Don't know. Put a question mark on it.

etc

Here's what it looks like at the end of this step:

[ID: A black and white background showing many boxes in two different shades of blue, all with white text. Some of the boxes are overlapping each other.]

As you can see, at this phase you don't need to worry about any of the following:

ordering the tasks. Just stick 'em right on top of each other for now

how you're going to do any of this. Right now we just need to know what, not how

sticking to only one project. As I was working on this, it occurred to me that this whole process would have been a heck of a lot easier if someone had just made a user manual for this, and since I have to go through all the code line-by-line anyway, I might as well write up the documentation while I'm at it. (To help out future-me, if nothing else.) So I put those tasks on another color of sticky note.

making notes that make any ***ing sense to anyone else. This process is for you, and only you need to understand what you're talking about it. Phrase it in ways that make sense to your brain, and to hell with anyone else.

on that topic, also don't worry about making steps that are "too small" or "too dumb" to write down. This is for you. If "save document" feels like a step to you, then write it down.

You also don't need to get every single step involved in the project right now. Get as many as you can, to be sure, but the process is designed on the assumption that you ARE going to forget important steps, and is designed to handle that.

When you can't think of any more steps, then the third question is: what order does it make sense to do these in? Are there any steps that would be easier if you did another step first? Are there any that literally cannot be done unless another step is complete?

This is also a good place to group steps if they fit together nicely. When I used physical sticky notes, I used two different sizes; digitally I can of course make them whatever size I want.

So I have several documentation steps that (a) do need to be written to make sense to other people and (b) I really need to know what's going on before I can do that. I could write them now, but if I did, I'd just end up re-writing them based on things that change as I'm coding. So we'll move those to the end:

[ID: Three dark blue boxes with white text. They read "Create step-by-step instructions for creating your own metric agg", "Create step-by-step instructions for modifying a metric", "Create step-by-step instructions for modifying a query."]

These parts, though -- if I had all the variable structures written down, I could look at them while I'm coding. Then I won't have to keep scrolling back and forth in the code, trying to remember if it's an array or a dictionary while also trying to remember what part of the code I was working on. Brilliant. Move that to the front.

[ID: Seven dark blue boxes with white text, three large, four small. The first one is large and says "Write up explanation of how Rosetta works." The second one is large and says "Document structure of all variables." Attached to that one are four smaller boxes that say "All_blocks", "Runs", "metric", "New_block". The third large one says "Document what qb_parameters.csv contains"]

Also, while I'm at it, I should get the list of variables I need to document -- then I won't have to keep scrolling to find them. Make those sub-steps.

I definitely keep needing to look up what's in the parameters document, so I should write that down, too. For the user manual I also should write down what's in the metric document, but I don't need that for myself, so I can send that to the end.

[ID: The same three dark blue boxes from two screenshots ago (create step-by-step instructions for metric agg, modifying a metric, and modifying a query), now with another dark blue box in front of them with white text that says "Document what granular_metrics.tsv contains."]

These five are all small steps, and are all related in that they don't actually (hopefully) change the functionality of the code; they're just stuff left over from prior versions of this code. So we can lump them all together.

[ID: Five light blue boxes with white text that say "Delete first part of get_runs()", "Have build_query_script only receive the "run" parameter" "Delete dmf" "Move metrics=get_metrics() outside build_all_blocks (all the way up to the top level?" "Delete group_variable from qp_parameters"]

My brain likes this better, so that I can keep track of fewer "main steps", but that's just a peculiarity of me -- you should lump and split however you prefer to make this process easier for you.

[ID: The same five boxes from the prior screenshot, now all made smaller and attached to a larger box that says "Remove Legacy Code"]

Keep going, step by step, sticky by sticky, until you've got them in order. If -- while you're doing this -- you remember another thing you need to do, write it on a sticky and slap it on the pile; you don't have to stop what you're doing to deal with it, because it's written down and it's on the pile and it will get processed; you can just keep working on the thing you're on right now.

[ID: All the same boxes from the first screenshot, now in a neat row. Some of the original boxes have been grouped together. The ones that were said to be at the beginning of the process are on the left and the ones that were said to be at the end are on the right.]

Step four: for the love of all that's holy, SAVE THIS LIST.

Write it on your cubicle whiteboard where it won't be erased

write it on a piece of paper and tape it to the office wall

send an email to yourself

take a picture with your phone

I don't care but save it.

When I used physical sticky notes, I kept them all on the hood of my cubicle's shelf. Now, as you can see, I use Powerpoint, which is irritating af but does allow me to keep everything in a single document, which I can write down the path of.

[ID: White text on a black background says "open ~/Documents/Rosetta\ Modifications\ and \Documentation.pptx" The next line says "Notes in Rocketbook pg 10-12, 16" The next line says "Turn that into documentation that can be used for making modifications."]

And now (finally) you can answer the question "How would I even get started on that?" You look at the first thing on the list, and you treat it as its own project. You can hyperfocus on this step and completely forget about everything else this project requires, because everything you need to remember for the rest of it is written down.

If, as you're working a step, you think of something else you need to do for the big project, write it on a sticky and slap it on the pile. Don't even worry about trying to order it or identify sub-steps; as long as it's not blocking the thing you need to work on right now, you don't have to care. Just stick that bugger anywhere at all on the list, and go back to what you were doing. When you un-hyperfocus and come back to look at your list, there'll be a big sticky note stuck sideways across all the rest of the steps, and you'll remember to file and order it then.

Other benefits of this system

1) The first question really helps with unclear directions from your boss. You can take whatever they told you to do, and translate it into a requirement that is clearly either met or not-met, and then run it back by the boss.

If they say, "No, no, we want ______" then phew! You just saved a huge miscommunication and weeks of wasted work! What a good employee you are! What an excellent team player with strong communication skills!

If they say "Yes, that's what I want," then you know -- for sure -- what it is you're trying to accomplish. Your anxiety is reduced, and your boss thinks you're super-conscientious.

(And if your boss is a jerk who likes to move the goalposts and blame it on their subordinates, then have this conversation over email, so you can show it to their boss or to HR should it become necessary.)

2) Having this project map means that when you spend an hour staring at the requirements and trying to figure out how to get started (which, let's be honest, you were definitely going to do anyway) ... When your boss/coworker comes by and says, "How's it going?" Instead of having to say "I haven't even started 😞" You can say, "Pretty well! I've got all the steps mapped out and am getting ready to start on implementation!" and show them your list, and they think you're very organized and meticulous. 3) Sometimes, especially in corporate jobs, you and your coworkers will run into a problem that's too big for even Neurotypicals to hold all in their heads. At that point, the NTs will be completely lost -- they've never had to develop a way to handle projects they can't just look at and know how to get started. So then you pipe up in the meeting and say, "OK, well, what exactly are we trying to accomplish?" and everybody at the conference table looks at you like you're a goddamned genius and you don't have to tell them that you use this exact same process to remember how to make a sandwich 😅

4) Having this project map makes it so much easier to stop work and then start it up again later, but this post is already really really really long, so I'm going to address that in a separate (really really long) post.