Let's discuss Development Methodologies like DevOps, agile, BDD, FDD etc.
- 11 Topics
- 29 Replies
The topic of "Feature Flags and Feature Toggles: A Strategy for Controlled Rollouts" is a valuable discussion point for developers interested in optimizing their release processes. What are Feature Flags and Toggles Feature flags (also known as feature toggles) are a development technique that allows you to turn specific features or parts of your application on or off at runtime. They are essentially conditional statements in your code that determine whether a particular feature should be visible or active for end-users. This enables developers to have granular control over feature releases and updates.Do you use features flags?What is your experience with them?Any benefits/drawbacks that you want to share?
Some time ago about what is SAST and DAST emerged in one of the community threads which inspired me to write this short article explaining the difference between SAST, DAST, IAST and RASP using a clever analogy.Before we start explaining the terms, try to imagine yourself as a castellan who is concerned about protecting his castle (your computer system) from the savage raiders (cyber threats).Our application is like a castle we have to protect SAST - Static Application Security TestingNaturally, you would want to prevent most of the issues when the castle is not yet built. I mean, it's much easier to change the design of a certain wall before it is built rather than after it's already standing. And how to spot the potential issues? By carefully examining the blueprints and looking for the issues. This is when SAST (Static Application Security Testing) comes into play. When looking for flaws using SAST, the castellan should ask himself questions such as: "Do the walls have the right thi
Demystifying Saga Design Pattern in C#: A Cure for Distributed Transactional WoesIn the world of distributed systems, managing transactions across different services can often pose a significant challenge. Traditional approaches like the 2-Phase commit and 3-Phase commit patterns have been reliable companions in monolithic applications, yet they fall short when it comes to modern, distributed environments. This article explores the Saga Design Pattern, a powerful approach that addresses these issues in a distributed setting. We will delve into its definition, types, and the concept of compensation, illustrated with a real-world e-commerce platform example. The Problem at HandWhen it comes to transactions in a monolithic architecture, the typical approach is the ACID (Atomicity, Consistency, Isolation, Durability) model, with distributed transactions implemented via the 2-Phase or 3-Phase commit patterns. However, these models run into scalability and performance issues in distributed s
Are you really using Agile in your Projects? A lot of projects/teams claim to work in an Agile ways. They use methodologies and ceremonies that are tipically associated with Agile and with Scrum. However in reality it is actually a Sprint based Waterfall. Share your experience. What do you use.
Test-Driven Development (TDD) vs. Behavior-Driven Development (BDD): Which Approach do you use in your Project?
Test-Driven Development (TDD) and Behavior-Driven Development (BDD) are two popular approaches to software development that prioritize testing and quality assurance. TDD focuses on writing tests before writing codeBDD focuses on defining the behavior of the system before writing code. Which one do you use? Do you use either, or a third one?
In the world of testing, oh what a sight,There are development methodologies left and right!Waterfall, Agile, DevOps, and more,Each with its own unique score. Waterfall's like a river, flowing down,Each phase completed before the next comes 'round.Design, coding, testing, all in a row,In the end, a product that's good to go. Agile's more like a jungle, wild and free,With sprints and stand-ups, and lots of team camaraderie.Iterations and feedback, they all do their part,To create a product that's work of art. DevOps is like a machine, moving fast,Continuous integration, deployment, and testing that lasts.Automation's the key, with pipelines in play,To deliver software every single day. But which one's the best, you may ask,Well, that depends on the testing task.Each has its own strengths and flaws,So pick the one that suits your cause. In the world of testing, there's no one size fits all,So experiment and find the right call.And when you've found the right way to test,Your product will
Lean Software Development is an agile software development methodology that focuses on reducing waste and maximizing value delivery to customers. It is based on the principles of the Toyota Production System and emphasizes continuous improvement, teamwork, and customer focus.In Lean Software Development, testing is an integral part of the development process. Testing is not considered a separate phase but is instead integrated throughout the development cycle. This is because Lean Software Development emphasizes the need for continuous feedback and continuous improvement, which can only be achieved through continuous testing.Testing in Lean Software Development is carried out in various forms, including unit testing, acceptance testing, and exploratory testing. Test automation is also an essential component of Lean Software Development, as it helps to reduce waste and improve efficiency. Automated testing helps to detect defects early in the development process, which reduces the cost
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.