Port IO

Today we launched Port Insights. Our newsletter explains what's inside, and why tracking engineering metrics in the portal is the right thing to do. Read inside for some great resources on Insights, working agreements, engineering standards in the portal and how to make it all actionable.

Measuring engineering performance is no mean feat. It’s no wonder that even the brightest brains in our industry are constantly striving to find the best way to do it. At Port IO, we believe no one size fits all - engineering leaders have unique needs. That's why we're launching Insights today. It allows you to leverage the data in Port to start tracking the metrics you care about - whether it’s DORA metrics or a variation of the SPACE framework. But it can do so much more! Drill down into developer productivity and track things like: 📊 Build duration 👐 PR open to close 💻 PR size  📉 Track your compliance with your organizational standards over time ✍ Check your developers’ onboarding time 💲 Track the cost of your dev environments You get the point! And the best part? You can use automations and self-service actions in the portal to immediately make the changes that drive better performance. Read more about it in our post - link in the comments.

Checkmarx's engineering team was drowning in tickets, it had 5 methods for spinning up environments, resulting in higher complexity and costs. By implementing an internal developer portal, the team saved hundreds of thousands of dollars on developer environments, giving developers autonomy and reducing complexity. Noam Brendel explained how the team was able to create an end-to-end experience with Port IO for developer environments, which looks like this: 🛠️Using a self-service action to create an environment 📊 Seeing all relevant information about the environment in the software catalog ⏳ Requesting an extension of the TTL using a self-service action 🤖 Using an automation to destroy the environment when the TTL expires 🗑️ Using a self-service action to delete any environment that is no longer required Read the full case study, here: https://hubs.la/Q02NgkWW0

🚀 Join Us in London for a Developer Portals Meetup on September 25th! 🚀 We're hosting a first London meetup about internal developer portals and what platform engineers do with them at Port's London office. The meetup will be focused on enhancing internal developer experiences. Whether you're into platform engineering or developer experience, this is a must-attend! 🕠 Agendas: 17:30 - 18:00: Welcome & Drinks 🍻 18:00 - 18:30: Understanding portal user needs: a practical approach with James D., Head of Platform Engineering, Xceptor 18:30 - 19:00: The future of developer portals – a panel about real-life portals with Jennifer Riggins, Maria Lepp (Port IO), and James Daniels 19:00 - 19:30: Internal developer portal walkthrough with Sébastien Blanc Come for the insights, stay for the networking! 📍Location: Port Offices, London

Lightweight API governance improves the developer experience for developing new APIs. This approach asks: 😁Are developers happy? 📉Are costs reduced? ⚡Is time to market fast? Using an internal developer portal can help organizations to implement this approach by enabling devs to: - Get context through a global API catalog - Have clarity on standards - Gain autonomy through self-service actions - View the latest open feature requests - Use insights from API analytics insights for decision-making Aidan O'Connor explains all in this article on The New Stack here: https://hubs.ly/Q02Ml4HP0

“Swiper, No swiping!”

In our latest article for The New Stack, Aidan O'Connor explains five key ways you can use a portal to help implement and encourage InnerSource. They are: 🏅 Ensuring 'trusted committers' for each service are known and rewarded 🔍 Boosting discoverability via the software catalog 📩 Requesting access to the right person via a self-service action 🛠️ Creating new services that are InnerSource-ready using a self-service action 📊 Grading and monitoring compliance with InnerSource standards through scorecards Read the full article - link in the comments!

🚨 Event Announcement 🚨 We're thrilled to announce our inaugural Developer Portal Meetup in London! If you're eager to deepen your knowledge of platform engineering, enhance developer experience, and gain insights into internal developer portals, this is the perfect event for you. Sign up here to come along: https://hubs.la/Q02MVC8N0

Nobody will remember: - Your salary - How many days you came in to the office each week - How many hours you worked People will remember: - You made Developers self-sufficient - You made Developers love DevOps - You made DevOps love Developers

Lightweight API governance improves the developer experience for developing new APIs. This approach asks: 😁Are developers happy? 📉Are costs reduced? ⚡Is time to market fast? Using an internal developer portal can help organizations to implement this approach. Aidan O'Connor explains how in our latest article on The New Stack. (With thanks to Mark Boyd, who talked about the concept at Portal Talks 2024) Link for the article is in the comments!