{"id":5768,"date":"2024-03-07T15:47:50","date_gmt":"2024-03-07T15:47:50","guid":{"rendered":"https:\/\/www.horsesforsources.com\/?p=5768"},"modified":"2024-09-11T11:38:28","modified_gmt":"2024-09-11T11:38:28","slug":"why-actions-will-eat-code_050724","status":"publish","type":"post","link":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/","title":{"rendered":"Why actions will eat code"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Has there ever been a time when we’ve challenged the ever-increasing stranglehold enterprise applications and their codebase have been inflicting on us for decades?\u00a0 Where each version upgrade requires more and more code to be rewritten just to keep everything working; where we’re subjected to aging developers holding us to ransom for their dated programming languages. Because they can.<\/p>\n

Where it just takes bloody ages to get anything done because our enterprise technology just sucks and these cloud migrations are a big mess. \u00a0And where both our personal and professional lives are beset by the constant inability of applications to talk to each other, to validate who the hell we are every day, to keep upping their subscription fees… Because they can.<\/p>\n

Well maybe they won’t for much longer as the sheer energy behind this move to generative solutions takes hold, and the desire to drive actions<\/em> to bypass bad antiquated technology overwhelms the old ways of doing things.\u00a0 So who better to speak his mind after a lifetime grappling with technological stranglehold than our new Chief Technology Evangelist<\/a>, Francis Carden…<\/p>\n

Our future is all about visible actions and invisible technology<\/span><\/h3>\n

After a remarkable journey through the era of computerization and its remarkable contributions, we stand at a pivotal moment of innovation. It’s time to bid farewell to a core element that has been instrumental in its success:\u00a0 We must undertake a comprehensive reevaluation of our enterprise application suites and the ecosystem of coding that has been central to their development and support.<\/p>\n

Our reliance on codifying applications suffocates innovation<\/span><\/h3>\n

Something hit me in the face when I recently heard that we were going to start using AI to write code. My first thought was that this is BS. Writing code was never really the problem at the creation stage of each software application! Because even if the business and IT requirements were always in total alignment to codify great applications, it was really the next 10,20, or even 30 years of supporting this \u201csoftware\u201d through coding hacks that created the slow strangulation towards legacy debt and accelerating cost of ownership. These mammoth costs and constraints stalled so many enterprise innovations and dare I say, will continue to stifle our ability to embrace the new transformative shift in technology with AI if we stay on this course. We must stop thinking about coding the old way.<\/p>\n

The new focus is on ACTIONS, not applications<\/span><\/h3>\n

Enter the new world of Large Action Libraries (LALs) where ACTIONS are the true makeup of all future business processes and application needs. Easily understandable and digestible, ACTIONS can be consolidated into Large Action Models (LAMs) that become consistent and flexible interconnected assets to meet any current or future business, or IT need rapidly. ACTIONS are key and can still be built by programmers in code, but more and more likely, by citizen developments using lowcode and nocode. Software will now be constructed, not coded.<\/p>\n

This concept of ACTIONS, LALs and LAMs is not new because we\u2019ve dreamed of being able to do this since the first program became a callable \u201csubroutine\u201d! But until more recently, we have never had the technology to do this properly. The dream of modular, reusable code through ACTIONS, LALs, and LAMs, once constrained by hardware limitations, is now achievable and transformative due to the exponential growth in computing power and cloud infrastructure, mirroring the AI revolution’s leap from theoretical to practical, game-changing applications.<\/p>\n

A world without code frees us to innovate with technology at a speed we\u2019ve never experienced<\/span><\/h3>\n

Picture reducing the ongoing costs of supporting apps written with code for our users, consumers, and partners to a mere fraction of what we’ve accepted as normal since the start of the computing era. Envision being able to near instantaneously create, modify or improve any process or task for governance, competitive advantage, or even just aesthetic purposes. These goals can now be achieved without adding another gazillion lines of code to each \u201capp\u201d, which only serves to spaghettify our already complex business logic nestled within. Instead, we can adopt a revolutionary approach that simplifies our software implementations, permanently.<\/p>\n

I can now foresee where service providers will provide prebuilt actions of public or private LAL\u2019s and even host and execute LAM\u2019s themselves as well (think Microservices around the most common business rulesets across all common horizontals and verticals. I mean, why are there 10,000 different codified versions of a US driving license validation when one would suffice across all enterprises? This license validation process may thus be created as a LAM, available to some or all, and each consisting of ACTIONS chosen from the LAL\u2019s. Your enterprise was never better because it has the best driving license validation, it\u2019s just more expensive to run! This quagmire of coded software is duplicated within and across millions of tasks and processes today. Each unnecessarily exists in isolation, duplicated many times over, in each and every enterprise!<\/p>\n

The world of enterprise applications we have built no longer makes sense in the GenAI era.<\/span><\/h3>\n

To be clear, most enterprise applications still in use today were written logically (often illogically) to make data calls (transactions and APIs), describe the business logic (rules, coding, subroutines, functions), along with the conditions and branches to determine the correct order to run. Combine all that with the multi-denominations of user interfaces, squirrely logic at each layer, most likely too, encased with many modified duplicates of all the same coded capabilities, from the back end to the front end and everything in between. And there we have it, the birth (and hostage) of the legacy systems. This huge but impossible-to-measure TCO (Total Cost of Ownership) keeps being piled on just to \u201ckeep the lights on\u201d with no end in sight except more risk, more downtime, and stifling the business needs to innovate and lead. This is our \u201centerprise apps\u201d, with old school code.<\/p>\n

A little side history lesson: Before \u201capps,\u201d users would simply log in to access a \u201csystem\u201d or \u201crun a program.\u201d But when we started building richer UIs, we suddenly felt the urge to lump it all together and coined the phrase \u201capps,\u201d a term that has stayed ever since.<\/p>\n

Is there a NoAPP for that?<\/span><\/h3>\n

In reality today, primarily outside of the enterprise, we have turned full circle as consumers may only just consider apps, an \u201capp\u201d, when they download something first (often from an app store!). Is the browser itself an app or a browser? Is Facebook running in a browser an app or is it only an app when it\u2019s running ON a phone? There\u2019s an app for everything \u2013 but is there really? With ACTIONS, LAMS and LALs, perhaps nothing is really an application until it\u2019s consumed and presented with a UI. The introduction of NoAPPS software? Food for thought.<\/p>\n

Successful LAMs will pave a sustainable path for the future of technology<\/span><\/h3>\n

LAMs could even be construed to represent the renewable energy revolution within the software development industry. Just as the shift to renewables offers a path away from the harmful emissions that threaten our planet, LAMS (NoAPPS) promises to move us beyond these ‘Legacy Gases’; the outdated, inefficient duplicated practices that suffocate innovation and progress within our field. This approach not only mitigates the risk of internal stagnation but also revitalizes our industry by reducing the dependency on cumbersome and polluting legacy systems. By embracing ACTIONS, LALs and LAMs, in a NoAPP era, we are choosing a sustainable future, one where software \u201cdevelopment\u201d is cleaner, more efficient, and infinitely more adaptable\u2014ushering in a time where our industry’s growth is no longer at odds with the health of its ecosystem. See what we did there? Green NoAPPS? But it\u2019s important, because our current legacy systems are beyond recyclable, though our future ones don\u2019t have to be!<\/p>\n

Why have we not really achieved this before? For sure we tried! 3GL\u2019s, 4GLS, lowcode\/nocode, Rapid Application Development tools and model application development. And even, dare I say it, object-oriented programming to drive reuse! But to be fair, all of these great concepts were often long before their time, constrained by memory limits, CPU power, storage and networking bandwidths to name a few. Our coding became atrocious, through no fault on any individual, but by the desire to not get left behind. so we are out of excuses for the new future of software. This is why we need to rebrand software development that can easily adapt to any current or future desired outcome. Hooray for NoApps and LAMS consuming ACTIONS from libraries to create the sustainable autonomous enterprise and the dream of the OneOffice.<\/p>\n

Setting standards for the NoApps revolution<\/span><\/h3>\n

The first part of this new paradigm is to capture any process and task detail in some form, into an agreed standard, albeit a new open standard or unique to you (thought I don\u2019t encourage the latter). You also need to capture the variations and the rules (separately). No programming or tech speak necessary unless you want it (because you will always want it easily explainable!). \u00a0Once captured, in whatever form we desire, with all of the variations and business rules, they will be consuming, ready for translation into ANY desired execution format, even code. \u00a0Remember, these ACTIONS, that go into the Library (LALs) can be small (the execution of the simplest of tasks), or grouped into LAMs for more complex needs. These actions and the models they are consumed by, will always be the core of what you need for your business to run and evolve, albeit for true end to end execution or an app. Apps are born of the NOAPPS description, only if required, not the other way around.<\/p>\n

In this methodology, you actually do not even need to know how ACTION descriptions will be consumed. Will they be used by an application? An API? An AI call? It doesn\u2019t matter yet because these things don\u2019t change based on the use, that\u2019s where we went with legacy coding. Each action would 100% describe what needs to be done, and can even run and be tested standalone in many cases. And cleverly, when something that already exists, is detected (by AI), it will be reported and attempt to force the reuse (or logically split into multiple inheritable actions)! The goal must be to never have two copies of the action, model or rule but rather, now it should be added to the broader library for the business to consume, and now, with AI, automatically. Actions will tracked as to where they reside and run (think always on mining here). When a change is made to a now encapsulated ACTION or LAM, process, or task, it can transition easily upstream to live, post-testing.<\/p>\n

What about the database and what about the UX I hear you ask. They are irrelevant for the implementation of NoAPPS going forward. ACTIONS and ACTION MODELS should no longer be tied or locked into either. You will regret it. We are not living in the 80\u2019s where indexing and storage sacrifices were mandatory before software design! Standard for the consumption and runtime executables will be encryption, roll-forward, roll-back, transaction reliance, smart locking, reporting et al. Just as with the cloud, so many upstream guardrails become automatically inherited and trusted.<\/p>\n

Bottom-line: Technology\u2019s future is about driving actions that you define.\u00a0 You are the outcome, and the tech must be invisible<\/strong><\/span><\/h2>\n

Some in IT, or even business, might argue that they need their own unique version of these ACTIONS, but I submit that they don\u2019t.<\/p>\n

They may need variations in rules and flows but to hard code them will become sacrilege. Most enterprises already use the same cloud vendor as their competitors, the same security and encryption as their competitors, and the same browser or mobile access device. \u00a0Do you care which insurance company you use to cover your home and car?\u00a0 Probably not, you just need an action (when you need it) at a reasonable price.\u00a0 It\u2019s becoming the same with technology\u2026 it is a means to an action, not the action itself.<\/p>\n

The days of which one you choose giving you the competitive edge are dead. It’s irrelevant for most. And if this last holy grail of software and application development is where your business wants to hang its hat, then even if someone notices and applauds you for it, it might just very well be your most costly downfall.<\/p>\n","protected":false},"excerpt":{"rendered":"

Has there ever been a time when we’ve challenged the ever-increasing stranglehold enterprise applications and their codebase have been inflicting…<\/p>\n","protected":false},"author":3,"featured_media":5769,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[867,959,49,1014,1092,1192,1043,1220,833],"tags":[968,151,1015,1215,1216,1052,1119,1195,1213,1159,1212,619,1196],"organization":[],"ppma_author":[1198,19],"class_list":["post-5768","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-artificial-intelligence","category-automation","category-buyers-sourcing-best-practices","category-chatgpt","category-genai","category-large-action-models","category-large-language-models-llms","category-lowcode-nocode","category-oneoffice","tag-ai","tag-automation","tag-chatgpt","tag-code","tag-francis-carden","tag-generative-ai","tag-lambda","tag-llms","tag-low-code","tag-lowcode","tag-no-code","tag-phil-fersht","tag-rabbit"],"yoast_head":"\nWhy actions will eat code - Horses for Sources | No Boundaries<\/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:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why actions will eat code - Horses for Sources | No Boundaries\" \/>\n<meta property=\"og:description\" content=\"Has there ever been a time when we’ve challenged the ever-increasing stranglehold enterprise applications and their codebase have been inflicting...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/\" \/>\n<meta property=\"og:site_name\" content=\"Horses for Sources | No Boundaries\" \/>\n<meta property=\"article:published_time\" content=\"2024-03-07T15:47:50+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-09-11T11:38:28+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1792\" \/>\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Francis Carden, Phil Fersht\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@pfersht\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Phil Fersht\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/\",\"url\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/\",\"name\":\"Why actions will eat code - Horses for Sources | No Boundaries\",\"isPartOf\":{\"@id\":\"https:\/\/www.horsesforsources.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg\",\"datePublished\":\"2024-03-07T15:47:50+00:00\",\"dateModified\":\"2024-09-11T11:38:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.horsesforsources.com\/#\/schema\/person\/c4f084ff7ad43632f537b3b30918e69f\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#primaryimage\",\"url\":\"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg\",\"contentUrl\":\"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg\",\"width\":1792,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.horsesforsources.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why actions will eat code\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.horsesforsources.com\/#website\",\"url\":\"https:\/\/www.horsesforsources.com\/\",\"name\":\"Horses for Sources | No Boundaries\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.horsesforsources.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.horsesforsources.com\/#\/schema\/person\/c4f084ff7ad43632f537b3b30918e69f\",\"name\":\"Phil Fersht\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.horsesforsources.com\/#\/schema\/person\/image\/86ee0c0ac2d033eed87f327162eb27f7\",\"url\":\"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2020\/11\/phill-150x150.png\",\"contentUrl\":\"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2020\/11\/phill-150x150.png\",\"caption\":\"Phil Fersht\"},\"description\":\"Phil Fersht is\u00a0a world-renowned analyst, writer and visionary in\u00a0emerging technologies, automation, digital business models, and the alignment of\u00a0enterprise operations to\u00a0drive customer impact and competitive advantage\",\"sameAs\":[\"http:\/\/hfsresearch.com\/team\/phil-fersht\",\"https:\/\/www.linkedin.com\/in\/pfersht\/\",\"https:\/\/x.com\/pfersht\"],\"url\":\"https:\/\/www.horsesforsources.com\/author\/phil-fherst\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Why actions will eat code - Horses for Sources | No Boundaries","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:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/","og_locale":"en_US","og_type":"article","og_title":"Why actions will eat code - Horses for Sources | No Boundaries","og_description":"Has there ever been a time when we’ve challenged the ever-increasing stranglehold enterprise applications and their codebase have been inflicting...","og_url":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/","og_site_name":"Horses for Sources | No Boundaries","article_published_time":"2024-03-07T15:47:50+00:00","article_modified_time":"2024-09-11T11:38:28+00:00","og_image":[{"width":1792,"height":1024,"url":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg","type":"image\/jpeg"}],"author":"Francis Carden, Phil Fersht","twitter_card":"summary_large_image","twitter_creator":"@pfersht","twitter_misc":{"Written by":"Phil Fersht","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/","url":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/","name":"Why actions will eat code - Horses for Sources | No Boundaries","isPartOf":{"@id":"https:\/\/www.horsesforsources.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#primaryimage"},"image":{"@id":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#primaryimage"},"thumbnailUrl":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg","datePublished":"2024-03-07T15:47:50+00:00","dateModified":"2024-09-11T11:38:28+00:00","author":{"@id":"https:\/\/www.horsesforsources.com\/#\/schema\/person\/c4f084ff7ad43632f537b3b30918e69f"},"breadcrumb":{"@id":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#primaryimage","url":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg","contentUrl":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/03\/Actions-eating-Code.jpg","width":1792,"height":1024},{"@type":"BreadcrumbList","@id":"https:\/\/www.horsesforsources.com\/why-actions-will-eat-code_050724\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.horsesforsources.com\/"},{"@type":"ListItem","position":2,"name":"Why actions will eat code"}]},{"@type":"WebSite","@id":"https:\/\/www.horsesforsources.com\/#website","url":"https:\/\/www.horsesforsources.com\/","name":"Horses for Sources | No Boundaries","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.horsesforsources.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.horsesforsources.com\/#\/schema\/person\/c4f084ff7ad43632f537b3b30918e69f","name":"Phil Fersht","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.horsesforsources.com\/#\/schema\/person\/image\/86ee0c0ac2d033eed87f327162eb27f7","url":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2020\/11\/phill-150x150.png","contentUrl":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2020\/11\/phill-150x150.png","caption":"Phil Fersht"},"description":"Phil Fersht is\u00a0a world-renowned analyst, writer and visionary in\u00a0emerging technologies, automation, digital business models, and the alignment of\u00a0enterprise operations to\u00a0drive customer impact and competitive advantage","sameAs":["http:\/\/hfsresearch.com\/team\/phil-fersht","https:\/\/www.linkedin.com\/in\/pfersht\/","https:\/\/x.com\/pfersht"],"url":"https:\/\/www.horsesforsources.com\/author\/phil-fherst\/"}]}},"authors":[{"term_id":1198,"user_id":0,"is_guest":1,"slug":"francis-carden","display_name":"Francis Carden","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/?s=96&d=mm&r=g","job_title":"","first_name":"","last_name":"","user_url":"","description":""},{"term_id":19,"user_id":3,"is_guest":0,"slug":"phil-fherst","display_name":"Phil Fersht","avatar_url":{"url":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/02\/Phil-Fersht-HFS-Updated.jpg","url2x":"https:\/\/www.horsesforsources.com\/wp-content\/uploads\/2024\/02\/Phil-Fersht-HFS-Updated.jpg"},"job_title":"","first_name":"Phil","last_name":"Fersht","user_url":"http:\/\/hfsresearch.com\/team\/phil-fersht","description":"Phil Fersht is\u00a0a world-renowned analyst, writer and visionary in\u00a0emerging technologies, automation, digital business models, and the alignment of\u00a0enterprise operations to\u00a0drive customer impact and competitive advantage"}],"_links":{"self":[{"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/posts\/5768","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/comments?post=5768"}],"version-history":[{"count":0,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/posts\/5768\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/media\/5769"}],"wp:attachment":[{"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/media?parent=5768"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/categories?post=5768"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/tags?post=5768"},{"taxonomy":"organization","embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/organization?post=5768"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.horsesforsources.com\/wp-json\/wp\/v2\/ppma_author?post=5768"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}