I just finished a my C# and Software Architecture Training yesterday that spanned for 2 weeks. The first week was spent on basic C# .NET programming, while the second week was on the company’s software architecture standards and design. It was a very useful training as I may say. I can’t say that I’m now an expert on C# programming, but since C# coding is very similar to Java, I think it won’t be long ’til I become competent with C#. 
Regarding the software architecture side, it’s actually not very new to me. As far as I know, it’s more or less just like what we have with my previous employer. The N-Tier architecture, the separation of the UI and business logic, and the components of the data layers are all the same. I think most software companies adapt this kind of architecture which provides a lot of advantages when it comes to interoperability, usability, scalability, maintainability, manageability, and security. The training just provided me some useful in-depth information on design patterns and how the components of our product line fit together.
I’m now trying to understand our source code based on the things I learned from the training. I may not be a developer here, but then as a Configuration Manager, it’s still useful to have a thorough understanding of the codes and it’s architectural design.
[tags]C#, .NET, Software Architecture, Design Patterns, Training[/tags]
Popularity: 3% [?]