Friday, September 20, 2019

How to become a .NET Architect?

In this article, I try to research and keep information required to become successful .NET software architect.

Let's begin from basics.

Who is Software Architect?

A software architect is a software developer expert who makes high-level design choices and dictates technical standards, including software coding standards, tools, and platforms.

Who can become a Software Architect?

  1. One who is the lead developer
  2. One who has good knowledge in business domain
  3. One who has great view on technical domain
  4. One who knows how to improve the quality attributes of product
  5. One who has awesome system knowledge
  6. One who knows the need of their organization

What skills need to be developed?

  1. Thorough understanding of C# language (Advanced level skills)
  2. Good understanding of .NET framework
  3. Awesome insight on applications of Data Structure & Algorithms  
  4. Should have strong knowledge on OOAD
  5. Clear understanding on SOLID principles
  6. Great insight on Design Patterns
  7. Framework: MVC, MVVM
  8. Data Access: Entity Framework, Web API
  9. Web Development: ASP.NET, HTML, JavaScript, TypeScript

What are the soft skills requirement of Software Architect?

  • Interpersonal skills - Need to talk to business, technical and marketing teams in their lang.
  • Excellent in Communication - Laconic, Eloquent 
  • Personality - Very positive, Persuasion, Convincing, Empowering 




Thursday, May 2, 2019

When to use Microsoft Azure Cosmos DB?

Microsoft Azure Cosmos DB
  • The first globally distributed, multi-model database service for building planet scale apps
  • Azure Cosmos DB is the next big leap in globally distributed, at scale, cloud databases
  • Cosmos DB automatically replicates all of your data to any number of regions of your choice
  • It allows you to use your favorite API including SQL (Document DB), JavaScript, Gremlin, MongoDB, and Azure Table storage to query your data
  • You can easily build globally-distributed applications without the hassle of complex, multiple-datacenter configurations

Deep dive here: 
https://azure.microsoft.com/en-us/blog/dear-documentdb-customers-welcome-to-azure-cosmos-db/

Monday, April 29, 2019

Roles and Responsibilities of software architect in agile

I see in Agile world there are 3 defined roles exist:
1) Product Owner (PO)
2) Scrum Master (SM)
3) Development Team (DT)

But, are they enough to develop great software?

I see, moving from water fall model, Agile misses out below roles in a team:
1) Team Lead
2) Software Architect
3) Manager

In Agile world, we don't have any such role called Team Lead. Ok what was the typical duties of TL?
1) Planning a project
2) Recruiting resources ie Interviews
3) Reviewing team's work
4) Interacting with external teams
5) Project Status update to stake holders / customer
6) Giving feedback about team member performance
7) Having great amount of domain knowledge about product
8) Engaging team members in project

What architects used to do?
1) Having vision on program (multiple projects)
2) Defining architecture of projects
3) Choosing technology / tools to develop projects
4) Defining coding standards / Best practices
5) Collaborating with various team and customers

Though Manager role is not defined in Agile, there is no much difference for Manager role as they conduct Performance Review for team members.

In Agile, I'm sure many of us get confused who takes care of TL role and Architect role?
Though TL role is been done by DT, PO and Architect, Architect role still holds good and needed in Agile as well. It is because, the DT couldn't focus much on system and make decisions on technology and tools.

The below URL discusses on importance of architect in Agile:
https://dzone.com/articles/role-of-architect-in-scrum-team

Monday, January 7, 2019

How to add shared assembly info to all projects in Visual Studio?


When we have multiple projects in solution then every project used to have different AssemblyInfo.cs file under Project>Properties. So, if you want to change the version information for release or any other attribute in AssemblyInfo.cs file then you might have ended up doing same with every AssemblyInfo.cs of projects which is tedious and time consuming. Here is the easy solution for this problem.


1. Create SharedAssemblyInfo.cs file as solution item
Go to any project and under Properties folder copy the AssemblyInfo.cs file and paste in solution folder. Now, rename the file as SharedAssemblyInfo.cs. Then, keep attributes which needs to be reflected as same across all projects and remove the remaining items. Make sure the remaining items exist in AssemblyInfo.cs file of every project. Basically, we segregate items from AssemblyInfo.cs into AssemblyInfo.cs and SharedAssemblyInfo.cs


     2. Update the solution’s AssemblyInfo file with required details that needs to be updated for every assemblies being built For every release or build, we need to update only SharedAssemblyInfo.cs file under solution folder going forward.

      3. Link SharedAssemblyInfo.cs file with every project
Right click on Project>Properties and select Add > Existing Item
From the file selection dialog, get into solution folder and select SharedAssemblyInfo.cs and then make sure to add the item as Link like below (Add As Link). It is very crucial to select Add As Link otherwise (if Add would have been selected) visual studio would just create copy of SharedAssemblyInfo.cs into Project > Properties folder which cut the common update we want to make across all projects.


Now, go ahead and build solution. Every project would have  same version number and other attributes defined in SharedAssemblyInfo.cs file now.