Or you could, you know follow either a naming convention or a parameter convention... For that matter, you can have each method simply test the data and return null if it doesn&#x27;t apply and the resolved value if it does, or any number of other patterns...<p>For that matter, you can use an object stream, and pipe it all through to resolution.  If your data comes from variant sources (spreadsheets, dirty xml, etc) then you are way better off with a scripted language.<p>Try importing a WSDL that defines various interfaces to use &quot;Object&quot; and VS&#x2F;.Net chokes on it.<p>As far as users go, without the hard enforcements you can coerce values into either what you expect or cleanly drop out... unlike .Net where you have to go through the Try versions of convert, on who knows how many types in order to get something resembling predictable values... that doesn&#x27;t even include regular expression syntax as a first class concept in JS.<p>I&#x27;ve handled dynamic input sources from both .Net (VB.Net and C#) and I&#x27;ll tell you that most of the time JS&#x2F;Node is simply easier...  I&#x27;ve replaced complex importers written in .Net with straight forward, easy to reason with JS importers that run in Node, and edit&#x2F;run&#x2F;deploy without a compile step.<p>I will say that I do like that VB.Net has XML literals which can be very useful... but now that JSON is getting to be more common JS is less of a disconnect.