I, always, am a big fan of simplicity. When I code. When using desktop/phone apps. When designing. Nothing’s more made me complain enough when it’s involve something I see or use like “it’s not that simple”. So I quite often, reinvent the wheel, to make or to use some other simpler.
I love Strong-Types. It’s make a breeze in my dev-life. I love how compiler will complain about your type if it’s a mess. That’s why I love Generic in .Net. You could say, I’m in love with all Generic classes/method. It’s simple to code. Simple to read.
When I give my take to choose which framework will I use, I’ll try ‘em all then I pick with most feature, then simplicity. Nowadays, I even more consider about simplicity. I dunno, maybe Microsoft’s Metro/Modern UI and Flat Design affect me in some ways. That’s why I hate when I had to use my company’s internal framework. They hard to code. With a bunch of feature, they sacrifice developer to make a bunch of config. It’s same for end-user, they had to make a bunch of config before they can use it.
That’s why I choose to make my own framework. No. I prefer to call it work tools or a library. Because it’s just a mere “plug and play” module instead of a framework which one could build something on top of it.
Choosing framework or library to help you in your project, always involving about which feature will make it easier to make that apps, which architecture will fit in your current design, or even which UI is most beautiful. But for me it is their style. The maker’s code style that make it simpler. Just choose one, simple to code but hard to use. Or simple to use but hard to code. Simple for both is even better.
To make many config simpler, I always code with naming convention in mind. You can make my library do something when you name it whit “X” for example. Without checking or storing the config. My library just simply check the naming and do it’s job.
I think naming convention should embraced more.