Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the zoho-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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-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 6114

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php:6114) in /home/mother99/jacksonholdingcompany.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":2683,"date":"2024-03-08T04:50:38","date_gmt":"2024-03-08T04:50:38","guid":{"rendered":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/"},"modified":"2024-03-08T04:50:38","modified_gmt":"2024-03-08T04:50:38","slug":"avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm","status":"publish","type":"post","link":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/","title":{"rendered":"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm"},"content":{"rendered":"

A realistic guide to empowering application developers<\/h2>\n

In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world.\u2026 Read more on Cisco Blogs<\/a><\/p>\n

\u200b[[{“value”:”<\/p>\n

A realistic guide to empowering application developers<\/h2>\n

In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world. They\u2019re responsible for creating the apps we use daily, the websites we visit, and the systems that keep businesses running smoothly. Yet, despite their crucial role, developers often find themselves caught in a whirlwind of challenges \u2013 juggling tight deadlines, complex code, and the ever-evolving technology landscape.<\/p>\n

\u201cShift left<\/a>\u201d is a potentially game-changing approach that is transforming the way developers work, and ushering in a new era of software development\u2026 Or is it?<\/strong><\/p>\n\n

What is shift left?<\/h2>\n

Shift\u00a0 left<\/a> is a mindset and a set of practices prioritizing early and continuous testing and collaboration throughout the software development process. Initially, the term \u201cshift left\u201d reflected the shift of testing and quality assurance tasks to earlier stages in the development cycle, reducing the likelihood of defects slipping through and causing havoc down the line. It\u2019s was built on the premise of catching issues sooner rather than later.<\/p>\n

The problem with shift left<\/h2>\n

Over time, shift-left has turned into \u201cdump left.\u201d What does that mean? More and more things are being \u201cdumped\u201d on the developer to do earlier and earlier, all in the name of increased quality, velocity, and decreased costs. Herein lies the problem for developers. In this blog series, we will separate facts from fiction.<\/p>\n

Why should application developers care?<\/h2>\n

For application developers, shift left was supposed to be a game-changer, empowering them to take control of the quality of their code from the very beginning. If done right, shift left can:<\/p>\n

Enhance Collaboration<\/strong>: Shift left encourages cross-functional collaboration. Developers work more closely with testers, quality assurance teams, and even end-users right from the project\u2019s inception. This collaboration leads to better understanding and a shared vision, resulting in higher-quality software.
\nReduce Costs<\/strong>: Identifying and fixing issues early in the development process is far more cost-effective than discovering them after deploying the software. Shift left can save time and money by preventing defects from becoming deeply ingrained in the codebase.
\nIncrease Security<\/strong>: By integrating security testing from the start, Shift left practices help identify and address vulnerabilities early in the development process. This proactive approach reduces the risk of security breaches, data leaks, and potential threats, making the final product more robust and secure.
\nImprove Software Quality<\/strong>: Because issues are caught and addressed in the early stages of development, the end product is of higher quality. This reduces the risk of post-launch problems and enhances user experience and satisfaction.
\nElevate Reputation<\/strong>: In a competitive market, software developers are often judged by the quality of their products. Shift left practices help build a reputation for delivering reliable, secure, and user-friendly software, attracting more customers and clients.<\/p>\n

But that\u2019s not what is happening!<\/strong><\/em><\/p>\n

Shift left exhaustion\u2026 it\u2019s a thing<\/h2>\n

While shift left practices offer numerous advantages for application developers and the software development process, it\u2019s essential to acknowledge that this shift isn\u2019t without its challenges. Embracing shift-left can, at times, place a significant burden on developers. Let\u2019s explore the reality of shift-left exhaustion and how it can, and often, impacts the individuals at the forefront of software creation.<\/p>\n

Increased Workload<\/strong>: Shift left requires developers to be involved in testing, quality assurance, and collaboration throughout the development cycle. While this is undoubtedly beneficial for the final product, it can lead to an increased workload for developers who must balance their coding responsibilities with testing and problem-solving tasks.
\nContinuous Learning<\/strong>: Adapting to Shift left practices often requires developers to acquire new skills and stay current with the latest testing methodologies and tools. This continuous learning can be intellectually stimulating and exhausting, especially in an industry that evolves rapidly. Developers must understand new tools, processes, and technologies as more things get moved earlier in the development lifecycle.
\nBurnout<\/strong>: The added pressure of early and continuous testing and the demand for faster development cycles can lead to developer burnout. When developers are overburdened, their creativity and productivity may suffer, ultimately impacting the software quality they produce.
\nTime Constraints<\/strong>: Shifting testing and quality assurance left in the development process may impose strict time constraints. Developers may feel pressured to meet tight deadlines, which can be stressful and lead to rushed decision-making, potentially compromising the software\u2019s quality.
\nBalancing Act<\/strong>: Developers find themselves in a delicate balancing act \u2013 juggling the need for rigorous testing and collaboration with the demands of coding, debugging, and meeting project milestones. Striking this balance can be challenging.
\nTeam Dynamics<\/strong>: The transition to shift left practices may also disrupt team dynamics, as it requires open communication and collaboration with colleagues who may not have been traditionally involved in the early stages of development. While enhanced collaboration helps create a widespread understanding of the software\u2019s design and the systems it runs on, it can also lead to additional tension due to organizational boundaries or dealing with non-development teams. Managing these changes in team culture can be demanding.<\/p>\n

The pitfalls of overextension<\/h2>\n

It\u2019s clear the shift left methodology has extended beyond its original intent over time. Instead of solely focusing on testing, it now includes various aspects such as security, performance, accessibility, and more. This overextension has led to an overwhelming workload for developers and testers, causing tool exhaustion and burnout.<\/p>\n

Examples of overextension include:<\/h3>\n

Shift left Security<\/strong>: The concept of \u201cshift left security\u201d has emerged in the security realm. While integrating security considerations early in the development process is beneficial, this extension has put considerable pressure on developers to become security experts, creating a heavy workload that often leads to burnout.
\nShift left Scaling<\/strong>: Performance testing, traditionally a late-stage activity, is also being \u201cshifted left.\u201d While this can lead to early detection of performance issues, it adds another layer of complexity to the developer\u2019s role, increasing their workload and contributing to tool exhaustion.<\/p>\n

Misuse of shift left by leaders<\/h2>\n

In addition to overextension, some leaders have misunderstood and misused shift left. Instead of using it as a strategic approach to enhance product quality, people often use it to cut costs and speed up product delivery.<\/p>\n

Examples of misuse of shift left include:<\/h3>\n

Example 1: Some leaders view shift left as a way to reduce the need for specialized testers or security experts, pushing these responsibilities onto developers. This view not only increases the workload of developers but also often leads to less thorough testing or security checks due to the need for specialized skills.
\nExample 2: Sometimes, people misinterpret shift left to mean that developers should do all testing, even the late-stage testing traditionally done by QA teams. This misinterpretation can overburden developers and lead to missing issues due to a lack of perspective and expertise.<\/p>\n

Conclusion<\/h2>\n

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 needs to be realigned towards its original goal \u2013 improving quality by catching issues early \u2013 without overburdening our developers or compromising the product\u2019s integrity.<\/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. 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

Related resources<\/h2>\n

Visit the shift left developer resource hub<\/a>
\nStart a conversation in the
DevNet developer security community<\/a><\/p>\n

\n\t\tShare\n
\n
<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t <\/a>\n\t<\/div>\n<\/div>\n<\/div>\n
Share:<\/div>\n
\n
\n
<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t <\/a>\n\t<\/div>\n<\/div>\n<\/div>\n

“}]]\u00a0\u00a0“Shift left” is a potentially game-changing approach to software development that is transforming the way developers work, and ushering in a new era of software development… Or is it?!\u00a0\u00a0Read More<\/a>\u00a0Cisco Blogs\u00a0<\/p>","protected":false},"excerpt":{"rendered":"

