Software Executive, Entrepreneur, Software Architect
The objectives and design of the test stages in a regular, distributed team environment.
Building CI/CD pipelines seems to be one of those topics that every team seems to struggle with. There are many effects that contribute to this:
How to improve your chances of getting the kind of people you need.
Let's face it: most of the companies out there (including most of the ones I worked for) hire opportunistically. They wait until they have a specific need, then quickly put together a job description, and publish the opening in the various channels that are readily accessible, hoping that they get a fit. Most of the time they can't find what they are looking for in a reasonable amount of time, and for the right salary. There's four options available at that point:
The requirements you can see at the beginning are only the tip of the iceberg.
Every professional in the software industry knows that building software is a highly unpredictable business. This is why we don't like the question of “How long is it going to take?". The thing that always puzzled me, however, is that that unpredictability always seems to point in the wrong direction: software seems to almost always take longer to build than expected. With practically any other process, one would expect something similar to a normal (binomial) distribution around the…
A brief bio