The tools discussed in this article will give insights and a starting point on implementing a better code on your projects

Writing is a vital skill and a continuous activity for professionals working with software engineering. Whether you are creating a JIRA ticket, crafting a wiki page or composing an email, clear communication through writing is crucial for effective collaboration.

Creating Pull Requests (also referred to as: PR) is not an exception. A well structured and written pull request can be a deal breaker for launching a new feature in your team. And there is more to it than simply shipping code when contributing to the solution.

This article explores the basics of working with pull requests and the importance of writing well. We will explore the structure and the way we communicate when contributing as a software developer in a collaborative team.

Let’s dive in!

Ephemeral environments are getting popular among companies that need to scale their business efficiently. Traditionally, the deployment environments usually included development, QA, staging, UAT, and production. However, the bottlenecks with shared QA and staging environments have hindered the efficient workflow of IT teams. The first issue you will face is environment drift because it is a shared environment, and you cannot afford a separate static environment for each developer. Similarly, you cannot take valuable feedback from the product manager, QA engineer, or developers unless you merge the code and deploy it on a shared staging/QA environment. Environment setup also becomes challenging now that most applications are containerized and consist of docker, Kubernetes, and microservices.

This article will discuss Ephemeral Environments and how they solve the problems mentioned above with a simple but powerful solution. We will describe its benefits to organizations and how the modern workflow based on ephemeral environments differs from the traditional workflow. Ultimately, we will discuss how to get started with ephemeral environments.

In this article I’ll show how to store and consume Helm charts in GitLab’s private registry.

You’ll learn how to create 2 simple helm charts, called store-chart and consume-chart where store-chart will be stored in GitLab and consume-chart will consume the stored chart.

GIT — is a powerful tool for collaborating with the team and storing work that can be easily replayed in time. However, for a sad reason, a lot of people use the GUI tool for interacting with it and can’t uncover its full potential of this tool. Like in a famous meme people learn only to commit and push and if something happened, they prefer to reload copies except to solve problems. (In all cases it’s not the optimal way)

Transible - the tool which converts you cloud to Ansible playbooks, now AWS EC2 and VPC are supported (in addition to Openstack).

Introduction

Git and other version control systems give software developers the power to track, manage, and organize their code.

In modern software development, speed and agility are crucial when it comes to developing and releasing software. However, when you have a large team of developers working simultaneously, branching and merging code can become messy fast.

Therefore, teams need to have a process in place to implement multiple changes at once. This is where having an efficient branching strategy becomes a priority for these teams.