Things with code

For several years now, DevOps has been one of the hype words, due to the desire to run development and operations of company software with more efficiency and predictability. This often takes the form of dumping operators into a development team and subsequently declaring it 'done'.  Of course, nothing could be further from the truth. What is DevOps So, this is a tricky one. In its most basic form, it's just the contraction of Development and Operations, but the more important idea is that there is a fluent integration between both disciplines. Developers who understand operations and take that knowledge into account when building software, operators understanding software and influencing how it is made and deployed. We've been here before In a way, DevOps is nothing new in the world of software development. We used to have other roles that were formally separated back in the dark ages of waterfall style software development. Information analysts, functional designer, p

One of the big improvements that came with NuGet is the ability to easily work with third party libraries and, because of proper versioning, using them with relative safety in your software development projects. With rise of dependency injection, nowadays libraries are not just third party pieces of software, they also become an important part of your own software projects. And this means that you need to have a way to store and share them within your team, but also have a sensible way of versioning them. Using Semantic Versioning is the best approach, since it gives a clean and easy way for your team to use versions and have everyone understand the same thing when talking about major, minor and patch version numbers. Now you need to make this a part of your CI/CD pipeline. Pre-Release version, aka the feature build While creating a new version of the library, you will also want to test the changes to your library in the code that consumes said library. For this you need to hav