DevOps uses Agile principles and combines infrastructure, development, QA, and operations engineers together through the entire cycle of software development, deployment, and support, eliminating many of the silos between teams. Most importantly, DevOps improves communication and enables better collaboration, helping enterprises to bring products and innovation to market much more rapidly.
Business-driven development (BDD) is a methodology in which business decisions and requirements drive an IT solution. Without adequate business needs identified, development cannot begin. Business-driven digital transformation is taking this a step further and having a company embrace a larger change, and therefore improve from it. The scale of digital transformation is of a larger magnitude, and it relies on buy-in of all business folks, as well as the IT department.
Depending on what version of TFS you intend to migrate and what features you are using, there are a few things that in my opinion are “major” considerations because they have the potential of adding scope to your migration efforts. While you will find out about them as you read through the official migration guide, I believe there is value to knowing these things prior to embarking in such journey.
I was recently working with one of my customers to help them improve the usability of their applications as mandated by their IT staff. The goal was to create quality web applications that can be equally useful to all users including those with disabilities. Together, we reviewed many good tools and potential best practices, but we wanted something that would specifically run as part of the application release process.
What I wanted to accomplish here was simply to create a redistributable Python package. Also show some of the practices on how to work with Python in a Windows environment, but I could not stop there.
I went ahead and built a complete CI/CD pipeline for the package, showing how easy it is and how well Python projects integrate with Azure DevOps.
This article is part 2 of DevOps and Culture. See part 1 here. In this entry I’ll discuss how we can think of culture in a systematic way and how we can change it.
Peter Drucker famously said, “Culture eats strategy for breakfast.” This is a great introduction to how we think about DevOps and in this article, I’m going to unpack this statement so that we have a bit more context. This is the first part of multiple articles on culture as it relates to DevOps.
Build a Boot web project, create a Dockerfile, build a Docker image, then run it in Docker.
VS Code can really be the platform of choice to benefit from the best features. Furthermore, its cross platform support allow users to have the same customer experience on multiple platforms (Windows, Linux and Mac OS).
Why is it that some organizations, though they may invest great expense in tools, process development, and rigor, fail to obtain the transformation and benefits other organizations have so greatly experienced?