#what sorting system LMAO

[jichanxo]

ok, i’ll bite: how pathetic is kitakata in sensei au fic in a scale from 1 to 10, and will he have some kind of kuwanafication-level fuckup (or at least a chance to fuck up that much)?

omg hi… thank you for asking… (twirls hair around my finger)

this got long (of course it did) so it's under the cut for those who would prefer to scroll past.

okay pathetic level… uhhh ummmm hm… how to quantify… I want to say either a 7 or an 8? he does embarrass himself quite a bit. he has no idea how to act around yagami FOR SURE. so while some of that is just him being annoying, a good chunk of that is. flirting. and he’s SO confident about it even though he keeps failing over and over again… buddy you gotta take a hint… and eventually something comes of it! but yeah he’s super embarrassing about it. and he’s down so bad for yagami. and his bedroom talk… yeah he’s lame. he’s very lame I think. trust me. (using my best judgment here)

kuwanafication-level fuckup… so far? no. current plan for this fic is essentially a mishmash of lj school story and kuwagami-romance-drama bullshit, so just by having that as the basis, there isn’t really that much opportunity for something that life-changing to happen, really. I have most of the kuwagami-romance-drama bullshit side of the story sorted, but I still need to figure out more of the school story side of this fic (I gotta go over em and take some detailed notes to make sure I write it correctly…), so there’s still a chance that something else will pop up as I write it, especially depending on how things with Itokura shake out, but so far there aren’t any plans for anything like that.

it’s definitely kind of this idealised universe where everything Just Goes Well, yknow… a contrast from canon… but this kind of mundane kuwana is nice too… he’s done his best to try and learn from his near-fuck-up. he’s not perfect but he tries.

in regards to Kusumoto Mitsuru, since it’s important and I don’t remember clarifying this in any post/tags – the deal here is that kitakata still fucked up but he managed to fix everything at the last second before mitsuru died. so kitakata’s kind of had the lesson but without the, yknow. the transformation. I wrote about it as a kind of prequel here if you haven't already seen (obligatory reminder to heed tags etc since it's heavy stuff). I assume that’s kind of sort of relevant to what you’re asking? it’s not that this kitakata never had it happen to him, he messed up and he was forced to stare that in the face, but he managed to avoid the worst outcome, took responsibility, tried to change and continued on with a renewed perspective on his job.

but let’s go back to kitakata actually fucking up during senseific, because I definitely have that! rn the most obvious example is yagami and kitakata getting into a fight and sawa having to intervene and tell them both off for it. it sounds silly when I put it like that, but in context it’s a big moment and a big deal for them both. it’s not just kitakata’s fuck up and it’s there’s more to it obviously (kitakata wouldn’t get all worked up without reason, right?) but yeah, having your kouhai/ex-student have to intervene because you’re trying to punch a grown man in the face? it’s a fuck up. lmao

[nipuni]

THE DOCTOR We had a pact, him and me. Every star in the universe, we were going to see them all.

My version of The Master and The Doctor in their Academy days 😊

A speedpaint video of this will be available at my Patreon on april 1st!

[telesodalite]

Never getting over Fulcrum being a project manager...

Idk why, but something about that is so funny to me. Not just because the title of "project manager" is inherently kinda funny for a Decepticon, but also because-

1. It's vague sounding and hard to explain irl because it technically exists in multiple fields, like healthcare or manufacturing, which surely translates into canon in some way.

2. In canon, it's simultaneously a really mundane, innocuous sounding job, yet it's also a super morally awful position to reside over depending on the context. (*cough* forced colonization and cyberforming *cough*)

And 3. It solidifies the fact that behind all the surface level militaristic work we get with both the Decepticons and Autobots, there's also Cons and Bots with "normal" jobs in both factions.

Like, sure yeah we get scientists and doctors, engineers and programmers, but usually in big important or warfront positions. (For plot reasons, understandably.) But it's also really funny and interesting to think of those that worked background positions, or minor jobs.

Like an Autobot working in their equivalent of an HR department, or a Decepticon who runs one of their outpost's or starship's kitchens.

Just all the pre-war jobs that didn't just disappear with the war, but instead evolved to exist within the factions.

It's particularly funny with the Decepticons though, because it could be a super mundane job or situation, but because it's them, it has to have an air of ~e v i l~ to it, either legitimately and/or merely for the vibes, like Tarn's "performance reviews".

[yellllowstar]

slowly I'm recovering the beauty of discovery

(creature by half•alive)

(textless + timelapse below cut)

[emry-stars-art]

Doodles after learning the different meanings of different wax seals; according to this infographic using blue wax indicates romance or passion, the darker the blue, the stronger the feelings. Abram only has red wax (the default option) if any at all, but luckily he knows exactly who to ask when he finally learns there’s a separate proper way to seal certain sweet letters to his prince

Find the royal au masterpost here 💕

[amateurmasksmith]

who the fuck is magnus, and what the hell did he do to get both an archive and a protocol named after him??

[dunaldoodles]

So this is a casual look to the inside of my head at all times. I had to do a role call 3 times to figure out who wanted to be where because they were all picky. You get a virtual cookie if you can name all of my nicknames for these guys. Maybe an art. Depends!

[coredrill]

sorry i’m still insane abt gravion. more posts incoming

[nintendont2502]

wait who blocked you

calware i think lmao

idk none of my comments ever show up on their posts + if i reblog something from them my rb doesnt show up in the notes but. eh. again im not gonna go bother them abt it yk if they did block me thats their call :thumbsup:

