Suggestions
Nirmal Christopher
Senior Specialist Salesforce
Nirmal Christopher is a skilled and experienced professional with a background in software development and project management. Graduating with a Bachelor of Engineering degree in Computer Science from Anna University, India, Nirmal's exceptional skills led him to work at reputed organizations such as Mphasis and Cognizant.
At his time at Mphasis, he developed software for financial clients in the United Kingdom. He went on to join Cognizant, working for over six years as a software engineer and lead. At Cognizant, he developed and maintained the financial software used by the Royal Bank of Scotland. His teamwork and project management skills eventually led him to become a project manager, where he led the project management office for Cognizant's banking and financial services practice in Europe.
Nirmal's passion for software development and project management motivates him to continually hone his skills. He holds a certification in Scrum Master from Scrum Alliance and has completed training seminars in Agile methodologies, Project Management Professional (PMP), and Lean Six Sigma Green Belt, to become a well-rounded professional.
He now works as a freelance software consultant and project manager, helping various clients and companies to improve on their software development processes.
Highlights
Revisiting lightning after coding more than a year in LWC surprised me. LWC is so lightweight, easy to maintain , Highly scalable. just go below the link for firing event from child components to parent in Aura vs creating and dispatching events using LWC. Anyone experienced same? Ditch Lightning please I don't want to take it anymore :) https://lnkd.in/gCfWpWE
Mistakes project leaders and product owners make when the project is in planning stage 1.Negotiation skills are the key. Donot accept anything and everything to what business wants. 2.Do not butcher or gamble with, out of box features over custom ones for silly requirements. Yes I'm calling that silly one example approving requirements that would involve in re-writting code for UI which does same thing like record detail or list views as the OOB application offers. This is why negotiation is important. 3.if some platform offers or had something before don't agree to same look and feel and behaviour in the new implementation. Recommend and write the generic user stories with open mind. This helps the tech team to give best solutioning possible. 4.Don't be so naive to implement an application is not future ready. What if the business wants to go mobile and you end up spending hundreds and thousands of dollars for a desktop application. 5. Most importantly propose a process or Design a process for each and every thing. I'm taking about implementing a process outside regular scrum ceremonies. A process for collecting requirements and writing users stories and get business approval. If there is no process it will be choas. #salesforce
