{"id":12134,"date":"2026-11-21T07:59:43","date_gmt":"2026-11-21T07:59:43","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=12134"},"modified":"2026-11-21T08:01:43","modified_gmt":"2026-11-21T08:01:43","slug":"six-myths-borrowing-methods-devops","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/six-myths-borrowing-methods-devops\/","title":{"rendered":"Six Myths About Borrowing Methods From Other Fields in DevOps"},"content":{"rendered":"<p>DevOps itself is a borrower. Its core habits drew on manufacturing flow, on incident practices from emergency services and on ideas from publishing and construction. Yet engineering teams still carry a handful of stubborn beliefs about borrowing methods from other fields, and those beliefs cost real time. Here are six myths, each tested against how teams actually work, with a plain correction and a thing you can do on Monday.<\/p>\n<h2>Myth 1: &ldquo;Our work is too different for other fields to teach us anything&rdquo;<\/h2>\n<p><strong>Reality:<\/strong> the surface is different, the problem shapes are not. Air-traffic controllers manage many moving things with limited attention. A deploy queue has the same shape. Construction crews cannot pour the second floor until the first has cured, which is a dependency chain any pipeline owner would recognise.<\/p>\n<p>The useful test is to describe your problem without any technical vocabulary. &ldquo;Several people want to change the same shared thing at once, and the order matters.&rdquo; Written that way, you can ask which trade has handled it for decades. Rail signalling, kitchen stations and shared workshops all have answers.<\/p>\n<p><strong>Do this:<\/strong> take your most annoying recurring problem, rewrite it in one jargon-free sentence, and ask three non-engineers where they have seen it.<\/p>\n<h2>Myth 2: &ldquo;Borrowing means adopting the whole process&rdquo;<\/h2>\n<p>This myth kills more experiments than any other. A team hears that aviation uses crew briefings, imagines rolling out a thirty-page procedure and quietly drops the idea. But what transfers is almost never the paperwork. It is the one move at the centre: a short, spoken statement of the plan and the abort conditions before the risky step begins.<\/p>\n<p>A practical team might take exactly that, a two-minute spoken statement before a major database change, and nothing else. The result is smaller, cheaper and far more likely to survive past the second week.<\/p>\n<p><strong>Do this:<\/strong> for any idea you admire, write down the single sentence that captures its core move, then discard the rest until you have a reason to bring it back.<\/p>\n<h2>Myth 3: &ldquo;Only glamorous industries have anything worth copying&rdquo;<\/h2>\n<p>Aviation and emergency rooms get all the attention in engineering talks, but humbler fields are full of tested ideas. Libraries solved findability. Warehouses solved the problem of knowing what is where. Kitchen brigades solved the handover between stations during a rush. None of these will headline a conference, and all of them are more directly usable than a dramatic story about a cockpit.<\/p>\n<p>Dull fields are often better teachers precisely because their constraints are ordinary. A warehouse cannot hire a genius for every shift, so its methods work with average attention on a Tuesday afternoon. Your on-call rota has the same limitation.<\/p>\n<p><strong>Do this:<\/strong> visit, or at least ask about, one ordinary workplace this month, such as a depot, a print shop or a school office, and note one practice you would not have thought of.<\/p>\n<h2>Myth 4: &ldquo;If it worked there, it will work here&rdquo;<\/h2>\n<p>The reverse error turns up just as often. A method that suits a field with slow, physical change may stumble in one where releases happen daily. A checklist meant for ten items is not a checklist at thirty. Conditions matter: how costly a failure is, how often the task repeats, how many people take part, how quickly feedback arrives.<\/p>\n<p>Before importing anything, compare those four conditions between the source field and your own. If two or more differ sharply, adapt before you adopt, or treat the idea as a prompt for your own design instead of a recipe.<\/p>\n<p><strong>Do this:<\/strong> keep a tiny table with four rows, cost of failure, frequency, group size, feedback speed, and fill it in for the source and for your team before trying anything.<\/p>\n<h2>Myth 5: &ldquo;Borrowed methods slow delivery down&rdquo;<\/h2>\n<p>Teams worry that every new habit adds friction. Sometimes it does, when it is introduced without a purpose. But the better borrowed methods remove work. A short pre-release briefing costs two minutes and can save a two-hour rollback. A clean naming convention borrowed from librarians costs a day to introduce and saves minutes on every future search.<\/p>\n<p>The honest way to settle the question is to measure something simple before and after: time spent on rework, number of reopened tickets, interruptions during a release. If the number does not move after a fair trial, drop the practice without ceremony. Neither speed nor pride should survive in the face of evidence.<\/p>\n<p><strong>Do this:<\/strong> before adding a practice, name the one number you expect it to improve and the date you will check on it.<\/p>\n<h2>Myth 6: &ldquo;Borrowing is a workshop, not a habit&rdquo;<\/h2>\n<p>Some leaders treat borrowing as a workshop: run it, collect ideas, move on. In reality it is closer to a habit of attention. The most effective teams keep a standing list of practices they have seen elsewhere and review it quarterly. Most items get ignored. The ones that fit a current pain get a small trial.<\/p>\n<p>That rhythm also keeps ideas from growing stale. A method adopted three years ago may have drifted from its purpose, and the same cross-field curiosity that brought it in is what helps you notice.<\/p>\n<p><strong>Do this:<\/strong> create a shared page called &ldquo;seen elsewhere&rdquo; and ask each person to add one entry a month.<\/p>\n<h2>A worked example: the shared deploy queue<\/h2>\n<p>To make this concrete, take a team of eight engineers who share one production environment. Releases collide, people jump the line and nobody knows who is deploying. Describe it jargon-free: several people need the same shared thing, and order matters. Rail signalling has a simple answer, a token that only one train can hold on a stretch of track. The team borrowed the core move and nothing else: a single marker in the team channel that says who holds the slot, passed along when the release finishes. No new tool, no policy document. Collisions stopped within the week, which is the sort of modest, measurable result worth chasing.<\/p>\n<h2>Evidence from inside our own field<\/h2>\n<p>You can see the same pattern within technology itself. Machine-learning teams adopted release and monitoring habits from software operations, and the practice that emerged is now widely discussed. If you are curious how that crossing played out, <a href=\"https:\/\/www.cotocus.com\/blog\/the-essential-role-of-mlops-in-machine-learning-success\/\">this write-up on where MLOps fits when models have to run reliably<\/a> shows one borrowed discipline settling into a new home, and <a href=\"https:\/\/www.cotocus.com\/blog\/mlops-roadmap-a-complete-guide-for-data-scientists-and-engineering-teams\/\">a roadmap that guides data scientists and engineering teams through it<\/a> shows how the borrowed habits get sequenced.<\/p>\n<p>For wider reading across software, AI\/ML and DevOps topics, <a href=\"https:\/\/gyan.school\/\">a single-page learning portal for engineers with blog, forum and LMS links<\/a> collects entry points in one place. It is useful as a map of the territory, so you can see where other people draw lines between disciplines.<\/p>\n<h2>How to run a first trial without drama<\/h2>\n<p>Pick one myth that you recognise in your own team, and one correction. Announce a two-week trial in a single message: what will change, who owns it, which number you are watching and the day you will decide. Keep the scope small enough that nobody needs permission. When the date arrives, hold a ten-minute review, keep what worked, and jot a single sentence on the lesson, whichever way it went. Trials that end with a clear decision, in either direction, build trust for the next experiment.<\/p>\n<h2>A no-nonsense summary<\/h2>\n<ul>\n<li>Describe the problem without jargon and ask who else has it.<\/li>\n<li>Borrow the core move, not the paperwork.<\/li>\n<li>Look at dull fields as well as famous ones.<\/li>\n<li>Compare conditions before copying.<\/li>\n<li>Measure one number and be willing to drop the practice.<\/li>\n<li>Treat borrowing as a standing habit, reviewed on a schedule.<\/li>\n<\/ul>\n<p>What ties the six corrections together is humility paired with discipline. Other fields have solved cousins of your problem, and you are still allowed to decide whether their answer fits. Do both and the borrowing stops being a fad and becomes a working part of how the team improves.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>DevOps is itself a borrower, yet teams still resist outside ideas. Six myths about cross-field methods, each with a plain correction and a Monday action.<\/p>\n","protected":false},"author":37,"featured_media":12135,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[147],"tags":[],"class_list":["post-12134","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Six Myths About Borrowing Methods From Other Fields in DevOps - Cotocus<\/title>\n<meta name=\"description\" content=\"Six DevOps myths about borrowing methods from other fields, from aviation briefings to library naming, each with a plain correction and a practical next step.\" \/>\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.cotocus.com\/blog\/?p=12134\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Six Myths About Borrowing Methods From Other Fields in DevOps - Cotocus\" \/>\n<meta property=\"og:description\" content=\"Six DevOps myths about borrowing methods from other fields, from aviation briefings to library naming, each with a plain correction and a practical next step.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cotocus.com\/blog\/?p=12134\" \/>\n<meta property=\"og:site_name\" content=\"Cotocus\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-21T07:59:43+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-21T08:01:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3515417-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Nikhil Farooqui\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nikhil Farooqui\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134\"},\"author\":{\"name\":\"Nikhil Farooqui\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"headline\":\"Six Myths About Borrowing Methods From Other Fields in DevOps\",\"datePublished\":\"2026-11-21T07:59:43+00:00\",\"dateModified\":\"2026-11-21T08:01:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134\"},\"wordCount\":1341,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3515417-banner.png\",\"articleSection\":[\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134\",\"name\":\"Six Myths About Borrowing Methods From Other Fields in DevOps - Cotocus\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3515417-banner.png\",\"datePublished\":\"2026-11-21T07:59:43+00:00\",\"dateModified\":\"2026-11-21T08:01:43+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"description\":\"Six DevOps myths about borrowing methods from other fields, from aviation briefings to library naming, each with a plain correction and a practical next step.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#primaryimage\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3515417-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3515417-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?p=12134#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Six Myths About Borrowing Methods From Other Fields in DevOps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\",\"name\":\"Cotocus\",\"description\":\"Shaping Tomorrow\u2019s Tech Today\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\",\"name\":\"Nikhil Farooqui\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"caption\":\"Nikhil Farooqui\"},\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/author\\\/nikhil-farooqui\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Six Myths About Borrowing Methods From Other Fields in DevOps - Cotocus","description":"Six DevOps myths about borrowing methods from other fields, from aviation briefings to library naming, each with a plain correction and a practical next step.","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.cotocus.com\/blog\/?p=12134","og_locale":"en_US","og_type":"article","og_title":"Six Myths About Borrowing Methods From Other Fields in DevOps - Cotocus","og_description":"Six DevOps myths about borrowing methods from other fields, from aviation briefings to library naming, each with a plain correction and a practical next step.","og_url":"https:\/\/www.cotocus.com\/blog\/?p=12134","og_site_name":"Cotocus","article_published_time":"2026-11-21T07:59:43+00:00","article_modified_time":"2026-11-21T08:01:43+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3515417-banner.png","type":"image\/png"}],"author":"Nikhil Farooqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nikhil Farooqui","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#article","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/?p=12134"},"author":{"name":"Nikhil Farooqui","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"headline":"Six Myths About Borrowing Methods From Other Fields in DevOps","datePublished":"2026-11-21T07:59:43+00:00","dateModified":"2026-11-21T08:01:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/?p=12134"},"wordCount":1341,"commentCount":0,"image":{"@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3515417-banner.png","articleSection":["DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cotocus.com\/blog\/?p=12134#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cotocus.com\/blog\/?p=12134","url":"https:\/\/www.cotocus.com\/blog\/?p=12134","name":"Six Myths About Borrowing Methods From Other Fields in DevOps - Cotocus","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#primaryimage"},"image":{"@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3515417-banner.png","datePublished":"2026-11-21T07:59:43+00:00","dateModified":"2026-11-21T08:01:43+00:00","author":{"@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"description":"Six DevOps myths about borrowing methods from other fields, from aviation briefings to library naming, each with a plain correction and a practical next step.","breadcrumb":{"@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cotocus.com\/blog\/?p=12134"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#primaryimage","url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3515417-banner.png","contentUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3515417-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.cotocus.com\/blog\/?p=12134#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cotocus.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Six Myths About Borrowing Methods From Other Fields in DevOps"}]},{"@type":"WebSite","@id":"https:\/\/www.cotocus.com\/blog\/#website","url":"https:\/\/www.cotocus.com\/blog\/","name":"Cotocus","description":"Shaping Tomorrow\u2019s Tech Today","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cotocus.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50","name":"Nikhil Farooqui","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","caption":"Nikhil Farooqui"},"url":"https:\/\/www.cotocus.com\/blog\/author\/nikhil-farooqui\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/12134","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/comments?post=12134"}],"version-history":[{"count":1,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/12134\/revisions"}],"predecessor-version":[{"id":12228,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/12134\/revisions\/12228"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media\/12135"}],"wp:attachment":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media?parent=12134"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/categories?post=12134"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/tags?post=12134"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}