We all want to develop better software, faster—not just for the sake of having cool software, but because we use software to solve business opportunities and to create competitive advantages for companies. DevOps is a much-used buzzword that gets thrown around when talking about ways to deliver software more quickly—but there are misconceptions about what it is and what it is not.
Graphical programming—or low-code/no-code programming—is excellent for education. When you’re trying to get an 8-year-old to understand programming logic and what software development can accomplish, the ability to create something concrete without spending months learning a programming language or debugging typing or syntax errors is powerful.
When you’re trying to develop a business application, one that has specific, pre-defined business logic associated with it, graphical programming will usually only get you 90% of the way there. When we’re talking about a business application, that isn’t enough. And in most graphical programming platforms, going from 90% to 100% is exceptionally hard.
Topics: Application Composition, Business Agility, Enterprise Applications, Enterprise Software, PaaS, Reducing Costs of IT, software development, DevOps First, Full Stack Deployment, DevOps Automation, Machine Generated Code, Infrastructure Automation
Every school’s goal is to give students an advantage in the professional world. No matter what subject they teach, university professors squeeze as much information as possible into a short semester to create intellectual value. For computer science, this is most obvious in the global race for artificial intelligence (AI) talent. According to Forbes, “The countries pushing AI forward have ready access to qualified professionals. They have also developed university programs and AI curriculum to develop more talent. When it comes to emerging technologies, intellectual capital is a huge strategic advantage.”
A few weeks ago TechTarget published a great article by Kurt Marko: "To build or to buy? That is the DevOps toolchain question”
At the end Kurt summarizes an organization's decision to three factors: expertise and comfort toward deploying open source tools, opinionated versus non-opinionated tooling choices, and the underlying PaaS. Allow me to add another important criterion: automation. More to the point, should the automation code play a role in your decision to build or buy?
Until now, development and operations teams have had to choose between a custom-built DevOps pipeline or pre-made toolchain bundled with cloud provider or PaaS offering. A pre-made toolchain is simpler than individually collected tools, but it sacrifices flexibility and control. Organizations that don't want to use an opinionated PaaS stack and pre-defined toolchains, yet don't have the time or expertise to stitch together and manage a myriad of DevOps point products, now have a new option that combines the best of both worlds: full stack automation with machine generated DevOps pipelines. Agile Stacks can provide customizable DevOps toolchain and create standardized environments, based on machine generated stack automation code.