What is the point of these three methods inside a .NET project? Near as I can tell, you're converting requests for config entries that would be structured like Python variable names (snake case, e.g. user_name) into what is actually in your json config, but idiomatic .NET code shouldn't be written in snake case anyway. This is one place where having unit tests would explain your design. Is your intent for ALL languages to access the config using the exact same string of code, e.g. ```config.Database.admin.user_name``` in Python AND C#, or is your intent for the config to remain the same but each language to use it's native conventions? e.g. ```config.database.admin.user_name``` in Python and ```config.Database.Admin.UserName``` in C#, assuming a variable named config.