MARKLANCE INFOTECH PVT LTD’s Post

- Strategic Thinking Over Quick Fixes: Hiring junior developers for testing lacks strategic foresight and hampers long-term growth. - Expert Evaluation: Inexperienced developers assessing complex systems should be replaced with a structured approach where seniors lead testing and therefore mentor juniors. - Structured Development for Growth: Implementing a structured approach empowers juniors, improves code quality, and fosters a pool of skilled engineering managers for organizational growth. Those who know me know that QA holds a special place in my heart. My initial discovery of automated testing changed a struggle to keep pace with customer expectations into a slow, steady march toward success. In all of my successful projects since, automated testing has formed a foundational position in the planning and implementation of projects. It put periodic anchors in place that myself and my teams used to ensure we never moved backwards. This experience has been foundational to how I perceive its use, and how I interact with my colleagues. So, during an online discussion about a software system in trouble and how best to recover it, it was suggested that hiring a junior developer to test the software would offer a quick, cheap win. Since they were cheap, hiring a junior developer would be better than nothing and offer some assurance. I think this is a disastrous solution: quality should not be judged by the apprentice but by the master. The suggestion demonstrates a lack of strategic thinking, and is likely the type of thinking that likely got the organization into trouble in the first place. Instead, a more future-oriented strategy, focussed on organizational growth, is in order. I have both seen and experienced cases where poorly written, shallow testing resulted in a false sense of security: it was a net negative, even though it was a large volume. A lot of activity (testing) was being done by unqualified individuals; because there was a lot of testing happening, everyone felt it was well tested. These aren’t the same thing. ... read more https://lnkd.in/gKtVy9Ky ... In all cases I have seen, the organization suffered from an inversion of the apprentice/master relationship: apprentices evaluating masters. We correct the relationship by having seniors write tests while juniors write code. This corrects the relationship: teachers test students, experts judge the work of novices, and masters evaluate apprentices, not the other way around. ... read more https://lnkd.in/gKtVy9Ky ... Testing offers a solid foundation to pivot that strategy around, but that strategy must be focused on the future stability and growth of the organization.

🤔 Ever wondered why it's so challenging to teach quality to developers? In a thought-provoking blog post by Jeremie 🎭 Fleurant titled "Why it’s difficult to teach Quality to Developers", the important role of Quality Assurance in software development is thoroughly explored. Quality isn't just one part of creating software—it's essential for making a product successful. One of the core challenges highlighted in the article is redefining what it means for a development task to be 'complete'. Is coding up to the point where the program merely functions on a developer's machine enough? Absolutely not. A 'done' job should encompass rigorous testing scenarios, code refactoring for enhanced efficiency and maintainability, and adequate automation tests to guarantee consistent performance. The article emphasizes the need for developers to change their approach to new tasks. It’s not just about moving a ticket from 'backlog' to 'in progress'. Developers should question the purpose of the task, plan necessary tests, and consider its impact on different platforms. Often, rushing these tasks leads to missed details and features that don’t work as intended. Furthermore, the article highlights how developers often ignore or dismiss bugs that aren't directly related to their current tasks. Yet, paying close attention to and proactively fixing even small issues can greatly improve the overall quality of the final product. The concept of Quality Assistance offers a compelling solution. It encourages developers to actively focus on quality, integrating QA throughout the development process and enabling them to take responsibility for maintaining high standards. Considering this, how can we build a culture where quality is central to everything we create? It starts with reevaluating how we handle development tasks, deeply engaging with our work, and always aiming to get better. More about it: https://lnkd.in/dXvMHUJp #qualityassurance #softwaretesting #webdevelopment #quality

