From 300893cd14976602deb58eb855c34495419fe798 Mon Sep 17 00:00:00 2001 From: vele616 Date: Tue, 16 Sep 2025 14:47:54 +0200 Subject: [PATCH] chore: ante blog post quote update --- ...igrating-an-enterprise-app-from-angularjs-to-react.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/apps/website/src/content/posts/migrating-an-enterprise-app-from-angularjs-to-react.md b/apps/website/src/content/posts/migrating-an-enterprise-app-from-angularjs-to-react.md index 12ffe560..2596d742 100644 --- a/apps/website/src/content/posts/migrating-an-enterprise-app-from-angularjs-to-react.md +++ b/apps/website/src/content/posts/migrating-an-enterprise-app-from-angularjs-to-react.md @@ -95,6 +95,15 @@ While off-product work can sometimes feel fragmented or disconnected, these grou Pair programming turned out to be a highly effective method for hands-on coding support in this project. Initially, developers were hesitant to ask for help, so we took the initiative by offering guidance on new features and React. After a few programming sessions, developers started reaching out on their own, asking for support and assistance with adding new components. +
+
+

Before starting the migration, only a few of our developers had some React experience. With the help of CroCoder developers, we were able to lead the migration ourselves. They explained everything clearly, gave us confidence in the new codebase, and supported us whenever we needed.

+
+

+ — Florian Le Dentu-Jost, Senior Software Developer at sevdesk +

+
+ ## The Turning Point When it comes to large initiatives and changes, it may take some time to see the fruits of your labor, but that doesn’t mean you are on the wrong track. Our efforts proved effective when two developers from the same team reached out to us requesting new components. Unlike before, when such tasks were assigned to the Core team, they now wanted to build the components themselves with our support. This was a huge step forward, as it showcased the willingness and motivation of the developers to start coding in React and participate in the migration. After a few pair-programming sessions, the first components not created by the Core team were added to the new component library. Because of this, the two developers continued working on maintaining these components independently.