• they/them

Clown who draws and sometimes publishes games.
Icon by https://cohost.org/bachelorsoft!

Also mine:
@RPGScenarios
@DungeonJunk
@Making-Up-Adventurers


My Itch.Io Page
earthshaking.itch.io/
Dungeon Junk On Neocities
dungeonjunk.neocities.org/
Making Up Adventurers on Neocities
makingupadventurers.neocities.org/
My Dreamwidth Journal for Writing!
shaker-e.dreamwidth.org/

I have a test coming up today and I've got the material down, so I'm just kind of hanging out helping my neighbors when they get stuck. I started him at the hardest page and we worked through it so I could show how the trick if understanding the engineering stuff is knowing what info is found in which documents, and navigating from a blueprint, to a data list, to a part list, to the blueprint, and keeping notes for the relevant stuff.

It's not so bad once you get the flow. big aerospace company has a relatively easy to use database. The real difficult part is navigating giant busy schematic drawings one section at a time on a slow fucking computer with a small monitor.


You must log in to comment.

in reply to @EarthShaker's post:

i work in a similar field with a similar issue lmao it's backwards for us though. new hardware, but last major software update to our cal track system was 2012. Thing was made in 96 which isn't that bad until you remember that's when it was certified. The program had been in use since the 80's

lmao the software bugs and quirks are just something we deal with now

"Oh yeah even though it's a sister lab, it'll be considered a vendor cal unless you put this specific number in this specific spot. If you fuck this up the cert will be wrong and the whole QA process will need to be restarted"

Solution: just don't fuck it up lol

At least the software is stable due to calcification over the hard centuries