Empowering Developers: A Journey into Software Testing 🏔 Despite studying Software Engineering, testing wasn't emphasized during my college days. I didn’t write any tests during college, resulting in a 0% test coverage upon graduation. Testing wasn’t part of my curriculum, which seemed normal then but feels surprising now. Testing is crucial in software engineering, a concept I learned about much later. Why Test? Tests ensure your code works "correctly." They're like insurance—investing time in writing and maintaining tests can prevent costly bugs in production. Testing also supports "shift left," identifying and resolving issues early in development. Types of Testing Unit tests examine individual code units, integration tests assess interactions between code pieces, and end-to-end tests cover entire code paths. More tests generally mean more confidence in your system's behavior, but they require time and maintenance. Tests Increase Confidence Writing tests boosts developers' confidence to refactor code. Passing tests guarantee existing system behaviors, allowing safe code modifications. Tests signal problematic changes, motivating developers to keep test suites fast. Writing Tests I realized the importance of testing when a bug surfaced in my last company’s software. Writing a test to reproduce the bug helped identify and fix the issue. Tests serve as documentation, detailing expected code behavior in various scenarios. #SoftwareEngineering #TestingBasics #QualityAssurance #CodeQuality #TestDrivenDevelopment #BugFixing #SoftwareDevelopment #TechEducation #CodingTips #DeveloperSkills #ContinuousIntegration #AutomatedTesting #SoftwareQuality #Debugging #TestAutomation #ProgrammingTips #TechCommunity #LearningJourney #DevelopmentTools #DeveloperResources

Being a Programmer vs. Being a Software Developer! Being just a programmer is totally different from being a software developer! Programming is a crucial part, but it's just a small piece of the software development lifecycle. As your programming experience grows, you'll realize there's much more to it than writing functional code. From gathering business requirements to correctly designing the software architecture within the existing framework, from designing or extending the existing database to ensuring the highest performance, scalability, and maintainability, writing code using clean code principles that align with your company's coding style—which varies from company to company—is just the beginning. Next, Code testing at least unit testing but with proper code coverage is a must, and I highly recommend using TDD 💪 . Testing is bigger than unit testing but it's the responsibility of QAs (testers) to do the next steps of Testing to guarantee smooth software integration. A software developer must also be familiar with the deployment technology stack and the steps needed to deploy code within the CI/CD process across different servers seamlessly. In my opinion, communication skills are among the most crucial skills for a software developer. Throughout the process—from design to deployment—interaction with many people inside and outside your team is inevitable. Learning to handle these interactions professionally and enthusiastically is key to moving tasks forward efficiently. Knowing when to ask for help and when to offer it to keep the team's tasks progressing is equally important. A Junior software developer focuses only on their task and might not see beyond their current assignment. In contrast, a senior software developer understands the goals of the current release or sprint, knowing how their task and others fit into the bigger business objectives. They might even have a broad understanding of the team's goals for the next three months at least! Over time, it becomes clear that as a software developer, you frequently interact with the business side, QAs(testers), scrum master, managers, DevOps teams, developers, and stakeholders. Non-functional tasks like performance improvements and automating repetitive tasks to ease the team’s workload are also vital. Code reviews of colleagues' work are a daily routine, providing opportunities to assist others and learn from their way of thinking to write their code. Despite all this, some say AI can replace software developers! AI is a tool that can assist developers, but as we've shown, software development is much, Software is Life is an Environment that needs humans to interact professionally and understand the business needs as humans to generate a great piece of software.

