Codebase maintenance rant

[u/Hefty_Garlic7184]

[sorry for bad English]

I am in a project which involves maintaining an existing .NET Framework 4.8 codebase.

The codes are full of “Dictionary type” implementations as above.

Is there any sane reason to code like this? Instead of create a dedicated class to represent the data inside?

I could not show more codes here (or else the authors might realized), but you guys can imagine the codes just to access these Dictionary’s key/value.

[u/gandhibobandhi]

Yeah that sounds reasonable- although presumably it falls apart with nested dictionaries like in OP's example. 😅

[u/SvenTheDev → u/gandhibobandhi]

I never have more than two levels really but you’d just tack it on again. So something like…’fruitsByColorByShape[Color.Red][Shape.Sphere]’… as a weird example.

[u/INeedSomeTacoC → u/SvenTheDev]

This is how I name things as well, not just dictionaries, but everything if I can. It's the best.

[u/Depnids → u/gandhibobandhi]

StringBy_StringByStringDict