Some of the results, such as the percentage of people using Continuous Integration, surprised me. I can't say for sure but I have the suspicion that people confuse using a pipeline in a CI server with the practice of CI, which implies everybody integrating all their code/changes at least daily in the main branch.
I'm afraid, that less people than indicated are following this CI practice and that many simply refer to using jenkins/github actions or similar, while working using Feature Branches of several days duration.
In the DORA reports, in order to avoid these problems, they didn't ask directly if they did CI, but they asked how often they put all the code together in the main branch, or if each change triggered an automatic test suite or if they give priority to restore the build when there is an error.
I'd be interested in how UI dev is set-up in companies that have a shared frontend across teams, so central vs decentral vs hybrid setup and also how that plays together with UX people / Design System.
The tide is changing for native mobile engineers unfortunately. What I am observing is that early stage companies are using either Flutter or React Native. Even NextJS packed as PWA is an option.
Therefore, frontend team mentioned in this text (that leans to be a web oriented team with capability and knowledge to deploy mobile app) makes perfect sense.
Some of the results, such as the percentage of people using Continuous Integration, surprised me. I can't say for sure but I have the suspicion that people confuse using a pipeline in a CI server with the practice of CI, which implies everybody integrating all their code/changes at least daily in the main branch.
I'm afraid, that less people than indicated are following this CI practice and that many simply refer to using jenkins/github actions or similar, while working using Feature Branches of several days duration.
In the DORA reports, in order to avoid these problems, they didn't ask directly if they did CI, but they asked how often they put all the code together in the main branch, or if each change triggered an automatic test suite or if they give priority to restore the build when there is an error.
I'd be interested in how UI dev is set-up in companies that have a shared frontend across teams, so central vs decentral vs hybrid setup and also how that plays together with UX people / Design System.
Hey. Regarding PRs and code reviews - recently, I came across this interesting research about code reviews https://www.infoq.com/articles/co-creation-patterns-software-development/. Might be useful to share issues with PRs and code reviews.
The tide is changing for native mobile engineers unfortunately. What I am observing is that early stage companies are using either Flutter or React Native. Even NextJS packed as PWA is an option.
Therefore, frontend team mentioned in this text (that leans to be a web oriented team with capability and knowledge to deploy mobile app) makes perfect sense.