𝗛𝗼𝘄 𝗧𝗼 𝗕𝗲𝗰𝗼𝗺𝗲 𝗔 𝗚𝗿𝗲𝗮𝘁 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿? As we all know, being a software engineer is not easy. You need to see a lot and constantly improve yourself. But, what differs excellent software engineers, and here are recommendations on how to become one: 𝟭. 𝗠𝗮𝘀𝘁𝗲𝗿 𝗼𝗻𝗲 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲 𝗶𝗻 𝗱𝗲𝗽𝘁𝗵 Take one programming language and go in-depth with it. Learn everything you can and be a master of it. Some good languages you can select today are JavasScript, Python, Java, C#, and Rust, ... 𝟮. 𝗟𝗲𝗮𝗿𝗻 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗰𝗼𝗻𝗰𝗲𝗽𝘁𝘀 When you master a programming language, its syntax, semantics, and constructs, the next thing is to learn different software engineering concepts, such as: - Software architecture - Software design - Design patterns - Clean code - SOLID, DRY, KISS, and YAGNI principles 𝟯. 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗦𝗗𝗟𝗖 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 Understand the complete software development process, from requirements to deployment. Learn about Agile methodologies, DevOps, and Quality assurance. Try to work on different projects; the more projects you work on, the more you will learn new stuff and grow. 𝟰. 𝗕𝗲 𝗮 𝗽𝗿𝗼𝗱𝘂𝗰𝘁-𝗺𝗶𝗻𝗱𝗲𝗱 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 Don't settle just for specs; jump to implementation when working on your project. Think about other ideas and approach your product manager with them. Try to understand the complete system and how the business works. Be an end-to-end product feature owner. 𝟱. 𝗜𝗺𝗽𝗿𝗼𝘃𝗲 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝘀𝗼𝗳𝘁-𝘀𝗸𝗶𝗹𝗹𝘀 Be respectful of others, communicate clearly, and be humble. Being kind has no financial cost, but its effects are immeasurable. Try pair/mob programming. Talk with people outside engineering, grab a coffee or lunch, or do a hallway chat. 𝟲. 𝗟𝗲𝗮𝗿𝗻 𝗶𝗻𝘁𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹𝗹𝘆 We need to learn, but the trick is when and how. Don't just learn things; this is inefficient. We need to learn intentionally, just before we need it, and this will make the most significant impact. 𝟳. 𝗪𝗼𝗿𝗸 𝘄𝗶𝘁𝗵 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗺𝗼𝗿𝗲 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲𝗱 The fastest way to progress in your career is to find a mentor. He can help you find your gaps and show you some new opportunities. A mentor can be found inside an organization or outside. 𝟴. 𝗨𝘀𝗲 𝗴𝗼𝗼𝗱 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 Learn and follow good practices, such as: - Using version control - Write your tests correctly - Learn how to refactor - Learn TDD - Code reviews - DevOps mindset Also, learn your IDE and all the essential shortcuts you need. Debugger too. #career #software_engineering #mindset #dev_ops #career_couseling #software_architecture #system_design #devsinc #IT