<\/p>\n

A realistic guide to empowering application developers<\/h2>\n

In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world.\u2026 Read more on Cisco Blogs<\/a><\/p>\n

\u200b[[{“value”:”<\/p>\n

A realistic guide to empowering application developers<\/h2>\n

In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world. They\u2019re responsible for creating the apps we use daily, the websites we visit, and the systems that keep businesses running smoothly. Yet, despite their crucial role, developers often find themselves caught in a whirlwind of challenges \u2013 juggling tight deadlines, complex code, and the ever-evolving technology landscape.<\/p>\n

\u201cShift left<\/a>\u201d is a potentially game-changing approach that is transforming the way developers work, and ushering in a new era of software development\u2026 Or is it?<\/strong><\/p>\n

What is shift left?<\/h2>\n

Shift\u00a0 left<\/a> is a mindset and a set of practices prioritizing early and continuous testing and collaboration throughout the software development process. Initially, the term \u201cshift left\u201d reflected the shift of testing and quality assurance tasks to earlier stages in the development cycle, reducing the likelihood of defects slipping through and causing havoc down the line. It\u2019s was built on the premise of catching issues sooner rather than later.<\/p>\n

The problem with shift left<\/h2>\n

Over time, shift-left has turned into \u201cdump left.\u201d What does that mean? More and more things are being \u201cdumped\u201d on the developer to do earlier and earlier, all in the name of increased quality, velocity, and decreased costs. Herein lies the problem for developers. In this blog series, we will separate facts from fiction.<\/p>\n

Why should application developers care?<\/h2>\n

For application developers, shift left was supposed to be a game-changer, empowering them to take control of the quality of their code from the very beginning. If done right, shift left can:<\/p>\n

Enhance Collaboration<\/strong>: Shift left encourages cross-functional collaboration. Developers work more closely with testers, quality assurance teams, and even end-users right from the project\u2019s inception. This collaboration leads to better understanding and a shared vision, resulting in higher-quality software.
\nReduce Costs<\/strong>: Identifying and fixing issues early in the development process is far more cost-effective than discovering them after deploying the software. Shift left can save time and money by preventing defects from becoming deeply ingrained in the codebase.
\nIncrease Security<\/strong>: By integrating security testing from the start, Shift left practices help identify and address vulnerabilities early in the development process. This proactive approach reduces the risk of security breaches, data leaks, and potential threats, making the final product more robust and secure.
\nImprove Software Quality<\/strong>: Because issues are caught and addressed in the early stages of development, the end product is of higher quality. This reduces the risk of post-launch problems and enhances user experience and satisfaction.
\nElevate Reputation<\/strong>: In a competitive market, software developers are often judged by the quality of their products. Shift left practices help build a reputation for delivering reliable, secure, and user-friendly software, attracting more customers and clients.<\/p>\n

But that\u2019s not what is happening!<\/strong><\/em><\/p>\n

Shift left exhaustion\u2026 it\u2019s a thing<\/h2>\n

While shift left practices offer numerous advantages for application developers and the software development process, it\u2019s essential to acknowledge that this shift isn\u2019t without its challenges. Embracing shift-left can, at times, place a significant burden on developers. Let\u2019s explore the reality of shift-left exhaustion and how it can, and often, impacts the individuals at the forefront of software creation.<\/p>\n

Increased Workload<\/strong>: Shift left requires developers to be involved in testing, quality assurance, and collaboration throughout the development cycle. While this is undoubtedly beneficial for the final product, it can lead to an increased workload for developers who must balance their coding responsibilities with testing and problem-solving tasks.
\nContinuous Learning<\/strong>: Adapting to Shift left practices often requires developers to acquire new skills and stay current with the latest testing methodologies and tools. This continuous learning can be intellectually stimulating and exhausting, especially in an industry that evolves rapidly. Developers must understand new tools, processes, and technologies as more things get moved earlier in the development lifecycle.
\nBurnout<\/strong>: The added pressure of early and continuous testing and the demand for faster development cycles can lead to developer burnout. When developers are overburdened, their creativity and productivity may suffer, ultimately impacting the software quality they produce.
\nTime Constraints<\/strong>: Shifting testing and quality assurance left in the development process may impose strict time constraints. Developers may feel pressured to meet tight deadlines, which can be stressful and lead to rushed decision-making, potentially compromising the software\u2019s quality.
\nBalancing Act<\/strong>: Developers find themselves in a delicate balancing act \u2013 juggling the need for rigorous testing and collaboration with the demands of coding, debugging, and meeting project milestones. Striking this balance can be challenging.
\nTeam Dynamics<\/strong>: The transition to shift left practices may also disrupt team dynamics, as it requires open communication and collaboration with colleagues who may not have been traditionally involved in the early stages of development. While enhanced collaboration helps create a widespread understanding of the software\u2019s design and the systems it runs on, it can also lead to additional tension due to organizational boundaries or dealing with non-development teams. Managing these changes in team culture can be demanding.<\/p>\n

The pitfalls of overextension<\/h2>\n

It\u2019s clear the shift left methodology has extended beyond its original intent over time. Instead of solely focusing on testing, it now includes various aspects such as security, performance, accessibility, and more. This overextension has led to an overwhelming workload for developers and testers, causing tool exhaustion and burnout.<\/p>\n

Examples of overextension include:<\/h3>\n

Shift left Security<\/strong>: The concept of \u201cshift left security\u201d has emerged in the security realm. While integrating security considerations early in the development process is beneficial, this extension has put considerable pressure on developers to become security experts, creating a heavy workload that often leads to burnout.
\nShift left Scaling<\/strong>: Performance testing, traditionally a late-stage activity, is also being \u201cshifted left.\u201d While this can lead to early detection of performance issues, it adds another layer of complexity to the developer\u2019s role, increasing their workload and contributing to tool exhaustion.<\/p>\n

Misuse of shift left by leaders<\/h2>\n

In addition to overextension, some leaders have misunderstood and misused shift left. Instead of using it as a strategic approach to enhance product quality, people often use it to cut costs and speed up product delivery.<\/p>\n

Examples of misuse of shift left include:<\/h3>\n

Example 1: Some leaders view shift left as a way to reduce the need for specialized testers or security experts, pushing these responsibilities onto developers. This view not only increases the workload of developers but also often leads to less thorough testing or security checks due to the need for specialized skills.
\nExample 2: Sometimes, people misinterpret shift left to mean that developers should do all testing, even the late-stage testing traditionally done by QA teams. This misinterpretation can overburden developers and lead to missing issues due to a lack of perspective and expertise.<\/p>\n

Conclusion<\/h2>\n

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 needs to be realigned towards its original goal \u2013 improving quality by catching issues early \u2013 without overburdening our developers or compromising the product\u2019s integrity.<\/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. 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

Related resources<\/h2>\n

Visit the shift left developer resource hub<\/a>
\nStart a conversation in the
DevNet developer security community<\/a><\/p>\n

\n\t\tShare<\/p>\n
\n
<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t <\/a>\n\t<\/div>\n<\/div>\n<\/div>\n
Share:<\/div>\n
\n
\n
<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t\t<\/a>\n\t<\/div>\n<\/div>\n
\n
\n\t <\/a>\n\t<\/div>\n<\/div>\n<\/div>\n

“}]]\u00a0\u00a0“Shift left” is a potentially game-changing approach to software development that is transforming the way developers work, and ushering in a new era of software development… Or is it?!\u00a0\u00a0Read More<\/a>\u00a0Cisco Blogs\u00a0<\/p>\n

