In this article, we will examine common monorepo challenges and show how Bazel helps turn a large codebase into a more manageable, efficient ecosystem. Also, we included a link to a working repository where the ideas described here are implemented.
Companies, especially mid-sized and larger ones, face the challenge of structuring projects at scale. Arguably, almost every technology and paradigm can be used by a single developer to write a small piece of code, but obviously, this is not enough for any organization—engineering solutions must allow people from multiple disciplines to develop and maintain the application efficiently throughout the whole application lifecycle.
Platform engineering builds Internal Developer Platforms (IDPs) to simplify infrastructure management, improve developer experience (DX), and boost productivity through self-service capabilities.
Being software engineering consultants we have a unique perspective on how different developer experience tools work with our client’s tech stacks. We have gathered a collective experience of our engineers and prepared this list of 9 developer experience tools that our clients and their developers found helpful.
Code organization is easy when work is done in a small team, and the codebase is not yet extensive. However, as the project's scope grows and new sub-teams appear, the question of how to subdivide and manage the growing codebase becomes increasingly important.
This article will guide you through a notable subset of Bazelʼs querying features backed by examples. These are useful for debugging, exploration, and tooling. We’ll start with basic Bazel queries with target patterns, then we will move on to demonstrating Bazel aquery and cquery.
The micro frontend architecture gives engineering teams flexibility in developing and maintaining different parts of the application. However, this comes with drawbacks, such as an increased total size of the code and an additional layer of complexity. In this article, we will go through the pros and cons of this architecture and share our recommendations for implementing it in your project.
Developer Experience (DX) has emerged as a crucial factor in the success of any software development project. At its core, DX represents the overall happiness, productivity, and ease with which developers can create high-quality work. But how can you truly measure the DX of your project?
There is more than one way to build a micro frontend architecture. The most sensible, and popular, is via the appropriate framework. If you're short on time, here's our quick take: single-spa is likely the framework you'll want for your project right now. It is light, fast and reliable.
Learn the key indicators and strategic steps to determine the right time for adopting platform engineering to enhance productivity and streamline operations.
Discover how internal developer portals boost platform engineering by centralizing deployment and enhancing developer experiences. Learn more from VirtusLab!
In this article, we will take a closer look at 3 IDEs, that we believe to be the best in their own right, and a few others that are worth taking a closer look at. We will explain their unique features and the types of projects for which they are best suited.