𝐂𝐨𝐦𝐦𝐨𝐧 𝐌𝐲𝐭𝐡𝐬 𝐕𝐬 𝐑𝐞𝐚𝐥𝐢𝐭𝐲 𝐢𝐧 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠 When I first started as a Software Engineer, I had a lot of misconceptions about the field. Over time, I realized that many of these "myths" were far from reality. Let’s list down some common myths I’ve encountered. ❌ 𝐌𝐲𝐭𝐡 - 𝐘𝐨𝐮 𝐍𝐞𝐞𝐝 𝐭𝐨 𝐊𝐧𝐨𝐰 𝐄𝐯𝐞𝐫𝐲𝐭𝐡𝐢𝐧𝐠 𝐭𝐨 𝐛𝐞 𝐚 𝐆𝐨𝐨𝐝 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫 I used to feel overwhelmed by all the programming languages and frameworks. I needed to master them all to be "good enough." ✔️ Reality - You don’t need to know everything! Focus on building strong fundamentals in problem-solving and a few key technologies. ❌ 𝐌𝐲𝐭𝐡 - 𝐘𝐨𝐮 𝐌𝐮𝐬𝐭 𝐇𝐚𝐯𝐞 𝐚 𝐂𝐨𝐦𝐩𝐮𝐭𝐞𝐫 𝐒𝐜𝐢𝐞𝐧𝐜𝐞 𝐃𝐞𝐠𝐫𝐞𝐞 𝐭𝐨 𝐆𝐞𝐭 𝐚 𝐉𝐨𝐛 I remember meeting engineers from all kinds of backgrounds—some had business degrees, others were self-taught.  ✔️ Reality - While a CS degree can help, many companies value skills and experience over degrees. Build projects, contribute to open-source, and show what you can do. ❌ 𝐌𝐲𝐭𝐡 - 𝐂𝐨𝐝𝐢𝐧𝐠 𝐢𝐬 𝐀𝐥𝐥 𝐘𝐨𝐮 𝐍𝐞𝐞𝐝 𝐭𝐨 𝐃𝐨. Early on, I believed that coding was the only thing I’d be doing as a software engineer. ✔️ Reality - Coding is important, but communication, problem-solving, and teamwork are just as crucial. You’ll spend time debugging, designing systems, and collaborating with others. ❌ 𝐌𝐲𝐭𝐡 - 𝐁𝐮𝐠𝐬 𝐌𝐞𝐚𝐧 𝐘𝐨𝐮’𝐫𝐞 𝐚 𝐁𝐚𝐝 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫. I used to feel defeated every time I encountered bugs in my code. It felt like a sign that I wasn’t good enough. ✔️ Reality - Bugs are part of the process! Every developer faces them, and solving bugs is a great way to improve your skills. ❌ 𝐌𝐲𝐭𝐡 - 𝐘𝐨𝐮 𝐇𝐚𝐯𝐞 𝐭𝐨 𝐖𝐨𝐫𝐤 𝐋𝐨𝐧𝐠 𝐇𝐨𝐮𝐫𝐬 𝐭𝐨 𝐒𝐮𝐜𝐜𝐞𝐞𝐝 I once believed that pulling late nights and working weekends was the only way to prove myself as a dedicated developer. ✔️ Reality - Productivity is about working smart, not just working long hours. Taking breaks, managing your time well, and maintaining a healthy work-life balance are essential ❌ 𝐌𝐲𝐭𝐡 - 𝐎𝐧𝐥𝐲 𝐒𝐞𝐧𝐢𝐨𝐫 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐂𝐚𝐧 𝐌𝐚𝐤𝐞 𝐁𝐢𝐠 𝐂𝐨𝐧𝐭𝐫𝐢𝐛𝐮𝐭𝐢𝐨𝐧𝐬 As a junior engineer, I thought I couldn’t make a real impact until I reached a senior level. ✔️ Reality - Junior engineers can absolutely make valuable contributions! Fresh perspectives often lead to creative solutions, and companies appreciate team members who show initiative Follow Gourav Roy for more such amazing content 💚 𝐈𝐟 𝐲𝐨𝐮 𝐰𝐚𝐧𝐭 𝐭𝐨 𝐤𝐧𝐨𝐰 𝐦𝐨𝐫𝐞 𝐚𝐛𝐨𝐮𝐭 𝐃𝐒𝐀, 𝐒𝐲𝐬𝐭𝐞𝐦 𝐃𝐞𝐬𝐢𝐠𝐧 𝐚𝐧𝐝 𝐅𝐫𝐨𝐧𝐭-𝐞𝐧𝐝 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰𝐬, 𝐆𝐞𝐭 𝐲𝐨𝐮𝐫 𝐑𝐞𝐬𝐮𝐦𝐞 𝐑𝐞𝐯𝐢𝐞𝐰𝐞𝐝, 𝐆𝐢𝐯𝐞 𝐚 𝐌𝐨𝐜𝐤 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰, 𝐟𝐞𝐞𝐥 𝐟𝐫𝐞𝐞 𝐭𝐨 𝐂𝐨𝐧𝐧𝐞𝐜𝐭 𝐰𝐢𝐭𝐡 𝐦𝐞 𝐡𝐞𝐫𝐞 : 👨💻 𝐂𝐨𝐧𝐧𝐞𝐜𝐭 𝐨𝐧 𝐭𝐨𝐩𝐦𝐚𝐭𝐞.𝐢𝐨 - https://lnkd.in/gyGxA7ut #softwareengineering #myths #reality #networking #connections