<\/p>\n","protected":false},"author":0,"featured_media":2684,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-2683","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cisco-learning"],"yoast_head":"\nAvoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm - JHC<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm\" \/>\n<meta property=\"og:description\" content=\"A realistic guide to empowering application developers In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world.\u2026 Read more on Cisco Blogs \u200b[[{"value":" A realistic guide to empowering application developers In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world. They\u2019re responsible for creating the apps we use daily, the websites we visit, and the systems that keep businesses running smoothly. Yet, despite their crucial role, developers often find themselves caught in a whirlwind of challenges \u2013 juggling tight deadlines, complex code, and the ever-evolving technology landscape. \u201cShift left\u201d is a potentially game-changing approach that is transforming the way developers work, and ushering in a new era of software development\u2026 Or is it? What is shift left? Shift\u00a0 left is a mindset and a set of practices prioritizing early and continuous testing and collaboration throughout the software development process. Initially, the term \u201cshift left\u201d reflected the shift of testing and quality assurance tasks to earlier stages in the development cycle, reducing the likelihood of defects slipping through and causing havoc down the line. It\u2019s was built on the premise of catching issues sooner rather than later. The problem with shift left Over time, shift-left has turned into \u201cdump left.\u201d What does that mean? More and more things are being \u201cdumped\u201d on the developer to do earlier and earlier, all in the name of increased quality, velocity, and decreased costs. Herein lies the problem for developers. In this blog series, we will separate facts from fiction. Why should application developers care? For application developers, shift left was supposed to be a game-changer, empowering them to take control of the quality of their code from the very beginning. If done right, shift left can: Enhance Collaboration: Shift left encourages cross-functional collaboration. Developers work more closely with testers, quality assurance teams, and even end-users right from the project\u2019s inception. This collaboration leads to better understanding and a shared vision, resulting in higher-quality software. Reduce Costs: Identifying and fixing issues early in the development process is far more cost-effective than discovering them after deploying the software. Shift left can save time and money by preventing defects from becoming deeply ingrained in the codebase. Increase Security: By integrating security testing from the start, Shift left practices help identify and address vulnerabilities early in the development process. This proactive approach reduces the risk of security breaches, data leaks, and potential threats, making the final product more robust and secure. Improve Software Quality: Because issues are caught and addressed in the early stages of development, the end product is of higher quality. This reduces the risk of post-launch problems and enhances user experience and satisfaction. Elevate Reputation: In a competitive market, software developers are often judged by the quality of their products. Shift left practices help build a reputation for delivering reliable, secure, and user-friendly software, attracting more customers and clients. But that\u2019s not what is happening! Shift left exhaustion\u2026 it\u2019s a thing While shift left practices offer numerous advantages for application developers and the software development process, it\u2019s essential to acknowledge that this shift isn\u2019t without its challenges. Embracing shift-left can, at times, place a significant burden on developers. Let\u2019s explore the reality of shift-left exhaustion and how it can, and often, impacts the individuals at the forefront of software creation. Increased Workload: Shift left requires developers to be involved in testing, quality assurance, and collaboration throughout the development cycle. While this is undoubtedly beneficial for the final product, it can lead to an increased workload for developers who must balance their coding responsibilities with testing and problem-solving tasks. Continuous Learning: Adapting to Shift left practices often requires developers to acquire new skills and stay current with the latest testing methodologies and tools. This continuous learning can be intellectually stimulating and exhausting, especially in an industry that evolves rapidly. Developers must understand new tools, processes, and technologies as more things get moved earlier in the development lifecycle. Burnout: The added pressure of early and continuous testing and the demand for faster development cycles can lead to developer burnout. When developers are overburdened, their creativity and productivity may suffer, ultimately impacting the software quality they produce. Time Constraints: Shifting testing and quality assurance left in the development process may impose strict time constraints. Developers may feel pressured to meet tight deadlines, which can be stressful and lead to rushed decision-making, potentially compromising the software\u2019s quality. Balancing Act: Developers find themselves in a delicate balancing act \u2013 juggling the need for rigorous testing and collaboration with the demands of coding, debugging, and meeting project milestones. Striking this balance can be challenging. Team Dynamics: The transition to shift left practices may also disrupt team dynamics, as it requires open communication and collaboration with colleagues who may not have been traditionally involved in the early stages of development. While enhanced collaboration helps create a widespread understanding of the software\u2019s design and the systems it runs on, it can also lead to additional tension due to organizational boundaries or dealing with non-development teams. Managing these changes in team culture can be demanding. The pitfalls of overextension It\u2019s clear the shift left methodology has extended beyond its original intent over time. Instead of solely focusing on testing, it now includes various aspects such as security, performance, accessibility, and more. This overextension has led to an overwhelming workload for developers and testers, causing tool exhaustion and burnout. Examples of overextension include: Shift left Security: The concept of \u201cshift left security\u201d has emerged in the security realm. While integrating security considerations early in the development process is beneficial, this extension has put considerable pressure on developers to become security experts, creating a heavy workload that often leads to burnout. Shift left Scaling: Performance testing, traditionally a late-stage activity, is also being \u201cshifted left.\u201d While this can lead to early detection of performance issues, it adds another layer of complexity to the developer\u2019s role, increasing their workload and contributing to tool exhaustion. Misuse of shift left by leaders In addition to overextension, some leaders have misunderstood and misused shift left. Instead of using it as a strategic approach to enhance product quality, people often use it to cut costs and speed up product delivery. Examples of misuse of shift left include: Example 1: Some leaders view shift left as a way to reduce the need for specialized testers or security experts, pushing these responsibilities onto developers. This view not only increases the workload of developers but also often leads to less thorough testing or security checks due to the need for specialized skills. Example 2: Sometimes, people misinterpret shift left to mean that developers should do all testing, even the late-stage testing traditionally done by QA teams. This misinterpretation can overburden developers and lead to missing issues due to a lack of perspective and expertise. Conclusion 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 needs to be realigned towards its original goal \u2013 improving quality by catching issues early \u2013 without overburdening our developers or compromising the product\u2019s integrity. 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. 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. Related resources Visit the shift left developer resource hub Start a conversation in the DevNet developer security community Share Share: "}]]\u00a0\u00a0"Shift left" is a potentially game-changing approach to software development that is transforming the way developers work, and ushering in a new era of software development... Or is it?!\u00a0\u00a0Read More\u00a0Cisco Blogs\u00a0\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\" \/>\n<meta property=\"og:site_name\" content=\"JHC\" \/>\n<meta property=\"article:published_time\" content=\"2024-03-08T04:50:38+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif\" \/>\n\t<meta property=\"og:image:width\" content=\"1\" \/>\n\t<meta property=\"og:image:height\" content=\"1\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/gif\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\"},\"author\":{\"name\":\"\",\"@id\":\"\"},\"headline\":\"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm\",\"datePublished\":\"2024-03-08T04:50:38+00:00\",\"dateModified\":\"2024-03-08T04:50:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\"},\"wordCount\":1344,\"publisher\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif\",\"articleSection\":[\"Cisco: Learning\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\",\"url\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\",\"name\":\"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm - JHC\",\"isPartOf\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif\",\"datePublished\":\"2024-03-08T04:50:38+00:00\",\"dateModified\":\"2024-03-08T04:50:38+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage\",\"url\":\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif\",\"contentUrl\":\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif\",\"width\":1,\"height\":1},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/jacksonholdingcompany.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/#website\",\"url\":\"https:\/\/jacksonholdingcompany.com\/\",\"name\":\"JHC\",\"description\":\"Your Business Is Our Business\",\"publisher\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/jacksonholdingcompany.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/#organization\",\"name\":\"JHC\",\"url\":\"https:\/\/jacksonholdingcompany.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/jacksonholdingcompany.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2023\/07\/cropped-cropped-jHC-white-500-\u00d7-200-px-1-1.png\",\"contentUrl\":\"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2023\/07\/cropped-cropped-jHC-white-500-\u00d7-200-px-1-1.png\",\"width\":452,\"height\":149,\"caption\":\"JHC\"},\"image\":{\"@id\":\"https:\/\/jacksonholdingcompany.com\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm - JHC","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/","og_locale":"en_US","og_type":"article","og_title":"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm","og_description":"A realistic guide to empowering application developers In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world.\u2026 Read more on Cisco Blogs \u200b[[{\"value\":\" A realistic guide to empowering application developers In today\u2019s fast-paced digital landscape, application developers are the unsung heroes who craft the software that powers our modern world. They\u2019re responsible for creating the apps we use daily, the websites we visit, and the systems that keep businesses running smoothly. Yet, despite their crucial role, developers often find themselves caught in a whirlwind of challenges \u2013 juggling tight deadlines, complex code, and the ever-evolving technology landscape. \u201cShift left\u201d is a potentially game-changing approach that is transforming the way developers work, and ushering in a new era of software development\u2026 Or is it? What is shift left? Shift\u00a0 left is a mindset and a set of practices prioritizing early and continuous testing and collaboration throughout the software development process. Initially, the term \u201cshift left\u201d reflected the shift of testing and quality assurance tasks to earlier stages in the development cycle, reducing the likelihood of defects slipping through and causing havoc down the line. It\u2019s was built on the premise of catching issues sooner rather than later. The problem with shift left Over time, shift-left has turned into \u201cdump left.\u201d What does that mean? More and more things are being \u201cdumped\u201d on the developer to do earlier and earlier, all in the name of increased quality, velocity, and decreased costs. Herein lies the problem for developers. In this blog series, we will separate facts from fiction. Why should application developers care? For application developers, shift left was supposed to be a game-changer, empowering them to take control of the quality of their code from the very beginning. If done right, shift left can: Enhance Collaboration: Shift left encourages cross-functional collaboration. Developers work more closely with testers, quality assurance teams, and even end-users right from the project\u2019s inception. This collaboration leads to better understanding and a shared vision, resulting in higher-quality software. Reduce Costs: Identifying and fixing issues early in the development process is far more cost-effective than discovering them after deploying the software. Shift left can save time and money by preventing defects from becoming deeply ingrained in the codebase. Increase Security: By integrating security testing from the start, Shift left practices help identify and address vulnerabilities early in the development process. This proactive approach reduces the risk of security breaches, data leaks, and potential threats, making the final product more robust and secure. Improve Software Quality: Because issues are caught and addressed in the early stages of development, the end product is of higher quality. This reduces the risk of post-launch problems and enhances user experience and satisfaction. Elevate Reputation: In a competitive market, software developers are often judged by the quality of their products. Shift left practices help build a reputation for delivering reliable, secure, and user-friendly software, attracting more customers and clients. But that\u2019s not what is happening! Shift left exhaustion\u2026 it\u2019s a thing While shift left practices offer numerous advantages for application developers and the software development process, it\u2019s essential to acknowledge that this shift isn\u2019t without its challenges. Embracing shift-left can, at times, place a significant burden on developers. Let\u2019s explore the reality of shift-left exhaustion and how it can, and often, impacts the individuals at the forefront of software creation. Increased Workload: Shift left requires developers to be involved in testing, quality assurance, and collaboration throughout the development cycle. While this is undoubtedly beneficial for the final product, it can lead to an increased workload for developers who must balance their coding responsibilities with testing and problem-solving tasks. Continuous Learning: Adapting to Shift left practices often requires developers to acquire new skills and stay current with the latest testing methodologies and tools. This continuous learning can be intellectually stimulating and exhausting, especially in an industry that evolves rapidly. Developers must understand new tools, processes, and technologies as more things get moved earlier in the development lifecycle. Burnout: The added pressure of early and continuous testing and the demand for faster development cycles can lead to developer burnout. When developers are overburdened, their creativity and productivity may suffer, ultimately impacting the software quality they produce. Time Constraints: Shifting testing and quality assurance left in the development process may impose strict time constraints. Developers may feel pressured to meet tight deadlines, which can be stressful and lead to rushed decision-making, potentially compromising the software\u2019s quality. Balancing Act: Developers find themselves in a delicate balancing act \u2013 juggling the need for rigorous testing and collaboration with the demands of coding, debugging, and meeting project milestones. Striking this balance can be challenging. Team Dynamics: The transition to shift left practices may also disrupt team dynamics, as it requires open communication and collaboration with colleagues who may not have been traditionally involved in the early stages of development. While enhanced collaboration helps create a widespread understanding of the software\u2019s design and the systems it runs on, it can also lead to additional tension due to organizational boundaries or dealing with non-development teams. Managing these changes in team culture can be demanding. The pitfalls of overextension It\u2019s clear the shift left methodology has extended beyond its original intent over time. Instead of solely focusing on testing, it now includes various aspects such as security, performance, accessibility, and more. This overextension has led to an overwhelming workload for developers and testers, causing tool exhaustion and burnout. Examples of overextension include: Shift left Security: The concept of \u201cshift left security\u201d has emerged in the security realm. While integrating security considerations early in the development process is beneficial, this extension has put considerable pressure on developers to become security experts, creating a heavy workload that often leads to burnout. Shift left Scaling: Performance testing, traditionally a late-stage activity, is also being \u201cshifted left.\u201d While this can lead to early detection of performance issues, it adds another layer of complexity to the developer\u2019s role, increasing their workload and contributing to tool exhaustion. Misuse of shift left by leaders In addition to overextension, some leaders have misunderstood and misused shift left. Instead of using it as a strategic approach to enhance product quality, people often use it to cut costs and speed up product delivery. Examples of misuse of shift left include: Example 1: Some leaders view shift left as a way to reduce the need for specialized testers or security experts, pushing these responsibilities onto developers. This view not only increases the workload of developers but also often leads to less thorough testing or security checks due to the need for specialized skills. Example 2: Sometimes, people misinterpret shift left to mean that developers should do all testing, even the late-stage testing traditionally done by QA teams. This misinterpretation can overburden developers and lead to missing issues due to a lack of perspective and expertise. Conclusion 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 needs to be realigned towards its original goal \u2013 improving quality by catching issues early \u2013 without overburdening our developers or compromising the product\u2019s integrity. 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. 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. Related resources Visit the shift left developer resource hub Start a conversation in the DevNet developer security community Share Share: \"}]]\u00a0\u00a0\"Shift left\" is a potentially game-changing approach to software development that is transforming the way developers work, and ushering in a new era of software development... Or is it?!\u00a0\u00a0Read More\u00a0Cisco Blogs\u00a0","og_url":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/","og_site_name":"JHC","article_published_time":"2024-03-08T04:50:38+00:00","og_image":[{"width":1,"height":1,"url":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif","type":"image\/gif"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#article","isPartOf":{"@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/"},"author":{"name":"","@id":""},"headline":"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm","datePublished":"2024-03-08T04:50:38+00:00","dateModified":"2024-03-08T04:50:38+00:00","mainEntityOfPage":{"@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/"},"wordCount":1344,"publisher":{"@id":"https:\/\/jacksonholdingcompany.com\/#organization"},"image":{"@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage"},"thumbnailUrl":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif","articleSection":["Cisco: Learning"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/","url":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/","name":"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm - JHC","isPartOf":{"@id":"https:\/\/jacksonholdingcompany.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage"},"image":{"@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage"},"thumbnailUrl":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif","datePublished":"2024-03-08T04:50:38+00:00","dateModified":"2024-03-08T04:50:38+00:00","breadcrumb":{"@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#primaryimage","url":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif","contentUrl":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2024\/03\/16605177-7pbxXe.gif","width":1,"height":1},{"@type":"BreadcrumbList","@id":"https:\/\/jacksonholdingcompany.com\/avoiding-shift-left-exhaustion-part-1-shannon-mcfarland-on-march-7-2024-at-526-pm\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/jacksonholdingcompany.com\/"},{"@type":"ListItem","position":2,"name":"Avoiding Shift Left Exhaustion \u2013 Part 1 Shannon McFarland on March 7, 2024 at 5:26 pm"}]},{"@type":"WebSite","@id":"https:\/\/jacksonholdingcompany.com\/#website","url":"https:\/\/jacksonholdingcompany.com\/","name":"JHC","description":"Your Business Is Our Business","publisher":{"@id":"https:\/\/jacksonholdingcompany.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jacksonholdingcompany.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/jacksonholdingcompany.com\/#organization","name":"JHC","url":"https:\/\/jacksonholdingcompany.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jacksonholdingcompany.com\/#\/schema\/logo\/image\/","url":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2023\/07\/cropped-cropped-jHC-white-500-\u00d7-200-px-1-1.png","contentUrl":"https:\/\/jacksonholdingcompany.com\/wp-content\/uploads\/2023\/07\/cropped-cropped-jHC-white-500-\u00d7-200-px-1-1.png","width":452,"height":149,"caption":"JHC"},"image":{"@id":"https:\/\/jacksonholdingcompany.com\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/posts\/2683","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/comments?post=2683"}],"version-history":[{"count":0,"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/posts\/2683\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/media\/2684"}],"wp:attachment":[{"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/media?parent=2683"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/categories?post=2683"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jacksonholdingcompany.com\/wp-json\/wp\/v2\/tags?post=2683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}