easy-accordion-free domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114zoho-flow domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114In my previous blog post<\/a>, we discussed the state of the union for shift left and and how many organizations are not implementing correctly. So what now? We need to understand the are\u2026 Read more on Cisco Blogs<\/a><\/p>\n \u200b[[{“value”:”<\/p>\n In my previous blog post<\/a>, we discussed the state of the union for shift left and and how many organizations are not implementing correctly. So what now? We need to understand the are signs of doing shift left incorrectly and learn how to take a different approach.<\/p>\n A poor shift left model has \u201csoft\u201d and \u201chard\u201d consequences. Soft consequences impact the development staff\u2019s workload, health, and job satisfaction. Some of the soft consequences of a poorly implemented shift left model include:<\/p>\n Increased workloads Hard consequences are those that impact the actual business. Some of the hard consequences include:<\/p>\n Delays in shipping code\/applications Many of the high friction points with a poor shift left model involve developers\u2019 interaction with things like security, infrastructure, and observability and their having to understand complex security protocols, threats, and tools. Developers may have to interact with physical or virtual infrastructure. Also, having to instrument tracing, metrics, and logging for applications are a few of the many shift-left-oriented areas that cause toil for developers.<\/p>\n In addition to the technologies, developers must deal with the time it takes to learn new processes, adopt new tools, and interact with new groups.<\/p>\n In addition to providing developers with a streamlined way of learning about the new things they must take care of, there are other practical steps to ease the burden of shift left.<\/p>\n Developers have many tools, technologies, frameworks, SDKs, and communication tools to deal with. So, go to where they are and provide them with value through learning, services, and processes.<\/p>\n Provide value in the developer tools<\/strong>: High-quality IDE plugins, well-documented and well-implemented automation frameworks, well-supported SDKs, etc. Once developers check in code to a CI\/CD pipeline, provide the configurations and integrations in the pipeline that keeps things from falling apart.<\/p>\n Maintain consistency, security, observability, and quality inside of the pipeline Provide end-to-end value for the developer, operations teams, and business leaders.<\/p>\n \u2022 Maintain end-to-end observability for both technical and business insights Cisco DevNet<\/a> and the product engineering teams provide developer-centric training, tools, and code to reduce the toil in programmatically interacting with Cisco products and services.<\/p>\n Access to Infrastructure-as-Code, API and SDK documentation, tools, and code<\/a> While shift left is fundamentally sound and beneficial, it has been stretched beyond its original intent and misused, negatively impacting developers and product quality. The focus must align towards improving quality, security, and availability by catching issues early \u2013 without overburdening our developers or compromising the product\u2019s integrity. You can accomplish this by enabling developers with the training, tools, technologies, and processes.<\/p>\n A balanced approach, incorporating the core principles of shift left without overextending its reach or misusing it to cut corners, will help organizations achieve their goals.<\/p>\n As we continue to navigate the evolving landscape of software development, we must remember that methodologies and frameworks are there to facilitate our work, not to hinder it. And like any tool, they are only as effective as the hands that wield them.<\/p>\n “}]]\u00a0\u00a0See how smart shift left provides developers with a streamlined way of learning about the new tasks they must take care of, and other practical steps to achieve a balanced approach to shift left.\u00a0\u00a0Read More<\/a>\u00a0Cisco Blogs\u00a0<\/p>","protected":false},"excerpt":{"rendered":" <\/p>\n In my previous blog post<\/a>, we discussed the state of the union for shift left and and how many organizations are not implementing correctly. So what now? We need to understand the are\u2026 Read more on Cisco Blogs<\/a><\/p>\n \u200b[[{“value”:”<\/p>\n In my previous blog post<\/a>, we discussed the state of the union for shift left and and how many organizations are not implementing correctly. So what now? We need to understand the are signs of doing shift left incorrectly and learn how to take a different approach.<\/p>\n A poor shift left model has \u201csoft\u201d and \u201chard\u201d consequences. Soft consequences impact the development staff\u2019s workload, health, and job satisfaction. Some of the soft consequences of a poorly implemented shift left model include:<\/p>\n Increased workloads Hard consequences are those that impact the actual business. Some of the hard consequences include:<\/p>\n Delays in shipping code\/applications Many of the high friction points with a poor shift left model involve developers\u2019 interaction with things like security, infrastructure, and observability and their having to understand complex security protocols, threats, and tools. Developers may have to interact with physical or virtual infrastructure. Also, having to instrument tracing, metrics, and logging for applications are a few of the many shift-left-oriented areas that cause toil for developers.<\/p>\n In addition to the technologies, developers must deal with the time it takes to learn new processes, adopt new tools, and interact with new groups.<\/p>\n In addition to providing developers with a streamlined way of learning about the new things they must take care of, there are other practical steps to ease the burden of shift left.<\/p>\n Developers have many tools, technologies, frameworks, SDKs, and communication tools to deal with. So, go to where they are and provide them with value through learning, services, and processes.<\/p>\n Provide value in the developer tools<\/strong>: High-quality IDE plugins, well-documented and well-implemented automation frameworks, well-supported SDKs, etc. Once developers check in code to a CI\/CD pipeline, provide the configurations and integrations in the pipeline that keeps things from falling apart.<\/p>\n Maintain consistency, security, observability, and quality inside of the pipeline Provide end-to-end value for the developer, operations teams, and business leaders.<\/p>\n \u2022 Maintain end-to-end observability for both technical and business insights Cisco DevNet<\/a> and the product engineering teams provide developer-centric training, tools, and code to reduce the toil in programmatically interacting with Cisco products and services.<\/p>\n Access to Infrastructure-as-Code, API and SDK documentation, tools, and code<\/a> While shift left is fundamentally sound and beneficial, it has been stretched beyond its original intent and misused, negatively impacting developers and product quality. The focus must align towards improving quality, security, and availability by catching issues early \u2013 without overburdening our developers or compromising the product\u2019s integrity. You can accomplish this by enabling developers with the training, tools, technologies, and processes.<\/p>\n A balanced approach, incorporating the core principles of shift left without overextending its reach or misusing it to cut corners, will help organizations achieve their goals.<\/p>\n As we continue to navigate the evolving landscape of software development, we must remember that methodologies and frameworks are there to facilitate our work, not to hinder it. And like any tool, they are only as effective as the hands that wield them.<\/p>\nIntroduction<\/h2>\n
Recognizing the consequences of a poor shift left model<\/h2>\n
\nBurnout and mental well-being
\nReduced productivity
\nPoor job satisfaction<\/p>\n
\nLower-quality tooling and automation
\nIncreased security risks
\nIncreased likelihood of outages
\nPoor customer satisfaction<\/p>\nSmart shift left \u2013 the steps to a better way<\/h2>\n
Go to the developers<\/h3>\n
\nEngage with the developer community where they are<\/strong>: Educate and enable them at hackathons, dev-centric events, and inside dev-centric forums.
\nReduce\/remove the developer toil<\/strong>: Cross-environment tooling, in-code API and image checks, reliable API documentation (changelogs, roadmaps, etc.).<\/p>\nMaintain consistency inside of tooling<\/h3>\n
\nAdd additional capabilities to do external API security checks and infrastructure dependency checks
\nAdd pipeline observability into the end-to-end observability architecture
\nWhen safe and wise to do so, add in AI\/ML capabilities to augment code quality checks and remediation<\/p>\nDerive value from the experience<\/h3>\n
\n\u2022 Conditionally add policy triggers to the insights so that semi-automated or fully automated actions are taken
\n\u2022 Leverage multi-persona dashboards: Use the same tools, but the view changes for each persona
\n\u2022 Circular improvement: Value or loss of value finds its way back to the left for retrospective and improvements<\/p>\nWhat is Cisco doing in this space?<\/h2>\n
\nDeveloper and operator learning<\/a>
\nSecure Application Integrations such as Panoptica\u2019s API Gateway integration<\/a>
\nSecure CI\/CD pipeline integration via Panoptica\u2019s CI\/CD integration<\/a>
\nAccess to live interactive test environments for developers and operators to build and test their automation code, such as the NSO Developer Explorer<\/a> and NSO Developer Studio<\/a>
\nEnd-to-end observability for code, applications, and infrastructure via Cisco Full Stack Observability<\/a><\/p>\nAchieving a balanced approach to shift left<\/h2>\n
Introduction<\/h2>\n
Introduction<\/h2>\n
Recognizing the consequences of a poor shift left model<\/h2>\n
\nBurnout and mental well-being
\nReduced productivity
\nPoor job satisfaction<\/p>\n
\nLower-quality tooling and automation
\nIncreased security risks
\nIncreased likelihood of outages
\nPoor customer satisfaction<\/p>\nSmart shift left \u2013 the steps to a better way<\/h2>\n
Go to the developers<\/h3>\n
\nEngage with the developer community where they are<\/strong>: Educate and enable them at hackathons, dev-centric events, and inside dev-centric forums.
\nReduce\/remove the developer toil<\/strong>: Cross-environment tooling, in-code API and image checks, reliable API documentation (changelogs, roadmaps, etc.).<\/p>\nMaintain consistency inside of tooling<\/h3>\n
\nAdd additional capabilities to do external API security checks and infrastructure dependency checks
\nAdd pipeline observability into the end-to-end observability architecture
\nWhen safe and wise to do so, add in AI\/ML capabilities to augment code quality checks and remediation<\/p>\nDerive value from the experience<\/h3>\n
\n\u2022 Conditionally add policy triggers to the insights so that semi-automated or fully automated actions are taken
\n\u2022 Leverage multi-persona dashboards: Use the same tools, but the view changes for each persona
\n\u2022 Circular improvement: Value or loss of value finds its way back to the left for retrospective and improvements<\/p>\nWhat is Cisco doing in this space?<\/h2>\n
\nDeveloper and operator learning<\/a>
\nSecure Application Integrations such as Panoptica\u2019s API Gateway integration<\/a>
\nSecure CI\/CD pipeline integration via Panoptica\u2019s CI\/CD integration<\/a>
\nAccess to live interactive test environments for developers and operators to build and test their automation code, such as the NSO Developer Explorer<\/a> and NSO Developer Studio<\/a>
\nEnd-to-end observability for code, applications, and infrastructure via Cisco Full Stack Observability<\/a><\/p>\nAchieving a balanced approach to shift left<\/h2>\n