Starting a software project can be exciting, but it can also get chaotic without a proper plan. If you’re just beginning, or even if you’ve been at it for a while, setting up a solid structure is crucial to long-term success. Whether it’s a solo effort or a team project, here’s a practical guide to help you get started on the right foot. 1. Define Project Scope: Clearly outline objectives and features before starting. 2. Choose the Tech Stack: Select tools based on your team’s skills and project needs. 3. Organize Your Project Structure: Maintain clear folder hierarchies for backend (controllers, services, repositories) and frontend (components, services). /src /main /java/com/projectname/ /controller /service /repository /model 4. Version Control with Git: Use Git from day one, with branches for features, fixes, and releases. 5. Set Up CI/CD Pipelines: Automate testing and deployment for continuous integration. 6. Code Quality & Documentation: Follow coding standards, use automated tools, and keep your documentation up to date. 7. Modular Structure or Microservices: Start simple, scale with microservices if needed. 8. Test Early & Often: Incorporate testing from the start, using unit and integration tests. 9. Communication & Collaboration: Regular check-ins and open communication are key to project success. 10. Track Progress: Use project management tools to stay organized and agile. A solid foundation is the key to success. Happy coding! 💻 #Tips #Project #freshers #ideas #guide #developer #professional

🚀We're launching our fully practical <Manual Testing> course designed for beginners. For attending to the course, you need to pass ‘Selection of participants’ phase. 👫 Selection of participants The course is designed for beginners who have an analytical mindset with at least an intermediate English level and are hardworking. Participants are selected during 2 steps ․․․ 1. The participant fills the application, which is reviewed by QWALLITY team 2. We hold a Zoom call with the participant selected in the 1st step, during which he/she will pass a small test 📃 Course Agenda Our training program was developed based on the required QA skills and tools used in different IT companies. We offer theoretical/practical knowledge, knowledge of toolkit, real software testing, team workshops and interview preparation. Lesson_1: Fundamental of Testing Lesson_2: Testing during Software Development Life Cycle Lesson_3: Defect Management Process/Testing Documentation Lesson_4: Test Case Development Lesson_5: Bug Report in Jira and Test Case design in Zephyr Scale Lesson_6: Static Testing Technique Lesson_7: Dynamic Testing Technique - Black Box Lesson_8: Dynamic Testing Technique - White Box Lesson_9: Test Estimation, Agile methodology (Scrum/Kanban) Lesson_10-12: Database Testing (SQL) Lesson_13: Web Development Basics Lesson_14: Client-Server Overview (TCP/IP Model), FrontEnd/BackEnd Lesson_15-16: API testing with Postman Lesson_17: Workshop - API Testing Lesson_18: Performance testing with JMeter Lesson_19: Configuration Testing Lesson_20: CI/CD with Azure DevOps, OS Basics Lesson_21: Version Control System(Git/GitHub) Lesson_22: Mobile Testing(Android & IOS) Lesson_23: Root Cause Analysis, Final Assessment Lesson_24: Understanding AI Basics, Types, and Testing Techniques Lesson_25: QA/HR interview preparation 🕞 Course Duration: 25 lessons/60 hours All participants will be awarded certificates after course. ✅ Required information Start date: September 17 Course duration: 3 months Lesson duration: 2-2,5 hours Days and hours: Tuesday(7:30PM) and Friday(7:30PM) Number of participants: Up to 14 people Your investment: 45,000 AMD for each month Trainer: Ani Movsisyan ®Registration Form: https://lnkd.in/gmMSrSpQ ☎️Contact us: 041 404 201 Linkedin` https://lnkd.in/dFyQbvZ FB` https://lnkd.in/d7GF57g Insta` https://lnkd.in/eXdBbw8h

It's been 9 years since I started practicing TDD. It started when I was interviewed for Thoughtworks where my interviewer wrote a test and asked me to fix it. At that point of time, I didn't even know what software testing was. I always used to test the behavior by writing console logs, system prints, etc.., so, I liked the idea of having an automated test verifying the behavior. Yet, I didn't understand the difference between writing tests before or after the implementation, but I know for sure that tests are a great thing for developer productivity and software quality. Now, I can confidently say that there is a huge difference in software quality when we write tests before implementation instead of writing them after the implementation (I am assuming that writing tests is anyway mandatory, not for the sake of it, but for our own peace of mind. So it's only a matter of writing them first or last). Test Driven Development is a great technique that helps us think about business requirements, keeps us focused on what is important and gives an opportunity/reminder to refactor the code by encouraging us to write test first. Keeping my experiences in mind and the difficulties that I came across while helping others practice, I created a short course on how to approach software development using TDD and also discussed some of the frequently asked questions (planning to add more). It is available in Udemy and you can take the course for free using the link below and it is really short, around 1 hour 45 minutes. I hope you like it. If you have any feedback, I am more than happy to discuss and improve the course :) Thanks to my team at OTTO who believed in TDD and gave me input on curating the course. PS: Link: https://lnkd.in/evcjpwCV Somehow the link is not updating, the previous coupon is expired. Please use this coupon code in Udemy 83B8EAE85FEC6E64F147 #tdd #testdrivendevelopment #xp

