The document provides details about the experience and responsibilities of an individual named Kamal. Kamal has over seven years of experience developing .NET applications, including web services and web applications. He has experience with technologies like Azure and AWS and has worked on projects using Agile methodologies.
Download as TXT, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
22 views
Net Script
The document provides details about the experience and responsibilities of an individual named Kamal. Kamal has over seven years of experience developing .NET applications, including web services and web applications. He has experience with technologies like Azure and AWS and has worked on projects using Agile methodologies.
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2
Hi, my name is Kamal, I have seven plus years of experience in developing,
maintaining dotnet applications. I started my career back in 2014 to 2015 in India
as a software developer so during that time, I started developing dotnet applications and mainly focused on WCF web services and SPH web applications. And that's how I started after that. I started working on VC and mostly back in VPPs, using C sharp language. Along with that, I got exposure to cloud computing, like several cloud computing technologies like AWS and Azure. I worked on different services with dotnet SDKs. I worked on all past services on Azure as well as AWS. This is pretty much technology stack from my end. I worked with several clients. It was a globe, I have had experience with diversified teams, and I had different kinds of project experience right from greenfield projects, brownfield projects, where I was involved into projects from scratch, and also I did enhancements and existing projects and also I did production support. These are mainly I worked on, this is my experience with dotnet. And in terms of cloud side in Azure. I worked on different pass servies for storage I worked on Azure storage on blob storage, and for saving the secrets to the secrets I used azure keyword. for authentication. I used Azure Active Directory and for multi units, I used Azure b2c And I also used back end SQL and no SQL technologies. In Azure. I used Azure SQL DB and in Azure, we have a cosmos TV as well. And we also worked on serverless technologies like Azure Functions, blob triggers, Service Bus triggers and other technologies using micro services I build different applications. So in AWS also, I had s3 storage and DynamoDB and lambda different experience. Most of the services I would want cloud pass services. This is pretty much about me. And I have been involved in two different DevOps Services, right from release and build pipelines I created build pipelines and also release pipelines. And this is first CI CD poopers along with that, I also have experience on complete source control kit. I use Git and earlier days I was using TFS as well. And I was using Azure DevOps for a project maintaining like to maintain work items, moods and everything. This is technology wise and this pretty much prefer would done by me thanks .
day to day activities.
It depends on the phase of the project like most of the project we do work on Agile methodology. So we have two weeks of sprint and we will have patlak meeting during that time we do the planning, like how many story points for each story, we will review the story and we refine that and we assign the story points to the story. And once that is done during the planning, we will be assigned each story for each developer and we put it in, you know Fibonacci numbers like 1 2 3 5 8 13. The maximum stories that we take up is 13 for sprint, and mostly we try to split that to 8 5. So that, you know developer is not bombarded with too much workload. So usually I picked up one night story and if I may able to finish it quickly, I'll take up another story which is three points or two points and usually work on the pointers and mostly, you know, specific business logic has to be done so during the sprint first, I'll go through the story. And once I look at the user story, what has to be done which module I look at the code base and everything low level, I analyze and I make the changes. And I do the testing, I write all unit test cases for the code that I write and I publish this to be here and I'll get it reviewed by my artist as well as peer team so that we once reviews done there are no code comments, quarterly comments, I'll push this to our source control Once the code is pushed, what I'll do is we will deploy to QA and I assist you during the testing phase. And once everything is over, once we get to sign out we'll push to UAT and do a test set and then they will mark it is for ready for prod that's all the cycle in terms of regular day to day activities that I do. It depends on you know phase of the typical I will be into dev work. And then it is supported by team and few deployment activities and scripts are required to prepare scripts that are by example there are a few changes that need to be done. And sometimes we might receive a broad request also and we work on them and ad hoc request as sprint work. So we'll take up that also. There's pretty much in terms of day to day activities.