Skip to content

Commit 6f1165e

Browse files
committed
line edits
1 parent 09eb6cd commit 6f1165e

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

_includes/planning.html

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@ <h1><a id="planning">Planning your Internal Developer Platform</a></h1>
22

33
<p>It is tempting to think platform engineering has a simple, technical solution. Perhaps a YAML template for your
44
Kubernetes cluster, a script for your CI/CD pipeline, or a custom web app providing a dashboard and internal
5-
registry of templates will solve the immediate requirements. But this narrow focus misses the opportunity a platform
5+
registry of templates will solve the immediate requirements. But this technical focus misses the opportunity a platform
66
team can bring to your organization.</p>
77

8-
<p>Platform engineering means building a Developer Experience as a Service platform. A platform team is effectively
8+
<p>Platform engineering means building a DevEx as a Service platform. A platform team is effectively
99
running an internal startup, which means you are not providing a piece of software but a complete service to your
1010
internal customers.</p>
1111

1212
<p>Running an internal startup can be daunting because platform engineering teams must draw from the work typically done
13-
by dedicated engineering, support, technical writing, training, product, and design teams. However, addressing a few
13+
by dedicated engineering, support, technical writing, training, developer relations (DevRel), product, and design teams. However, addressing a few
1414
key activities early in the inception of a platform team provides a solid foundation for future growth while
1515
retaining the agility required to keep pace with high-performing DevOps teams.</p>
1616

@@ -29,9 +29,9 @@ <h2>Building your Platform Team</h2>
2929
product manager; at firms in which a platform team has existed for more than three years, this number rises to
3030
74%.</p>
3131

32-
<p>You can expect a successful platform engineering strategy to incorporate other specialized roles such as technical
33-
support, technical writers, security, and site reliability. That said, though, generalists will serve your initial
34-
platform well by being able to draw on experience from various backgrounds.</p>
32+
<p>You can expect a successful platform engineering strategy to work closely with, or incorporate, other specialized roles
33+
such as technicalsupport, technical writers, security, and site reliability. That said, though, generalists will serve
34+
your initial platform well by being able to draw on experience from various backgrounds.</p>
3535

3636
<p>The Forbes article “Generalist Vs. Specialist Teams: How To Build A Highly Creative Startup” (https://oc.to/jkdl9C)
3737
notes that the unpredictable nature of startups does not support specialization:</p>

0 commit comments

Comments
 (0)