Standard term for instantiation practice
<p>Is there a standard term for the practice of instantiate a class without using an explicit constructor but instead initializing some of its properties?</p>

<pre><code>new SomeClass { PropertyA = true, PropertyB = "ugly code is ugly" };
</code></pre>

<p>I'm guessing there could be a standard not judgemental term and then there could be a negative term.</p>

<p>** --- ** --- EDITED POST CLARIFYING COMMENTS AND ANSWERS --- *** ---</p>

<p>Object Initialization it is.</p>

<p>After reading the comments I understand object initialization itself is not a bad practice; the problem is the lack of well defined constructors in favor of object initialization spread across a solution, which makes the solution much harder to maintain and to understand.</p>

<p>An example of bad use of object initialization:</p>

<ul>
<li>Class <code>Student</code> has 10 properties including <code>Code</code> and <code>Program</code>.</li>
<li>The code is instantiating this class from 10+ different points.</li>
<li>Every time, <code>Code</code> and <code>Program</code> are being defined through object initialization.</li>
</ul>

<p>In this case, class <code>Student</code> should have a constructor enforcing <code>Code</code> and <code>Program</code> to be passed on instantiation.</p>