What does "Knowledge of the basics of OOP" mean?

Question

OOP

Almost every job in the spirit of "C# Programmer (Intern)" requires knowledge of the basics of OOP.
Can someone please explain what is meant by the word "basics".

Answer 1

Recommended reading
www.ozon.ru/context/detail/id/4574420

Answer 2

The ability to answer two button accordion questions: -
What is the difference between an abstract class and an interface
- Why in C ++ it is impossible to throw an exception in the destructor (yes, in such a formulation, giving out that the questioner himself is not in the tooth with his foot).
But seriously, this is the ability to design the object structure of the application well, which is expressed in the knowledge of what you can do with classes in general, how to organize their relationships with each other, and how not to do it. Achieved by many hours of practical experience.
Interesting article: How two programmers baked bread.

Answer 3

If you know C#, then consider that you already know the basics of OOP. The basics of OOP are encapsulation (hiding an implementation behind an interface), polymorphism (the ability to use multiple implementations of a functional - for example, overloading methods), inheritance (I think it’s clear here). This is the basics of OOP. Usually, in books on C # and on Java, they write about these concepts everywhere and show what and how it looks in the code.
And you also need to be able to write generic classes and methods - very important for C # and Java.

Answer 4

Obsession with Awesome Patterns

Answer 5

It doesn't really mean anything since C Sharp is a completely OOP language and it goes without saying that you know everything about OOP.

Answer 6

those who say that everyone who writes in Sharp knows oops: I disagree, I wrote several projects in Sharp using only a structural approach (I'm not proud of it).

Answer 7

Obviously, because there is no return statement after the conditions.

Answer 8

Because it happens when everyone is equal