Checkly’s Post

I’ve not run into this specific issue with the clients I work with. Two of the points I want to emphasize that you made is communication and testing. Communicate early and often. Let them know where we are within the process and give them access to start testing as soon as possible. We have two testing environments that our code goes through before prod deployment. I have the stakeholder group begin testing as soon as it gets into the UAT environment. We can make changes there after we get feedback from them. Great video and explanation how you handle a difficult situation with a client.

"Your release was on yesterday, right?", my mother asked. My parents, being farmers, don't really understand what exactly I do. 🥲 BUT I relate my work to theirs and have educated them well on the basics like release, testing, development, rollback, etc. 😀 Now, they understand at least the basics when I discuss something with them. 🙌 #EducateParents #Educate #EducateToEmpower #ParentsAtWork #ParentSupport

Where do we draw the line between pre-release and post-release testing in actuality? For instance, certain video game companies are notorious for using their customers as guinea pigs for pre-release testing after the release, making the game almost entirely unplayable. This is primarily due to tight release schedules and corporate demands. In my experience as a tester, I have had to repeat tests numerous times before and after the release. The catch is that we did our best to make the pre-release the best we could, even though that sometimes caused some delays. My point is that pre-release testing should never creep become post-release testing. If it does, then something was missed, and the company could lose a lot of business and profits. #SoftwareTesting

What if I did not get what I wanted developing a software product? Sometimes clients come to us to rework what they have been doing somewhere else. More than once it has even been like that - it would have been funny if were not so sad. We quote them for the development, they say it’s expensive, go to a cheaper provider, and then come back after half a year or a year, saying they got something wrong. How to avoid that? And what to do if already done? #softwaredevelopment #changemanagement #projectmanagement #requirementsclarification #requirementsdocumentation #testing #videoblogaboutvideosoftware 

What if I did not get what I wanted developing a software product? Sometimes clients come to us to rework what they have been doing somewhere else. More than once it has even been like that - it would have been funny if were not so sad. We quote them for the development, they say it’s expensive, go to a cheaper provider, and then come back after half a year or a year, saying they got something wrong. How to avoid that? And what to do if already done? #softwaredevelopment #changemanagement #projectmanagement #requirementsclarification #requirementsdocumentation #testing #videoblogaboutvideosoftware 

Continuous quality is to apps what popcorn is to the perfect movie: the SDLC just doesn't work without it. So, what is continuous quality, anyways? Find out here: https://lnkd.in/evSBt-sr

What if I did not get what I wanted developing a software product? Sometimes clients come to us to rework what they have been doing somewhere else. More than once it has even been like that - it would have been funny if were not so sad. We quote them for the development, they say it’s expensive, go to a cheaper provider, and then come back after half a year or a year, saying they got something wrong. How to avoid that? And what to do if already done? #softwaredevelopment #changemanagement #projectmanagement #requirementsclarification #requirementsdocumentation #testing #videoblogaboutvideosoftware 

There's always a lot of discussion about not deploying on a Friday... But rarely do I see discussion of why people want to deploy on a Friday to begin with. In my experience, a lot of the time it's because the development workflow is less than ideal, and a deploy is the easiest path to continue work. This is especially true for feature sets that cross service boundaries. People often have to make a change in multiple places, but often are missing a good developer experience to test end-to-end... And so they want to deploy on a Friday to keep working.

Do you have a system of delivery or a Rube Goldberg machine? System of delivery: git commit && git push ⇒ runs tests, if they pass, deploys to prod Everything significantly more complicated than that is possibly a Rube Goldberg machine. #XP #ContinuousDelivery

🚨 Version Control Chaos 🚨 We've all been there – working on separate branches, feeling confident about the next big release, when suddenly... CHAOS ensues! 🤯 Managing branches in version control can sometimes feel like juggling fire. 🔥 One moment you're pushing your clean, isolated code changes, and the next moment, you're untangling a web of merge conflicts! Whether it’s navigating through rebase or trying to prevent a production mishap, version control can be a wild ride. 🚀 But amidst all the chaos, it’s also what makes collaboration possible. That’s the beauty of Git! ❤️ It teaches us to work smarter, document better, and occasionally remember to double-check before hitting that merge button. How do you handle version control chaos? Any tips or stories to share about your "git" battles? Let’s discuss in the comments! 💬 #Git #VersionControl #TechLife #SoftwareDevelopment #MergeConflicts #TechMeme #Collaboration