• I use Tutorials, Udemy course to start with a hello world application of my own

• Then learn individual features on those technologies and enhance my skill set with that particular technology

• When I get a chance, I try to use that in my work.

• Problem solving

• Team interaction

• Learning and implementing new technologies

• What is the one thing that we can do better that would help us to better serve you?

• What is the one thing we could add to the product / service that will help improve your efficiency?

• What are your pain points with us and how do you think we could fix them?

• How can I help provide more value to your organization?

• What would be the timeline that you expect the thing to be released?

• In my current job I had a situation where  I happened to work on implementing a new application where we had a discussion in a team on choosing UI framework/Library.  

• For one my team lead suggested angular as I suggested to go with React.

• React. js uses virtual DOM and one-way data binding while Angular operates on real DOM & two-way data binding.

• There's also a difference in bundle size (React's smaller) and speed (React works a bit faster).

• Angular is a framework where react is a library we can use in any existing  application.

• Isolated debugging, which helps us achieve better app's stability.

• Those are a few differences that I explained to the team and  then we finalized to go with React.

• I have took lead in learning the React JS

• And I developed a few POCs on React and I demo to the team members.

(OR)

• I have took lead in learning the dockers

• and I used them for architecting the microservices for my project.

• This is one of the places where I got good appreciation both from my team and project management.

• Yes, every developer experiences these.

• It was always for the betterment of the team – we were active in

• I don’t look at conflict as conflict

• Healthy discussion.

• Face to face communication

• It should be see from the angle of project and resources we have

• We should evaluate the pros and cons of different approaches

• We should should sit and discuss professionally rather than bringing the emotions

Axios is a very popular JavaScript library you can use to perform HTTP requests, that works in both Browser and Node.js platforms.

• It supports all modern browsers, including support for IE8 and higher.

• It is promise-based, and this lets us write async/await code to perform XHR requests very easily.

• Using Axios has quite a few advantages over the native Fetch API

• supports older browsers (Fetch needs a polyfill)

• has a way to abort a request

• has a way to set a response timeout

• has built-in CSRF protection

• supports upload progress

• performs automatic JSON data transformation

• works in Node.js

I wouldn’t call it a conflict, but we were asked to perform http requests and for that – we had to choose between Axios and fetch API. Axios had a few added advantages like….. Therefore we had a long discussion on which one would be a best fit for this specific requirement and solved it.

• My day starts with standup meeting

• I would go through emails

• The I switch work on the tasks/stories I am working

• Usually I would participate in refinement, retrospective, whiteboard meetings we have.

• I do code reviews, code releases, Pull request approvals

• I do coding, testing , debugging, deployments

• I also interact with QA, BA, UX and architects

• Design, implement and maintain java application phases

• To take part in software and architectural development activities

• Conduct software analysis, programming, testing and debugging

• Identifying production and non-production application issues

• Transforming requirements into stipulations

• Develop, test, implement and maintain application software

• Recommend changes to improve established java application processes

• Develop technical designs for application development

• Develop application code for java programs

When a story/task assigned to me initial step what I do isI will go through the business criteria/Documents Provided. If I don't understand then I will check the code/previous documents attached to that story/ticket to understand. Still I don't get it. Then I will approach people based on the questions that I have.

I will set up a meeting with the appropriate person .

• If it is related to technical issue - I will contact Senior Co- Developer

• If it is related to business then - I will approach BA/Product owner to check what is the actual business criteria for that particular story/task

• If it related to deployment or related to database then I will approach Devops/DBA

• If it is related to quality I will approach QA

• If it is related to the process then I will approach the scrum master or project manager.

• Understand the business

• Understand the policies, workflow, procedure

• Understand the environment – code bases are different?

• Understand the pull request and release processes

• Communicate with team mates

• best way to learn

• Understand the business 

• Technical => co-senior developer ,  tech  lead, architect

• Testing=> QA

• Business => BA , Product owner

• Deployment => Devops, co-senior developer ,  tech  lead

• Process => Scrum master, project manager

• Working examples

• Pros and Cons

• Industry wise examples

• Proof of concepts (POC)

• This happens sometimes, when new requirements or hidden challenges comes in

