{"id":11972,"date":"2026-11-17T08:30:00","date_gmt":"2026-11-17T08:30:00","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=11972"},"modified":"2026-11-17T08:30:00","modified_gmt":"2026-11-17T08:30:00","slug":"six-myths-about-naming-in-engineering","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/","title":{"rendered":"Six Myths About Naming Things in DevOps and ML Projects"},"content":{"rendered":"<p>Ask a room of engineers whether naming matters and most will say yes. Ask them to show the container image tags, experiment runs or infrastructure resources they named last month, and the room goes quiet. There is a gap between belief and practice, and it is propped up by a handful of myths. This article tests six common ones against what actually happens in engineering work, using concrete examples from container images, machine learning experiments and cloud resources.<\/p>\n<h2>Myth 1: &#8220;A tag like latest is clear enough&#8221;<\/h2>\n<p>It feels clear because it sounds like a promise. In practice, &#8220;latest&#8221; is a moving pointer, not a version. Two engineers pulling &#8220;latest&#8221; an hour apart can receive different images, and a rollback to &#8220;latest&#8221; rolls back to nothing. When an incident review asks which build was running at 3 p.m., &#8220;latest&#8221; cannot answer.<\/p>\n<p>The evidence against this myth is mechanical rather than opinion: a tag that changes meaning cannot identify anything. A tag built from a release number or a short commit reference can. The fix costs one line in the build script, and it makes every deployment traceable.<\/p>\n<h2>Myth 2: &#8220;Names are cosmetic; the real work is in the code&#8221;<\/h2>\n<p>Names are part of the interface. Every person who reads a repository, a dashboard or a log line meets the names first and the logic second. A variable called &#8220;x2&#8221; forces the reader to reconstruct intent from the surrounding code. A variable called &#8220;retry_delay_seconds&#8221; carries intent and the unit with it.<\/p>\n<p>You can test this on yourself. Open a piece of code you wrote six months ago and time how long it takes to understand one function. Then rename the three most cryptic identifiers and read it again. The difference is usually obvious, and no logic changed.<\/p>\n<h2>Myth 3: &#8220;Experiment names do not matter in machine learning; the metrics tell the story&#8221;<\/h2>\n<p>Metrics tell you that run 47 scored better than run 46. They do not tell you why, unless the run carries a name that records what changed. Teams that call experiments &#8220;test_final&#8221; or &#8220;run_new&#8221; end up with a tracking table full of results nobody can reproduce or explain.<\/p>\n<p>A plain naming habit helps: say what was varied, such as &#8220;baseline-with-smaller-learning-rate&#8221;, and keep the dataset version in the label. The wider practice of organising a model lifecycle is covered in <a href=\"https:\/\/www.cotocus.com\/blog\/mlops-roadmap-a-complete-guide-for-data-scientists-and-engineering-teams\/\">a stage-by-stage MLOps plan aimed at data scientists and engineering teams<\/a>, and naming is one of the quiet foundations underneath it. The reasoning behind <a href=\"https:\/\/www.cotocus.com\/blog\/the-essential-role-of-mlops-in-machine-learning-success\/\">the argument for operational rigour in machine learning work<\/a> applies directly: results you cannot trace are results you cannot trust.<\/p>\n<h2>Myth 4: &#8220;We can rename later when the project is stable&#8221;<\/h2>\n<p>The word &#8220;later&#8221; is where naming debt hides. Names spread: into configuration files, dashboards, scripts, documentation and other people&#8217;s habits. The longer a poor name lives, the more places it appears, and the costlier the eventual rename becomes. Projects rarely feel stable enough to start a rename, because the work of keeping them running always wins.<\/p>\n<p>The practical answer is that the cheapest moment to choose a name is the moment of creation. A minute spent then saves a migration project later. If you inherit poor names, rename in small, reversible steps, starting with the ones that cause the most confusion in incident reviews.<\/p>\n<h2>Myth 5: &#8220;Everyone on the team already knows what the names mean&#8221;<\/h2>\n<p>This is true on the day the names are invented and gradually false afterwards. People join, people leave, and the unwritten knowledge goes with them. An on-call rota guarantees that sometimes the person looking at a system is not the person who built it.<\/p>\n<p>A useful check is to hand a list of your service and resource names to someone outside the team, perhaps from a neighbouring department, and ask them to guess what each one does. The hit rate is your real measure of clarity. It is a cheap experiment and it produces uncomfortable, valuable data.<\/p>\n<h2>Myth 6: &#8220;Longer names slow us down&#8221;<\/h2>\n<p>There is something real in this complaint, and that is why it lingers. Very long names are tedious to type and clutter small screens. But the cost of typing is paid once, with autocomplete helping, while the cost of reading is paid by every person who meets the name afterwards. Reading wins by volume.<\/p>\n<p>The real target is not length but information density. &#8220;orders-db-primary&#8221; is short and rich. &#8220;database-server-for-the-orders-application-in-the-main-region&#8221; is long and padded. Aim for the shortest name that is still unambiguous.<\/p>\n<h2>Why the myths keep surviving<\/h2>\n<p>Each belief rests on seeing a name as the author&#8217;s private shorthand. It is closer to a shared road sign, and a road sign is judged by the driver, not the person who painted it. Nobody asks the sign painter how clear it felt. A name is read many more times than it is written, and often by people under stress. That asymmetry is the strongest argument, and it needs no statistic: anyone who has been paged at night knows which side of it they were on.<\/p>\n<h2>How to weigh the evidence fairly<\/h2>\n<p>Be careful about one trap when you run these tests: do not count only the incidents where a bad name was the proven cause. Names rarely get blamed in a post-incident write-up, because the delay they caused looks like ordinary investigation time. A better signal is the questions people ask in chat during an outage, such as &#8220;which one is the real database?&#8221; Collect a few of those from your own channels and you will see how often confusion over names slows the first ten minutes.<\/p>\n<h2>Two bonus examples worth checking in your own stack<\/h2>\n<p>Cloud resources deserve a look of their own. A storage bucket named &#8220;test-bucket-123&#8221; may hold production exports for years because nobody dares to touch it. Putting the owning system and the environment in the name, as in &#8220;reports-export-staging&#8221;, tells the next person whether deleting it is safe. Likewise, scheduled jobs called &#8220;cron1&#8221; and &#8220;cron2&#8221; hide their purpose; &#8220;nightly-invoice-export&#8221; announces it. These are cheap wins, and they tend to surface in the very first review.<\/p>\n<h2>A small experiment to try this week<\/h2>\n<ol>\n<li>Pick one system, such as a pipeline or a set of cloud resources.<\/li>\n<li>List every name in it on one page.<\/li>\n<li>Ask two colleagues to annotate what each name means without help.<\/li>\n<li>Compare their answers with reality and record the mismatches.<\/li>\n<li>Rename the three worst offenders and repeat the exercise a month later.<\/li>\n<\/ol>\n<p>The mismatches are your evidence. They turn a vague feeling into a ranked list, and that ranking decides where effort goes first.<\/p>\n<h2>Looking outward for a moment<\/h2>\n<p>Good labelling is also how public sites earn quick trust. A Gujarat events website like <a href=\"https:\/\/gujaratorbit.com\/\">GujaratOrbit, which sorts its content into events, a venue directory, a forum and a blog with matching menu labels<\/a>, makes it obvious what each section holds, and the same instinct belongs in your repositories. When a visitor, or a new engineer, can predict what is behind a label, you have named it well.<\/p>\n<h2>The takeaway<\/h2>\n<p>Hold any of the six up against a real incident review and it wobbles. Names that identify, state intent and age well are cheap to make and expensive to neglect. Test your own assumptions with the small experiment above, and let the results decide how much attention naming deserves in your team.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>From container tags to experiment runs: six common beliefs about naming in engineering, tested against what actually happens during incidents and handovers.<\/p>\n","protected":false},"author":37,"featured_media":11973,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[147],"tags":[],"class_list":["post-11972","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 Naming Things in DevOps and ML Projects - Cotocus<\/title>\n<meta name=\"description\" content=\"Six myths about naming in DevOps and machine learning projects, from the latest tag to experiment runs, tested against real incident and handover experience.\" \/>\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\/six-myths-about-naming-in-engineering\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Six Myths About Naming Things in DevOps and ML Projects - Cotocus\" \/>\n<meta property=\"og:description\" content=\"Six myths about naming in DevOps and machine learning projects, from the latest tag to experiment runs, tested against real incident and handover experience.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/\" \/>\n<meta property=\"og:site_name\" content=\"Cotocus\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-17T08:30:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1733829-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=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/\"},\"author\":{\"name\":\"Nikhil Farooqui\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"headline\":\"Six Myths About Naming Things in DevOps and ML Projects\",\"datePublished\":\"2026-11-17T08:30:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/\"},\"wordCount\":1231,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1733829-banner.png\",\"articleSection\":[\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/\",\"name\":\"Six Myths About Naming Things in DevOps and ML Projects - Cotocus\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1733829-banner.png\",\"datePublished\":\"2026-11-17T08:30:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"description\":\"Six myths about naming in DevOps and machine learning projects, from the latest tag to experiment runs, tested against real incident and handover experience.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1733829-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1733829-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/six-myths-about-naming-in-engineering\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Six Myths About Naming Things in DevOps and ML Projects\"}]},{\"@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 Naming Things in DevOps and ML Projects - Cotocus","description":"Six myths about naming in DevOps and machine learning projects, from the latest tag to experiment runs, tested against real incident and handover experience.","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\/six-myths-about-naming-in-engineering\/","og_locale":"en_US","og_type":"article","og_title":"Six Myths About Naming Things in DevOps and ML Projects - Cotocus","og_description":"Six myths about naming in DevOps and machine learning projects, from the latest tag to experiment runs, tested against real incident and handover experience.","og_url":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/","og_site_name":"Cotocus","article_published_time":"2026-11-17T08:30:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1733829-banner.png","type":"image\/png"}],"author":"Nikhil Farooqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nikhil Farooqui","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#article","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/"},"author":{"name":"Nikhil Farooqui","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"headline":"Six Myths About Naming Things in DevOps and ML Projects","datePublished":"2026-11-17T08:30:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/"},"wordCount":1231,"commentCount":0,"image":{"@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1733829-banner.png","articleSection":["DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/","url":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/","name":"Six Myths About Naming Things in DevOps and ML Projects - Cotocus","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#primaryimage"},"image":{"@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1733829-banner.png","datePublished":"2026-11-17T08:30:00+00:00","author":{"@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"description":"Six myths about naming in DevOps and machine learning projects, from the latest tag to experiment runs, tested against real incident and handover experience.","breadcrumb":{"@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#primaryimage","url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1733829-banner.png","contentUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1733829-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.cotocus.com\/blog\/six-myths-about-naming-in-engineering\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cotocus.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Six Myths About Naming Things in DevOps and ML Projects"}]},{"@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\/11972","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=11972"}],"version-history":[{"count":1,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11972\/revisions"}],"predecessor-version":[{"id":12088,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/11972\/revisions\/12088"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media\/11973"}],"wp:attachment":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media?parent=11972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/categories?post=11972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/tags?post=11972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}