Skip to content

Blog post: "Platform Engineering: Evolution or Rebranding?" #14910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 12, 2025

Conversation

adamgordonbell
Copy link
Contributor

@adamgordonbell adamgordonbell commented May 2, 2025

blog post continuing the conversation on whether PE is a fad from reddit.

Additionally I added a simplified blog layout simple_layout: true which I think will help with reddit traction.

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

Copy link
Contributor

@dirien dirien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Feedback in slack

@pulumi-bot
Copy link
Collaborator

@adamgordonbell adamgordonbell merged commit 4975baf into master May 12, 2025
8 checks passed
@adamgordonbell adamgordonbell deleted the agb/plateng-evolution branch May 12, 2025 11:18
thoward pushed a commit that referenced this pull request May 15, 2025
* Add new blog post: "Platform Engineering: Evolution or Rebranding?"

* Fix typo and improve wording in blog post about Platform Engineering rebrand.

* Add images and update layout for blog post on platform engineering rebrand

* Add summary to blog post on platform engineering rebranding and make minor formatting adjustments

* Update blog post date and enhance content clarity for 'Platform Engineering' discussion.

* Add new images and update blog content for platform engineering rebrand discussion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants