The acquisition of Emerson by Fullscript represented a major shift for our newly combined engineering teams. Previously, the developers at Emerson were skilled in using C#, PHP, and Angular — technologies foundational to the Emerson/Wellevate platforms. This transition, however, introduced them to a new set of challenges as they were tasked with learning Ruby, Ruby on Rails, and React, which are core to Fullscript’s application.

Transitioning to new technologies can often be a source of stress and anxiety. In this post, I aim to share how we’ve navigated these challenges, the outcomes of our efforts so far, and our ongoing journey in this dynamic environment. I will also discuss how the creation and adherence to sound engineering practices, Development Experience, and quality enabled success. Additionally, I will share how these investments make acquisitions and technology pivots to new stacks less daunting.

The Necessity of Learning New Languages Adapting to CI/CD and “Duck-Sized MRs”

Following the acquisition, it was evident that Fullscript had significantly invested in refining its technology and culture. With an ethos emphasizing speed and quality, supported by a robust CI/CD pipeline, the Emerson team needed to adapt swiftly. One major shift was adopting the practice of making ‘as close to 0 line change as possible’ — a stark contrast to their previous approach of managing complex, long-lived feature releases.

Another focus was on quality, addressing it where it is easiest and least expensive to manage. Fullscript’s quality standards start at the development stage, where automated unit tests are a requirement for merging code. We hold testing parties with business stakeholders to provide confidence in our work. This approach marked a pivot from a traditional quality process that leveraged automation but was far less iterative and could take weeks to complete.

While the team was familiar with using feature flags, the concept of having code live in production as soon as it’s merged was both exhilarating and, admittedly, a bit daunting. This integration was about more than just maintaining their roles; it was crucial for contributing effectively in their new environment. Ruby on Rails, which favors a convention over configuration philosophy, offered a drastically different experience from what many Emerson developers were accustomed to. This transition represented not only a technical upgrade but also a strategic move to synchronize development processes and merge financial and operational practices.

Confronting Imposter Syndrome and Anxiety

The shift to new technologies naturally triggered anxiety among Emerson’s developers. Many battled imposter syndrome, feeling inadequate among more experienced peers and worried that their unfamiliarity with Ruby on Rails might become a liability. The challenge of mastering a new language while proving one’s value in a new company can indeed be daunting. Such emotional hurdles are often as significant as the technical challenges themselves.

An intangible we had working in our favor was the strong desire we had to work better and smarter. To leverage good software development practices to free up engineers to focus on the solution without being dragged down by encumbrance.

This was where Fullscript’s deep investment in its culture truly made a difference. In an environment where community and grit are core values, and where failure is accepted as a part of growth, the newly combined teams began to thrive. Supported by unlimited access to learning materials, and continuous engagement through peer programming and embedding, the initial anxiety started to dissipate. Successes began to accumulate, gradually transforming the distinct Emerson identity into seamlessly integrated Fullscript pods.

Case Study: A Developer’s Journey

P. Wudgy, an Emerson engineer, illustrates a success story in this transition. As with any acquisition, initially there was some lack of clarity. What should I learn first and where should I invest my time? What about the responsibilities I had yesterday? I still have work to complete and customers to deliver for.

We took time to figure these things out and find a balance. One of the strong values we established at Emerson was mutual investment. We committed to invest in each teammate as much as they invested in themselves. This created an environment where one team member would work extra hard to ‘buy the air cover’ for another team member to learn. Fullscript at the same time built a culture of learning. They established programs for training, learning guilds delivered by peers, and provided stipends for independent learning.

Add in curious minds, amazing peers and a can-do attitude lots of grit and resilience and amazing things will happen. And that’s exactly what we did. We rotated people into and out of the training focus through embedding in teams. Before long we had a fully cross trained Pod taking on their own missions.

Effective Strategies for Transitioning to a New Tech Stack

• For software developers facing similar transitions, here are some effective strategies to ease the process:
• Realize that learning is an investment in yourself: Everything you add to your skills ‘Portfolio’ will make you a better engineer, increase your ability to have an impact, and advance your career.
• Leverage tools and technology. The use of AI tools like Copilot and GPT 4 enabled faster adaptation and best practice.
• Attitude is everything: be curious, stay open-minded, become a sponge of information. Demonstrate grit. Take on hard challenges, and the ‘grunt work’; it’s through that difficulty that you will evolve. Reach high, learn to embrace mistakes and the lessons that come with them.
• Structured Learning Path: Start with foundational courses and progressively tackle more complex applications. Find online outlets to supplement learning.
• Peer Learning: Engage in code reviews and pair programming with peers who are proficient in the technology you’re adapting to. This not only speeds up the learning curve but also helps to build relationships.
• Open Communication: Regularly communicate with your tech leads about your learning progress and challenges you face. Transparency will build trust.
• Wellness Checks: Acknowledge and address mental health aspects such as anxiety and imposter syndrome. Take care of yourself and your teammates and be there for one another.

Conclusion

The acquisition of Emerson by Fullscript is more than a corporate integration — it’s a cultural and technological assimilation. For Emerson’s developers, learning Ruby/ROR is a gateway to new opportunities and a testament to their adaptability and resilience. By embracing the new technology, they are not only ensuring their relevance in a merged company but are also paving the way for personal and professional growth. Through education, support, and perseverance, they turn the challenges of today into future achievements.

I’m grateful for the opportunity to witness my teammates thrive and I’m proud of their growth. I’m honored to be part of an organization that is committed to creating a technology ecosystem that delivers for the business but also delivers an environment for engineers to thrive. Most of all I am proud of the team that did not let change and challenge get them down and instead dug-in and GSD.