✍️ Promyze's blog

Best code review practices intend to help developers’ teams to have a great experience with code reviews. This practice has many benefits for a team. This post focuses on 5 mistakes to avoid when doing code reviews. #1 Forget to highlight well-written source code Show empathy. Developers who spent several hours/days working on a task

Knowledge sharing stands as one of the top factors that boost business excellence. In the context of software engineering, knowledge sharing is far from free and won’t be efficient until companies address the topic. Indeed: The IT sector undergoes one of the highest turnover rates in the industry, meaning onboarding needs to be efficient. Most

When defined and known by most developers, coding practices help ensure source code uniformity and quality within an organization. More globally, thanks to recent studies, we know that: knowledge sharing is one of the top factors that fuels business performance in the software industry; developers spend up to 50 % of their time answering questions

This post is part of a series of 7 blog posts on the topic How to create a learning culture for software development teams: Learning culture in software engineering teams: Motivations (1/7) Learning culture in software engineering teams: Technology watch & Coaching (2/7) Learning culture in software engineering teams: Training & E-learning (3/7) Learning culture

This post is part of a series of 7 blog posts on the topic How to create a learning culture for software development teams: Learning culture in software engineering teams: Motivations (1/7) Learning culture in software engineering teams: Technology watch & Coaching (2/7) Learning culture in software engineering teams: Training & E-learning (3/7) Learning culture

This post is part of a series of 7 blog posts on the topic How to create a learning culture for software development teams: Learning culture in software engineering teams: Motivations (1/7) Learning culture in software engineering teams: Technology watch & Coaching (2/7) Learning culture in software engineering teams: Training & E-learning (3/7) Learning culture

This post is part of a series of 7 blog posts on the topic How to create a learning culture for software development teams: Learning culture in software engineering teams: Motivations (1/7) Learning culture in software engineering teams: Technology watch & Coaching (2/7) Learning culture in software engineering teams: Training & E-learning (3/7) Learning culture

This post is part of a series of 7 blog posts on the topic How to create a learning culture for software development teams: Learning culture in software engineering teams: Motivations (1/7) Learning culture in software engineering teams: Technology watch & Coaching (2/7) Learning culture in software engineering teams: Training & E-learning (3/7) Learning culture

This post is part of a series of 7 blog posts on the topic How to create a learning culture for software development teams: Learning culture in software engineering teams: Motivations (1/7) Learning culture in software engineering teams: Technology watch & Coaching (2/7) Learning culture in software engineering teams: Training & E-learning (3/7) Learning culture

GitHub Pull Requests are useful to manage the workflow of your development with Git. Git offers a native branch management system that makes it easy to work collaboratively. Whether you’re using the Git-flow model or the Trunk-Based approach, only the lifetime branch varies: you still rely on branches to integrate new code increments. Pull Request