✍️ Promyze's blog

Good technical documentation appeared for the first time in the DORA report in 2021, as it’s observed foundational for successfully implementing DevOps capabilities. Technical documentation covers a large diversity of topics, among them: Architectural diagrams, business logic descriptions, … Procedures on how to do a fresh setup for a project on your laptop Coding standards and

InnerSource is an approach inspired by OpenSource, but applied to the scope of a company only. Many of these companies do not want to see their code revealed publicly for confidentiality reasons for example. Thus, InnerSource offers them the benefits of OpenSource, i.e. collaboration, innovation, and improvement, without opening the doors of their source code

The IT Industry has one of the highest turnover rates, with an average of around 15% in the past years. We can’t ignore this phenomenon, and even though you invest in increasing the retention of your tech teams, people will sometimes desire a new challenge. A reasonable strategy would be to consider both people’s wellness

IntelliJ IDEA stands as one of the most popular IDEs when developing Java code. It’s pretty tedious to have accurate numbers, but we can reasonably assume that it belongs to the two top leaders with Eclipse around the world. Btw, Keep in mind that this post content also works for Eclipse. Today we cover how IntelliJ

❓Why does onboarding matter? The software industry has one of the highest turnover rates globally, 10-15% on average in past years. Thanks to organic growth or fundraising, several digital companies significantly increase their teams every month. In that context, developers leaving or joining a team happens regularly, and the onboarding process of software engineers is

Technical debt is a term that many software engineers have already heard, but on which they have divergent definitions. In most cases, it refers to: Issues that developers face when working on their source code, impacting their organizations’ business. Technical decisions made in the past that currently impact software maintenance and evolution. Time spent on

Developers who practice code review sometimes feel lassitude and frustration when they repeat the same concepts and best practices in their comments. Code review is also about educating developers, so this observation is quite natural and part of the process. Still, there’s a gap to fill to optimize the overall code review and knowledge sharing process

If you have several software development teams in your company, maybe you’ve already heard: “Our teams don’t talk to each other” This situation happened more than once with our customers at Promyze. Companies have brilliant engineers in their teams that work on complex challenges every day. Still, sometimes they feel frustrated because they lack interactions,

Our motivation at Promyze was to have an overview of “what’s a typical public PR on GitHub ?”. This platform is used today by a large panel of organizations: single developers for their side projects, private companies, open-source organizations, universities, and so on. Our purpose is not to highlight data on PRs management in private companies, with teams working

Working efficiently as a team on a software project requires strong communication and definition of coding standards and best practices. A best practice is a rule that should be applied in your project, and it might target any topic: a programming language, a framework, security, performance, architecture, etc. A best practice for you is probably