Raise your hand, if your favorite dev task is refactoring. I'm guessing it hasn't been historically, but I'm hopeful that will change.

In this issue of CodeSee Product New-See, we'll cover 4 steps for ensuring your refactor is a success:

  1. Explain your refactor with a Product Tour
  2. Use Review Maps to tame your refactor
  3. Chart your refactor progress with Service Maps
  4. Keep your refactor on track with Code Automation

Want this content delivered straight to your inbox? Subscribe for CodeSee Product New-See.

Step 1. Explain Your Refactor with a Product Tour

To plan your refactor, start with a codebase map and label the parts that need to be refactored.

Walk teammates through your planned refactor with an interactive code tour.

Then add an interactive code tour to walk teammates or even your leadership team through your change. Click on the map to explore the tour our dev team wrote when they were planning to refactor our VSCode Extension.

Learn how the P.volve development team achieved complete alignment on their 13,000 line refactor in 30 minutes using CodeSee.

Step 2. Use Review Maps to Tame Your Refactor

Ever faced a 600-file code review? You can use review maps to get the lay of the land. Focus on changes and work through files in a logical order versus alphabetically.  

Sven Dowideit uses CodeSee on a 600-file refactor PR

New to Review Maps and Product Tours? One of our developers created a Review Map product tour to help you get your bearings. Check it out.

Read more about visually explaining code reviews with tours >>

Got refactoring questions? Our CodeSee Community has answers. Visit our Forum today.

Step 3. Chart Your Refactor Progress with Service Maps

With service-layer visibility, keeping track of all your new microservices doesn’t have to be a chore. Automatically visualized connections between services–and linked to the code–ensures everyone understands your services and sees how your migration is progressing.

Service Map with 3 Flows Highlighted
Sign up for our next Service Maps cohort today and work across services as easily as you work across files.

Step 4. Keep Your Refactor on Track with Code Automation

Sooner or later, as you refactor, you're going to face change conflicts. You can get ahead of this by using code automations (available with Business or Enterprise plans) to curate your code review process.

Block code changes during a refactor with Code Automation

Read Refactoring and the Monolith-to-Microservices Migration: Code Automation for the Win to learn how you can use Code Automations to:

  1. deprecate old code during and after your refactor
  2. assign reviewers
  3. generate checklists
  4. enforce your refactor
  5. add comments

Subscribe for more CodeSee Product News.

Move from a monolith to a microservice architecture in 5 steps. Download Monolith to Microservices: A Quickstart Checklist today.
RSVP for our founder-to-founder chat Wednesday 3/22/2023 at 9AM PT: Code Visibility from Day 0.