Ziggy Rafiq | Senior Technical Lead Developer

  Overview Over the past few years working within the Agile Scrum teams I have seen at some places there are not clear with the basic simple terms of Agile scrum definitions and I thought of writing this blog post based around exampling the simple basic terms definitions we use in Agile Scrum terms. Product Owner The primary decision-maker on the scrum team. Scrum Master Leads the meetings and standups, removes roadblocks and oversees the scrum team. User Story A brief explanation of the who, what and why behind a project. Tasks An item that needs to be completed by a scrum team member. Backlog A repository of the project ideas that may be executed in the future. Blockers Anything that is preventing a team member from completing their work. Minim Viable Product (MVP) A base-level project intended to show proof of concepts. Kanban A visual framework for tracking steps in a process that uses columns and status indicators moving from left (beginning ) to ri

via https://youtu.be/uUS2GuNwMbY

  Overview In this blog post, I am going to share with you exactly how I have become a successful Software Consultant and by following these simple rules and why it is important to apply the following in your Web Design, Web Development/Full-Stack Development and Mobile Application Development. There is this famous quote that “I wish he would tell me where I am going to die so that I cannot go there ever” In a nutshell what this means is that most of the times people trying to understand or learn something like how to become successful. I have seen many consultants closed their consultancy or have burned out to a point where they quit consulting and change their career to something else or started to work full-time for somebody else and avoid the consulting role completely because of their fear of failure. Five Fundamental Points There are five fundamental things I have followed to be a successful Consultant   Have a basic systematic way of attracting clients. This is the key

      Overview Agile is a collection of values and principles hence Agile’s the real utility is giving people a common foundation for making decisions about the best way to develop software effectively and to deliver on time. The 12 Principles   of Agile Below are the 12 Principles of Agile, which I feel are very important to follow/apply to any given software production. As delivering cost-effective, bug-free and on-time software is one of the main objectives for any software production cycle.  Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.  Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.  Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.  Business people and developers must work together daily throughout the project.  Build projects around motivated individuals.

  C# Virtual and Non-Virtual Method In Microsoft.net C# Virtual method supports polymorphism, which is part of the OOP Concept. We would combined virtual and override keyword with the virtual keyword on the parent/base class and then use the override keyword on the method in the child/derive class and both methods are virtual. Any methods which do not have virtual or override keyword or that have new keyword are non-virtual method. When a virtual method is invoked on an object, the run-time type of the object is used to determine which implementation of the method to use. When a non-virtual method is invoked on an object the compile-time type of object is used to determine which implementation of the method to use.

  C# Comments Overview C# Comments are only for you to read, not for the computer to execute. All the comments displayed in the Code Editor are green by default, which makes it easy to identify those lines, and the C# compiler ignores those parts when it runs your program. Single-line Comments You can make any line into the single-line comment by starting it with the two forward slash marks //, indicating the remainder of the line is a comment. Example End of line comments The End of line comments is generally used to describe variables and data types. Example Multiline Comments (delimited comments) Multiline Comments begin with an open comment mark /* and end with a lost comment mark */. All the text between the delimiters is ignored by the compiler. Example Code Example Code(Header Comments) XML Comments In C# we use XML comment on our methods by simply typing /// to get the XML comment.

Ziggy Rafiq Blog Overview As a Full Stack Designer, Developer, Tester, and DevOps with over 18 years plus of experience, Ziggy Rafiq has also led teams as a Technical Lead Developer for over 13 years. Ziggy Rafiq’s blog will provide many tips and useful information about Full Stack Design, Development, and Testing, catering to both new professionals and those interested in exploring the field. In Ziggy Rafiq’s blog posts, Ziggy Rafiq will share his journey as a Full Stack designer, developer, and tester and how Ziggy Rafiq stays current with industry changes and best practices. You'll also find code samples from Ziggy Rafiq demo projects and best practices for designing, developing, and testing. Ziggy Rafiq will also discuss the steps necessary to obtain ISO 9001 certification for software organizations. Throughout Ziggy Rafiq’s blog, you will find useful hybrid design and development information, design samples, code samples, and how-tos. Additionally, Ziggy Rafiq will talk about