Skip to contentSkip to content
Verified credentials. On-chain. Forever.Learn more
Ewance
Sign in
Cover image for Build a Source-to-Source Migration Tool for a Legacy API
Code

Build a Source-to-Source Migration Tool for a Legacy API

FreeVerified credential3 weeksIntermediate

Overview

What this challenge is about.

Build a Source-to-Source Migration Tool for a Legacy API. Intermediate challenge in code. Writing production code that solves real engineering problems, earn...

CredentialBlockchain-anchored
ShareableLinkedIn-ready
LanguageEnglish
PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Build a safe source-to-source migration tool that rewrites 14 v3 SDK call patterns to v4 across customer Python codebases, with zero false positives on a held-out corpus.

This is not a coding exercise. It is the work a software engineer does between a Jira ticket and a merged PR. That distinction matters to every hiring manager who has seen candidates solve LeetCode problems and none who have shipped production code under real constraints.

When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."

Earning criteria — what you'll demonstrate

  • Use a concrete syntax tree (CST) library to preserve formatting and comments
  • Write source-to-source rewrites for a real API migration
  • Measure precision and recall of an automated refactoring tool
  • Build a developer-experience tool that customers will actually run

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Aligned coursework coming soon.

One more thing

You can put a credential on your CV by Friday.