Dev Blog
Lessons learned, tips and documentation provided by the Humanitec team.
Want to contribute? Get in touch
Lessons learned, tips and documentation provided by the Humanitec team.
Leading tech organizations build Internal Platform teams to ensure end-to-end developer self-service. Platform teams build internal workflows and tooling, such as Internal Developer Platforms (IDPs), to ensure application developers are shielded from the evolving complexities of the underlying infrastructure. They create a smooth development and deployment experience for everyone involved.
When comparing products, you want to decide on their usefulness. Yet, we often forget to evaluate the project's documentation. A project might offer an excellent set of features but might lack easy-to-use documentation. This can have a detrimental effect on the developer experience and your team's efficiency. So, how do you evaluate the developer experience of documentation?
An Internal Developer Platform consists of five core components. Application Configuration Management and Infrastructure Orchestration allow developers to independently spin up fully-provisioned environments. Moreover, developers can deploy workloads and connect the required dependencies automatically. Lastly, RBAC provides Ops teams with fine-grained access control over their organization.
The DevOps approach has become increasingly complex. This puts more pressure on your Ops teams. Elite teams at companies such as Github, Airbnb, and Spotify realized that this way of interpreting the paradigm increases developers' cognitive load and decreases team velocity. Therefore, these teams started building Internal Developer Platforms (IDPs) to relieve pressure. But what is an IDP?
Many of you have probably read countless technical articles about scaling application infrastructure and capacity with Kubernetes. This is not one of those posts. Rather, it looks at how and when to implement Kubernetes when your team or the demands on your team grow rapidly.
If you want to build your applications and business on existing APIs and not reinvent all functionality yourself, how do you decide between the plethora of options available? This article helps you make that decision based on the developer experience (DX) you should expect from an API.
Software engineering involves an understanding of architecture, abstractions and implementation details. Determining what knowledge is intrinsic to a team member’s role and what is outside of their scope is critical to reduce the strain on their cognitive load. Internal Developer Platforms provide a way to compartmentalize complexity, and enable people to focus on what’s critical to their role.
An Internal Developer Platform (IDP) is an essential step for rapidly scaling companies to keep their developers working productively and happily. In this roundtable discussion we speak with Jason Warner, the current CTO of GitHub and previous VP of Engineering for Heroku about how IDPs help teams of that scale build efficiently.
German broadcaster Sport1 realized they were spending too much time grappling with an outdated deployment process, they decided it was time to build their own flexible Internal Developer Platform. Find out how it changed their development process in our roundtable with Paolo Garri, the director of technology.
An Internal Developer Platform (IDP) is an essential step for rapidly scaling companies to keep their developers working productively and happily. In this roundtable discussion we speak with Jan Löffler who helped build Zalando’s IDP about the problems they were trying to solve and the steps they took.
In this article I look mostly at improving the developer experience within a company, and touch upon other aspects where relevant, we have future articles planned to help you improve the DX of the projects you maintain. The goal of this article is to help those in charge of development teams understand what their developers struggle with and complain about and help them do something about it.
A good developer experience is crucial to keep developer teams productive, happy, and focussed on work important to your business aims. In this first roundtable, we get the opinions and experiences from two experts in the field: Nigel Simpson, Director, Enterprise Tech Strategy at a Fortune 100 company, and Erik Muttersbach, CTO at forto (formerly FreightHub), a Berlin logistics startup.
We tend to underestimate how inefficient workflows impact developer productivity and distract from the task at hand. In this article we explain the first- and second-order effects of inefficient developer workflows. We share real-life examples and analyse at what point you should invest in automation vs. doing things manually.
Why does everything always take so long? Most of us ask ourselves this question every day. In this article Humanitec’s CEO Kaspar von Grünberg shares some thoughts about developer productivity and how to improve it. 7 points about your DevOps workflow you should definitely keep in mind!