For a few years now, I’ve been coding on .NET, SharePoint, and the like. I went to University and learnt about Object Orientation. I hardly noticed nor appreciated the many OOP concepts that I’ve unconsciously applied to my coding/solution design. Dare I say it, I think this may describe many developers with around 2-4 years of coding experience up their belts.
I recently started reading a few articles online and came to realisation of the extent to the level of OOP concepts that have actually been applied. It made more sense why some of solutions worked better than others (of which include both .NET and SharePoint solutions).
Like many others, I’ve just had the time to understand and learn how to use API’s and/or how to ‘structure’ code to get the job done in the least amount of time with the best quality (least amount of bugs), but never to understand some software architecture concepts. Take my tip, re-learn the concepts that reflect what you already know – a design pattern.
Here are the links I have referred to: