Software development is not linear, and testing is not a phase. On Thursday, February 22nd: 20:00 UTC, the DORA community of practice will be discussing testing. The discussion will start with a presentation by Lisa Crispin, a DORA Guide and an independent consultant, author and speaker based in Vermont, USA. After Lisa's presentation, we will have a lean coffee discussion with the community. Visit https://dora.community/ , join the Google Group and check the calendar for more DORA related events. #DevOps #Community #DORA #testing #knowledgesharing
DevOps Research and Assessment (DORA)’s Post
More Relevant Posts
-
Code reviews are the heartbeat of robust software development. Join me in a conversation about the crucial role they play in maintaining top-notch code quality. https://lnkd.in/eA9S-3zn Have your own insights into effective code reviews? Share your thoughts in the comments! Connect with me to stay updated on this insightful discussion and more. #CodeReview #SoftwareDevelopment #BestPractices #TechTalk #softwareengineering
To view or add a comment, sign in
-
-
#Dev2Dev Talk : Software engineering tips Starting a project can make you want to focus on the details right away. But remember, the most important thing is how well it works. A software that looks nice but doesn't work well isn't very useful. It's usually functionality first before details!
#Dev2Dev Talk; Functionality First Before Detailing
To view or add a comment, sign in
-
What's the perfect timing between software releases? Is it every quarter, every month, every 2 weeks? It's as short as possible. The less time between releases: - The sooner you can learn whether what you developed is what the users need - The sooner features can deliver value to end users - The lower your surface area for identifying issues - The lower the chance of business needs changing It all boils down to risk. The shorter the time between releases, the lower your risk. #softwaredevelopment #softwareengineering #coding
To view or add a comment, sign in
-
If you are working on a part of large software system, a system that does not fit on a computer. Question for you - how does your team setup development environment? There are so many sub-questions but let’s stick to the local setup for now. Curious to know - reproduction of a bug, is local environment close to production? We have been promised same setup using containers, right? How easy it is to develop a new feature, how big is your team. If we have enough responses we can have video session to discuss more. #software #development #localdevelopment #containers #devops
To view or add a comment, sign in
-
In the fast-paced world of software development, testing teams face numerous hurdles. But what’s the #1 challenge for you? Cast your vote below! 👇 Time: Racing against the clock to meet those crucial deadlines. ⏰ Tech: Keeping up with the latest technology trends. 🖥️ Balance: Striking the perfect mix between depth and speed in testing. ⚖️ Share your thoughts and experiences in the comments! #QualityAssurance #DevOps #AgileTesting #TechTalk
To view or add a comment, sign in
-
This is by far the most important rule in software engineering. When functions do more than one thing, they are harder to compose, test, and reason about. When you can isolate a function to just one action, it can be refactored easily and your code will read much cleaner. If you take nothing else away from this guide other than this, you'll be ahead of many developers. #awoyemivictor #softwareengineer
To view or add a comment, sign in
-
-
As software engineers, we often encounter Software Entropy 👾 - the gradual deterioration of system quality over time. Just like physical systems tend towards disorder, software systems can accumulate complexity, bugs, and technical debt if not actively maintained. Drawing parallels with the Broken Window Theory, which suggests that visible signs of disorder can lead to further degradation, we understand the importance of not leaving "broken windows" - bad designs, wrong decisions, or poor code - unrepaired. It's crucial to fix each one as soon as it is discovered. If there is insufficient time to fix it properly, then managing it right becomes necessary to prevent further damage and demonstrates proactive management of the situation. ⚠️ What if we don't care? Neglected codebases not only become harder to understand and maintain but also hinder productivity and innovation. 🚀 💡 The Solution? Small and Steady Refactoring! By continuously improving code quality through incremental refactoring, we can prevent the buildup of entropy and maintain a healthy, sustainable codebase. This approach allows us to address issues early on, keeping the codebase clean, efficient, and resilient. ✅ Benefits of Refactoring: - Enhanced Readability: Clean code is easier to understand, reducing the time needed for onboarding and maintenance. - Reduced Technical Debt: Addressing small issues promptly prevents them from snowballing into major problems down the line. - Facilitates Innovation: A well-maintained codebase fosters experimentation and the implementation of new features with confidence. Let's fight the software entropy and uphold the integrity of our codebases. #SoftwareDevelopment #Refactoring #CleanCode #SoftwareEntropy #BrokenWindow
To view or add a comment, sign in
-
-
Software dev teams need to start learning how to do proper vertical slicing of user stories.
modern software development I count software development as passing (oops, not "paying") the modernity test if (and only if) many/most functionality changes to the software go from "end customer" request to "end customer" use in less than a day with no new bugs. Can't do that? Your software code / system / team /process hasn't made it to the 2010s. 2 weeks? you're not in the 2000s. the future is here... its just unevenly distributed. is that a fair model? do my other craftsmanship/devops folks think similarly?
To view or add a comment, sign in
-
Finally, this is the fifth and final instalment of my article series on Modern Software Engineering covering Continuous Evolution. This article includes a story I haven't told a lot of people on how closely involved I was in the Friendster outage of November 2008, one which ultimately damaged the brand due to a bug involving integer conversion in C++ -- it turns out, folks don't like it when the service comes up and they seemed to have lost friends and/or gained random friends. This also ties together the first four parts and discusses how modern software engineering's goal is the continuous evolution of a product especially those that follow the SaaS model. Here's my request: what would you like me to write about next time? I have a list of things I'd like to write about, but I'd also love to hear your suggestions! Thanks in advance for reading. :) #softwareengineering #ai #devops #agile #cicd
To view or add a comment, sign in
-
#platformengineering provides independence for developers, but it can also become burdensome if cultural change is not managed correctly. Read this week's post to learn how to do it right 👇 https://lnkd.in/dRR4dm2a Keep #DevEx #developerexperience #devops #alerts
Swift Roundup #13: Avoiding Overload as Developer Ownership Increases.
senora.beehiiv.com
To view or add a comment, sign in
Ich helfe IT-Abteilungen, 10x produktiver zu werden, durch Beratung auf Management- und Teamebene.
4mo„Testing is not a phase“ - Thank you for this!