Oy... bios. I'm horrible. No, really, though in a REALLY nice, polite, sociable, and gentle way. Utterly evil. I have very little use for the vast majority of social mores, though I have an extremely strong and binding ethic.

Moral. Ethical. The difference is important, and more often then not horribly misunderstood.

I have been accused of being a Socialist, though I suspect this isn't really accurate, I simply believe in the greatest good for the greatest number. No I am not a Communist. It doesn't work.

Power and Force are not the same, and people who confuse them make me all grumpy.

from user null, an excellent explanation of Trump.

There are three states Trump can be in:
Malignant Narcissism
Senile (or other) Dementia
Mix of both.

If he's narcissistic, he's aware of the rules in as much as he can use the rules to get whatever he wants and use do whatever benefits him, and when the rules get in his way they either magically cease to exist in his mind or don't apply to him, or when you cite the rules you are using them in the wrong manner/context or you're just wrong/making shiat up.

If he's senile dementia, he's literally not able to comprehend there being any rules, or how the rules apply, or he forgets that there are rules, or when you cite rules, you're making shiat up and attacking him.

I've had to deal with a malignant narcissistic family member with a side order of brain damage/memory loss/transient amnesia.  "I reject your reality and substitute my own" is taken to a whole new level.  You almost have to treat those people like robots or computers with a flaky, buggy, paper-tape-based bootloader, a failing 360KB floppy for his OS and storage, and very limited RAM.  You boot them up every day off an extremely limited program and try to limit the input they're exposed to with the hope that something doesn't blow the stack and dump bits of garbage data all over.  You pray that whatever they write to disk doesn't overwrite critical data, and you shudder in fear when they go to read from disk and you hear the motor and read heads make the "oh shiat disk read problem" noises, because the DISK READ ERROR subroutine doesn't return a failure code and abort, it actually tries to interpolate and error-correct whatever data it manages to read at all until it fills out the request for that disk sector and moves on.  If you can keep everything on track and minimize the interaction to limited validated inputs, you will probably have few instances of them spouting garbage to the output devices.  If you throw them something outside the tested and validated input, watch out.

You can literally see this in action with Trump based off of reports in the media.

Before Kelly, people would shove random shiat in Trump.EXE's stack of stuff to read, and Trump.EXE would throw an exception upon reading it and blast it on it's Twitter output device.

If Trump.EXE is fed Fox and Friends on his audio and visual inputs, whatever they say hits the non-maskable interrupt and is fed into the FIFO to its Twitter output device.

If Trump.EXE is kept from following the normal routine it gets extremely cranky and hard to predict/handle (see also trips).

Trump.EXE has a limited vocabulary and keeps repeating the same things, and gives the same answers to questions.

If Trump.EXE doesn't have an answer buffered in RAM for a query, it tries to read from storage on the floppy and either gets something written to disk long ago (and that the failing write heads can't overwrite) or it makes shiat up from whatever scraps it could read off the failing sector.

If you're having a bad day, the paper tape bootloader doesn't even get to the point of handling the floppy drive interface to load Trump.EXE.  If you're having a good day, the paper tape bootloader managed to properly initialize the system and detect and load Trump.EXE on the first attempt.

If you're having a really good day, Trump.EXE has room for more than three items on the memory stack.  If you're having a bad day, Trump.EXE has got room for one and the next input pushes the last thing off the stack, erasing whatever what previously input.
If you're having a really bad day, Trump.EXE eats the buffers on output so the next line of output erases all memory of the previous line of output and the system claims the previous line of output never existed.

And the best part is, if Trump.EXE crashes during the day, without a cold reboot (naptime), the system fails to reset volatile memory, so upon reload of Trump.EXE, RAM contents are non-zero (indeterminate) but scrambled, and any input and output become completely garbled.

/Trump is the living example of Management Stack Theory gone horribly wrong.