All of the above.
Egoless programming has mostly to do with how much respect you have for the programmer who comes after you, who is going to have to figure out what you did with your code so that they can maintain it, and quite possibly improve on what you did (I know, that seems inconceivable, since all the code I write is already perfect ;).
I also believe that egoless programmers don't take dogmatic positions about their work. This makes them flexible enough to work in environments where their idealistic expectations may not always be so eagerly embraced or unconditionally accepted.
Pseudocode is, as the name implies, not real code, but it looks like code. It helps people to understand a problem domain or solution better without having to add all the baggage necessary when using a real language.
In short: it's used only for illustrational purposes.
Pseudocode and programming
There is no definition or fixed rule of pseudocode, it can be different each time. It is not a (real) programming language and no-one will consider it one. It cannot be compiled or used as a real programming language: if you could do that, it ceases to be pseudocode. Pseudocode does not need to be deterministic (a necessity for computers to compile), it rather needs to be understood by humans. To use pseudocode, you'll have to convert it to your favorite programming language. This conversion process can be different each time and no rules can be given for it because, again, pseudocode is like free speech: it can take any form.
Usages
It is commonly used, especially in the design phase of projects to help understand a certain approach to a problem. It's also commonly used in algorithm design, or when teachers draw something on the board. In all these cases it is not necessary to compile the code, you just want to understand the problem/solution.
Types of pseudocode
Pseudocode can be, but doesn't have to be of a certain type, i.e., you can have a stack-based pseudocode to illustrate MSIL, you can have an imperative pseudocode to illustrate Java, C#, C++, Python, you can have a functional pseudocode to illustrate F#, Haskell, SQL etc.
Examples
From the top of my head, but anything goes, because pseudocode can be invented on the spot:
XML pseudocode, showing a head+body structure that allows for multiple p-elements:
<head ...
<title ...
</
<body ...>
(<p>...)+
</
Imperative pseudocode, showing the diamond problem in languages that support multiple inheritance:
class A() { readFile(); }
class B() : A {} // overrides readFile in A
class C() : A {} // overrides readFile in A
class D() : B, C {} // what definition of readFile should be used?
The above two examples obviously resemble some (type of) language, but aren't really that language and cannot possibly compile. They rather illustrate something that you want to explain.
Best Answer
It means reducing lines of code, by removing redundancies or using more concise constructs.
See for example this famous anecdote from the original Apple Lisa developer team: