A property IsEmpty, as suggested in another answer, is syntactic sugar that improves readability.Node should be a nested class for better encapsulation.It should be an extension method declared elsewhere. Create the node before the first if statement.

Push has a redundant creation of a node.This would remove a specific node, even if multiple nodes hold the same value as the specified node. Consider making it public if you would provide mehods as Remove(Node node). Given the few operations you provide, it could be made private. Node could be made public, but then its state should be private or internal at best.Call it LinkedStack (conform naming convention LinkedList). The name of a class should tell you what it is, not how it's implemented.They provide a Count to indicate eager iteration is provided ( Interesting Discussion about IReadOnl圜ollection). Don't be fooled by its name, collections implementing this interface are not stipulated to be immutable. Implement IReadOnl圜ollection to provide a property Count. Implement IEnumerable to let consumers iterate the items. A class representing a collection should always implement the correct interfaces.It should throw InvalidOperationException when empty. It can throw a NullReferenceException when the stack is empty.

You should always provide unit tests when providing a class to consumers of your API.

Your class should be generic to be usable.

The class access modifier does not allow public access, so your class is not usable by third party consumers.

Linked list stack