• Clearly explain the importance of why to attend that requirement or new scope

• If required I demo with POC’s

• My focus for the next 1-2 years is to explore new technologies: UI frameworks, AWS services, Distributed Services, Message Processing. I want to progress to higher role, gain more responsibility and lead some projects 

Health and wellness services, pharmacy services, health plans, prescription drugs and retail and online stores. 

In one of my projects that was previously designed using jquery, the main motto was to migrate to React but there was not enough documentation to understand the legacy code. Therefore, when I was assigned a story, I used to coordinate with the BA in a refinement meeting (explained my concern with the code) and performed reverse engineering to convert to React js and react native. (project was bootstrap with create react app) 

Series of sprint – team architect, check if it’s a common issue with QA – if its determined to be a new, report to BA or team mate. 

Scrum Ceremonies

• Sprint Planning => Grooming, Pointing (1,2,3,5,8,13,21), Tasking

• Daily Standup => Yesterday, Today, Raodblocks

• Sprint Review (Demo)=> Demo to Product, Statekholders, Feedback

• Sprint Retro => Good, Bad, Improve, Appreciations

• Sprint Refinement => Refine Backlog

• WhiteBoard => Developers and Architect meeting (Implementation design)

Understand the business

Understand the policies, workflow, procedure

Understand the environment – code bases are different?

Understand the pull request and release processes

It was always for the betterment of the team – we were active in

I don’t look at conflict as conflict

Healthy discussion.

Face to face communication

The greatest achievement I can quote with respect to my work is that In my current project with CapitalOne. I have been tasked to improve the performance of reports generation.

We have a large amount of data accumulating in our databases. Running a query to generate a report is taking a lot more time than usual as the amount of data is growing over time.

Team started to try different approaches like query optimization., Lazy data loading etc,

All of them worked for a while and over time the issue started to repeat as the data increased in volume

I researched for a solution and I came up with a solution to use a nightly job to get the data using SSIS.

I was new to SSIS and SSRS but I learnt those technologies quickly and was able to write the jobs that run every night to fetch the data, filter and transform it to generate report data. Which gets stored in report tables. There by drastically reducing the time for report generation

Communicate with team mates is the best way to learn

Based on the what issue is related to I would talk to respective person like if it is related to

• Technical => co-developer ,  tech  lead, architect

• Testing=> QA

• Business => BA , Product owner

• Deployment => Devops, co-senior developer ,  tech  lead

• Process => Scrum master, project manager

When a story/task assigned to me initial step what I do is I will go through the business criteria/Documents(BRD) Provided. If I don't understand then I will check the code/previous documents attached to that story/ticket to understand. Still I don't get it. Then I will approach people based on the questions that I have.

I would ask him/her to refer the team coding standards documents

Will discuss over the code review sessions

Will mention the suggestions in code pull requests

I would size the stories by considering effort, complexity, uncertainty. I would try to answer the questions

Effort. How much work is required to complete this task?

Complexity. How difficult or complicated is this task?

Uncertainty. Do we know exactly what must be done to accomplish this task, or will we need to learn as we go?

Fibonacci Series for pointing

To be on track with Work, Time, Budget 

Working in teams increases collaboration and allows brainstorming.

Two or more people are always better than one for solving problems, finishing off difficult tasks and increasing creativity.

Everyone is unique and has different skills, backgrounds and experiences.

• Better problem solving.

• Increased potential for innovation.

• Happier team members.

• Enhanced personal growth.

• Less burnout.

• More opportunities for growth.

• Boosted productivity.

• Smarter risk taking.

• For me It depends on the situation and the requirement

• How soon it to be delivered

• What’s functionality of the code that attends

When a User Story is allocated and I will go though description, acceptance criteria. And it has dependencies as well.

I will take all those and do the development.

After development, I will write unit tests and then I will create PR.

Once PR was approved and merged.

I will Move it to a QA environment. After qa validation, it will be moved to UAT & then deployed.

What is team composition like how many developers?

1. Do you people follow agile processes?

2. What type of typical meetings you people have?

3. How does a typical workflow of stories look with your team?

4. Technologies followed in your project

5. What would be challenges for a new joinee?