Poor practice to include code in default constructor
c#, oop
Solution
That depends on the situation, sometimes it's needed, sometimes it can be used, sometimes it should not be there.
What's important is that any constructor should leave the object in a properly initialised state. If an object always needs some code for initialising, but no specific input to do that, a parameterless constructor would be a good place for that.
Problem
I worked with a developer that had many years my senior in C# experience. I no longer have a way to contact him and I remember him saying that it's not a good idea to include code in a default parameter less constructor but I cannot remember the reason why. Is it good practice or bad practice to include code in the default constructor in C# or any language for that matter?