[darthyolk]

I've finally finished my first boss for my demon hunting game Judgement Nights! A guard dog for a much stronger demon, Grub keeps their secret safe and hidden from all mortal or demonic eyes

[voorice-corp]

"Victor is/was religious"

broke: saying he's vaguely christian and not elaborating any further

woke: making up a wholeass fictional pantheon n mythology for this purpose and nothing else

[keeps-ache]

the urge to talk my head off vs. the calm of quiet vs. the Thoughts

[voidimp]

i hate insurance companie

[dandyshucks]

fellas.... the art is not going well tonight, I'm ready to start gnawing on my sketchbook

WOE to the artist who tries to draw shit above their skill level AUGH

[c-infinity-83]

... If all goes well we might've switched Mains again. Yippee????!!

[trisockatops]

I know no one cares, but Imma go through this anyway.

More work shit!

So we're working on vapor (air) wells. These are monitoring wells to see if clean up of contamination is working, if the contaminant plume is moving, etc. It's oil, so contaminated wells are "hazardous" and you can legit smell and be effected by the oil during the purging/sampling process. The wells in places with no contamination to make sure the contaminate is migrating are "clean".

I had a well the other day that set off immediate alarm bells for being something weird. This project has been going on for decades. Every year, they update a list of what wells are determined hazardous or clean based on the previous quarter results. You check this before doing any sampling because you use different equipment depending on if the well is clean or hazardous. Well wasn't on the list, which was weird. I should have just asked then, but I figured maybe we didn't sample it last quarter for some reason, but the paperwork is here, so I should check out the well first. Plus, the well had another port at a very similar depth that was hazardous, so it follows this one would be hazardous as well.

I get to the well, and that port is flooded. It's collecting water. More alarm bells. Something is weird here. I've never seen a well get flooded in this particular way, but hey. The wells get flooded sometimes, so I'll just soak it up and move on.

We leak check the wells before sampling to make sure we're sampling the well and won't be pulling ambient or anything. There's lots of replaceable parts and we do quarterly maintenance, so sometimes it's just a simple as things don't get tightened well enough. Leak check involves putting a cover over the well with tubing coming out that connects to each individual sample port. We flood the well with argon (since, we don't sample for this, as it's not a contaminant of concern here). We test the well to make sure it's flooded. Then we test each well port to make sure they're a closed/contained system. This involves hooking the tubing up to a motor and collecting the exhaust in a tedlar bag.

Well, I can't get this port to flow at all. Flow rate is zero, so I can't fill up the tedlar. That's not a leak. That's the opposite of a leak. Sometimes the tubing gets kinked, so I try three times to reposition the tubing. Still no flow. Now that's bizarre. Now I could say, no air is pulling, so obviously the system is closed. Only the system is too closed. We need to pull air to purge and sample the well. If I can't get air for leak check, I'm not gonna be able to get it for purging or sampling.

Okay, that's three alarm bells about this well.

So, I call the PM and ask if there's anything wrong with this well or what's up with it.

Yeah, the well is plugged and has been for years, which is why they drilled another port in that well at a similar depth (most depths are 50 - 100 ft apart, this one is only 6 ft), and it just keeps getting missed every quarter to pull that paperwork (which, tbf, is a huge oversight).

Great! I am relieved. That makes sense, and that's one less port to sample than we thought.

Then PM thanks me for calling her about it because last quarter, two employees sat on that well and purged for two hours, and they only called to say something was wrong when they couldn't collect a sample. (Sample cans are negatively pressurized so they pull in air when you open them. Well, when opened to a system where no air flow is possible, the pressure will never change, and so you can never complete that sample, as we start a sample at around -25 psi and collect until about -5 psi.)

Okay, I remember that now! Had totally skipped my mind, but I specifically remember thinking "oh, kinda glad that was them and not me because I can imagine myself doing the same thing, and that's pretty embarrassing and a complete waste of your day and that sucks. Like how would you even know that?".

And, BRUH, NOPE. Like...how!? Okay, let's say they assumed no air flow during flow through meant a closed system and they were therefore fine. You literally CANNOT get through purging in a plugged well! Purging means to remove a specific "well volume" amount of content from the well (usually three well volumes) to ensure you're getting a fresh, representative sample rather than stagnant, old stuff that isn't very representative of the current environment because who knows how long it's been sitting there. The volumes are pre-calculated, and you are given a very specific flow rate to pump/purge at which is dependent on port diameter. Since different ports are drilled at different diameters (for stability, dependent on depth), ports have different flow rates. You are supposed to 1) check the pre-calculated flow rate because the ports can look similar but be different enough to have flow rates nearly double each other, and 2) periodically check the flow rate through purging, especially right after anytime you plug the system back in.

So either they noticed the flow rate was 0 and just shrugged and figured it would magically work itself out (??? super wrong, not at all what you're supposed to do; that fucks up the calculated volume, it is VERY against the approved work plan which can get our contract terminated and the data invalidated if we are caught deviating from it) OR they weren't every checking flow rate on any well they were doing and collected a fuckton of data that just got invalidated, has to be thrown out, and can't be used because we have no idea if it's actually correct or not.

This is why it's important to understand WHY the processes are what they are and not just memorize the steps. Turns out it COULDN'T have been me because I put forth an ounce of thought into what I was doing and correctly followed procedures. And it was not actually that hard. I have never dealt with a plugged well before, and I still had enough common sense to stop and troubleshoot and not just shrug my shoulders and say fuck it.