The reason why your enterprise wants to be more agile is the promise to be sustainably profitable in an ever faster moving world. More flexibility, more transparency and lower risk will help us achieving this. This is our assumption. Did you ever ask if Agile made you better?
The main reason behind writing this article is to highlight one of the best Ecommerce Software available in market, Prestashop. This in order to manage their online store and it has a proven level of security as well.
We, the CloudShare Quality Assurance team, migrated from a web-based UI Automation implemented using C# and Watin (http://watin.org/) to a solution using C#, Selenium (http://docs.seleniumhq.org/) and Applitools Eyes (http://applitools.com/).
At any company that leverages technology there is invariably a disconnect between the development and operations teams (hence the rise of DevOps). Both are driven by the success of the business and have a role to play; but each team views its role, its success criteria and its goals differently based on the unique challenges each must face, particularly in a world increasingly defined in software. I’d like to present this topic as “here is what every developer wished that operations knew so that we can work better together”. Or stated another way, as a developer, here is the list of things that I need from operations so we each can do our jobs more efficiently to grow the business that may end up putting our kids through college – or hopefully more.
Given the huge amount of buzz around Microservices right now, as well as the huge amount of content being generated, I thought I’d begin curating a “Microservices Reading List.” With that said, the main reason for the creation of this page is the continual question: “Great talk/article/etc. Where can I learn more?” Below you’ll find articles, blogs, videos, slide decks, etc. I’m going to try to categorize them a bit as well. This is by no means a complete catalog. Continue to check back for updates!
Several years ago, I gave a presentation on corporate open source anti-patterns. Several of my anti-patterns were clear and unequivocal (e.g., don’t announce that you’re open sourcing something without making the source code available, dummy!), but others were more complicated.