Kübra Duanur MUSLU’s Post

which method do you prefer?🤣

Which methodology do you prefer? 😅

🚨 New Video Alert! 🚨 Are you unknowingly breaking the ‘S’ in SOLID principles? Let’s dive deep into the Single Responsibility Principle with practical .NET examples. Don’t miss out! 👉 https://lnkd.in/dtpJjhqY #SOLIDPrinciples #DotNET #CleanCode #DesignPatterns #SRP

Our instructor, Vasilis Kallaras, will talk about "Performance Max Τweaks & Ηacks Υou Νeed" During this session, we are going to discuss: - Why zombie scripts are critical for your products - How to split strategies - What are the essential insights to monitor in Performance Max

**Taming the Storm: How Chaotic Exploration Shapes Big Picture Event Storming** This is what you have been waiting for :) Having delved into the intricacies of event storming, its various types, and effective workshop facilitation, it’s now time to embark on our first practical example. #CodeCraftsmanship #EventStorming

Check out our new video: 📹 Learn All About TestRail’s Project Types! 🛠️. Watch it here: https://lnkd.in/eWi7H2Bp this video, you will learn all about TestRail’s different project types. 🎓 As discussed in the other videos, projects are an important aspect of TestRail. 📂 Whenever you add a new project in TestRail, you can always choose between three different project types: 1️⃣ A single repository for all cases 2️⃣ A single repository with baseline support 3️⃣ Multiple test suites The type of project you use will define how you organize and manage your test cases within t... Link: https://lnkd.in/eTivu2JV powered by GVKN

We’re not about delivering test results and leaving. The CTL extra mile means working with you to ensure you understand the results of your test and the next best steps for your organization to take. #ChicagoTestingLab #TestingExcellence #ClientSupport #RoadConstruction

Have you ever implemented a genius creative idea only to see performance flop? Here are some tips you should keep in mind when creative testing!

Fantastic presentation by Dave Thomas at the GOTO conference. A few highlights: 1. Dave's superpower is associative memory. 2. Dave details the history of software dev and how folks came up with rules to help build better software, be it classifying them into different systems, all the way to TDD, Agile and beyond. 3. Dave then goes on to highlight that all these rules were created to help write perfect code, he contends that perfection is an incorrect goal to aim for. He cites a study which shows that requirements change at the rate of 2% per month or 25% per year. Hence a solution will never be perfect, especially as the goalpost is constantly moving. 4. But Dave does not stop with the negative contention that one ought not to aim for perfection. He ties it all in, and give us the one rule to rule all the rules from points, 2 & 3. He proposes that all the above rules were designed to do one thing, which was to make code easier to change and maintain. It is a wonderful way to look at how to create a solution, that designing with extensibility and maintainability in mind should be the goal. I could not agree more. Check the presentation out at : https://lnkd.in/gHetrqfE

View my verified achievement from Section.