🧵 How to Make Technical Documents
Anonymous at Thu, 12 Sep 2024 06:42:01 UTC No. 16375624
Just got a new job, former practically NEET retard here. To cut it short, I got a job as an Analytical Development in a big pharma company in my cunt. Only paid pennies during probation, but I digress. My supervisor tasked me with creating a set of procedure to analyze the dissolution profile of a drug the lab is developing and also a preservatives efficacy test for a beverage the lab is developing. The former is still within the scope of my experiece and knowledge as a chemist (albeit I am surprised by the adherence fo pharmacist to compendial literature rather than just scientific literature), but the latter is entirely alien to me.
I managed to familiarize myself with the industry's terminology and practices (theoretically that is), enough to fool people that I am familiar with pharmacist practices in conversation at least. Anyway I digress. I now have a rather solid idea of the procedure needed to run these tests. But little idea on how to propelry organize them and there are scant few resources available online. Also I'm working in a RnD lab, there already exist a seperate analytical development lab, but my supervisor decided to give me this job, and she herself doesn't seem to realize the full scope of it. Pic unrelated, need to post something fast since my supervisor is right beside me.
I think this is my last chance of escaping NEETdom, you are preventing a gamer moment by giving a good response to this thread. Thank you for your time faggots.
Anonymous at Thu, 12 Sep 2024 11:22:07 UTC No. 16376632
>>16375624
Be sure to delete all "As a large language model" from there and you'll be fine.
Anonymous at Thu, 12 Sep 2024 12:43:20 UTC No. 16376868
>>16376632
Well yeah ii cinverse with chatgpt as if it is my supervisor, we had a productive discussion btw, far more productive than with a human one, since this one actually i actually smart enough to communicate and accept when i point out its mistakes. But that faggot’s answers isn’t formatted nor detailled enough to make a technical document
Anonymous at Thu, 12 Sep 2024 15:01:13 UTC No. 16377037
>>16376868
Well, strange thing, maybe people who would communicate at current state of world, are separated by big digital gap they can't get over.
I find GTP somehow stupid, but it advanced a lot as I heard, since last time I've tried.
Anonymous at Thu, 12 Sep 2024 15:19:15 UTC No. 16377064
>>16375624
When it comes to documentation of this sort, start with an already drafted document from the same project/company that is of similar nature. This will give you the overall structure and formatting they are expecting.
There is a bunch of bullshit with doc control. If you are only writing a single document, the easy way to treat it is the doc rev process as a compiler check on it. They will kick it back to you for review for any formal errors. Be warned, they don't know jackshit about procedures and they won't be able to correct a process if you have it wrong.
If you are going to be writing a lot of documents, then you should refer to their SOPs and learn whats up.
In general, all documents in the project are going to have same section headers. Contents of the headers will be adjusted for the particular process.