Update 2024-05-20-enterprise-idp-maturity-hack.md

Updated .md formatting

Signed-off-by: Li-Or-Amir <[email protected]>

Author: Li-Or-Amir

website/content/en/blog/2024-05-20-enterprise-idp-maturity-hack.md

@@ -42,7 +42,7 @@ Example: soonicorn.io IDP status
 | Operations  | Managed services: VM users are only asked to declare their app as stateful/stateless and fault tolerant/intolerant. VM provisioning then spins up a spot instance configured for state reattachment and fallback or utilizes existing commitments.                        | Optimized   |
 | Measurement | Qualitative and quantitative: Within 1 year of MVP release, Dev vCPU hours increase by 30% while total Dev cloud costs only increase by 15%. Integrated FinOps tool analyzes each node to provide detailed cost attribution per project and team.                         | Optimized   |
 
-This scenario is highly relevant for enterprises, which are financially conservative by nature. For those, measurement is, above all, financial. The board is all in for engineering productivity, but it must be shown expected ROI to approve any IDP investment. In other words, an enterprise platform is expected to repay itself by saving software engineering hours or otherwise money in a direct, measurable way. Therefore**, the IDP mandate may depend on the ability to demonstrate how it saves the organization money:**
+This scenario is highly relevant for enterprises, which are financially conservative by nature. For those, measurement is, above all, financial. The board is all in for engineering productivity, but it must be shown expected ROI to approve any IDP investment. In other words, an enterprise platform is expected to repay itself by saving software engineering hours or otherwise money in a direct, measurable way. Therefore, **the IDP mandate may depend on the ability to demonstrate how it saves the organization money:**
 
 - Does it improve DORA time-centric metrics? (i.e. lead time for change, time to restore service)
 
@@ -52,7 +52,7 @@ This scenario is highly relevant for enterprises, which are financially conserva
 
  Achieving this may require the IDP to integrate both monitoring (e.g. GitLab) and guardrails for responsible cloud usage, backed by integrated tooling that applies savings techniques and visually tracks their results.
 
-**One takeaway:** an IDP can earn initial credit by generating financial value as soon as its provisional investment or adoption phase, i.e. without changing the way the engineers work. ****For example, it can enforce cost-effective cloud resource provisioning policies in the backend. The cost reduction generated by those is easily measured and understood. Thus, this so-called day-2 capability makes more sense as part of the platform’s MVP. The value they unlock might actually win the mandate to keep maturing the platform in other aspects.
+**One takeaway:** an IDP can earn initial credit by generating financial value as soon as its provisional investment or adoption phase, i.e. without changing the way the engineers work. For example, it can enforce cost-effective cloud resource provisioning policies in the backend. The cost reduction generated by those is easily measured and understood. Thus, this so-called day-2 capability makes more sense as part of the platform’s MVP. The value they unlock might actually win the mandate to keep maturing the platform in other aspects.
 
 
 ### CNoE from a platform engineering perspective
@@ -104,7 +104,7 @@ Intuitively, what’s right for your entire public cloud estate is right for an
 
 From a FinOps standpoint, you want your IDP to provide visualized cost observability and accurate usage attribution of each node’s components by label, namespace etc. This means it will facilitate collaboration between the engineering body and other cost stakeholders, FinOps first.
 
-From an activity standpoint, you want it to ****leverage discount compute (spots, RIs, SPs) and to continuously “squeeze the lemon” of each machine’s CPU, memory, storage, and network capacity. This is achievable by automating Kubernetes optimization techniques like [bin packing, rightsizing,](https://spot.io/blog/beyond-savings-overlooked-aspects-of-container-optimization/) shutdown scheduling, and dynamic storage.
+From an activity standpoint, you want it to leverage discount compute (spots, RIs, SPs) and to continuously “squeeze the lemon” of each machine’s CPU, memory, storage, and network capacity. This is achievable by automating Kubernetes optimization techniques like [bin packing, rightsizing,](https://spot.io/blog/beyond-savings-overlooked-aspects-of-container-optimization/) shutdown scheduling, and dynamic storage.
 
 **One takeaway:** Your IDP’s ideal integrated cost optimization solution has dual DevOps/FinOps qualities: On one hand, it has workable IaC integrations to automate the actions needed to lower cloud spend and minimize it going forward; On the other hand, it provides cost visibility & analysis that support cloud cost attribution and accountability.