#𝐃𝐞𝐯𝐎𝐩𝐬 𝐏𝐨𝐬𝐭𝟏 : 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐭𝐡𝐞 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 𝐋𝐢𝐟𝐞 𝐂𝐲𝐜𝐥𝐞? Before knowing DevOps, first, we will know what is SDLC & Its Phases. 𝙒𝙝𝙖𝙩 𝙞𝙨 𝙖 𝙎𝙤𝙛𝙩𝙬𝙖𝙧𝙚 𝘿𝙚𝙫𝙚𝙡𝙤𝙥𝙢𝙚𝙣𝙩? Software development is a process of designing, developing, testing, and maintaining computer programs & applications. It plays a vital role in our daily lives because we are using the software in the mobiles which eases our tasks. The #software is developed by software engineers or developers who should have good programming knowledge & complex problem-solving skills. 𝙒𝙝𝙖𝙩 𝙞𝙨 𝙎𝙤𝙛𝙩𝙬𝙖𝙧𝙚 𝘿𝙚𝙫𝙚𝙡𝙤𝙥𝙢𝙚𝙣𝙩 𝙇𝙞𝙛𝙚 𝘾𝙮𝙘𝙡𝙚? A Software Development Lifecycle is an organized way to develop software after following certain processes such as planning, designing, developing & testing. Software Development Life Cycle is Known as “SDLC” also. With the help of SDLC, you can easily describe how you are going to create a software product & what you do in every phase of the software development life cycle. 𝙎𝘿𝙇𝘾 𝙛𝙤𝙡𝙡𝙤𝙬𝙨 𝙩𝙝𝙚𝙨𝙚 𝙨𝙚𝙫𝙚𝙣 𝙥𝙝𝙖𝙨𝙚𝙨: 𝟭. 𝗥𝗲𝗾𝘂𝗶𝗿𝗲𝗺𝗲𝗻𝘁: In the first phase of SDLC, the team broadly discusses & collects all the requirements in detail with clients & understands what the client wants from them in terms of software product creation. 𝟮. 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴: After collecting all the requirements from the clients after a broad discussion, the team started planning what is needed to create software in terms of designing, developing, testing, and maintenance. It means how to design a frontend & develop the backend and which language, framework, or testing tools they are going to use for the software product. The team also focuses on how they can minimize the cost & deliver the project timely, which benefits both the clients & company. 𝟯. 𝗗𝗲𝘀𝗶𝗴𝗻: The front-end or designing team starts designing the website frontend by using languages such as HTML & CSS to make the UI/UX attractive to the users. 𝟰. 𝗗𝗲𝘃𝗲𝗹𝗼𝗽: The programming team starts developing the backend using languages such as Python, Java, PHP, or Ruby. 𝟱. 𝗧𝗲𝘀𝘁𝗶𝗻𝗴: When the designing and development team completes the process, the testing team starts testing the code. If any bug is found, the testing team reports to the programming team. 𝟲. 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁: First, the development team deploys the software on the dev/test environment and shows the software product to the client. If the client is satisfied, the team will deploy the software online in the production environment. 𝟳. 𝗠𝗮𝗶𝗻𝘁𝗲𝗻𝗮𝗻𝗰𝗲: If a sudden bug comes to the live software, the development team has a responsibility to fix the bug in the live environment. SDLC follows various models (such as Waterfall, Agile, etc.) to create a software product. In the next post, we will start discussing several SDLC models based on above mentioned phases.