pov: working on that one legacy codebase

@annoyinglysaucy

9.7K followers · usually 9.2K views a post

Views

72.0K

Likes

6.0K

Comments

73

Shares

754

Why it worked

The video uses relatable humor and a common pain point for software engineers (legacy codebases) to create engaging content. The "point of view" format and exaggerated scenarios resonate with the target audience, leading to high engagement.

Summary

A software engineer humorously describes the struggles of working with a legacy codebase. They highlight issues like the lack of tests, outdated branches, and a complex user creation process that requires multiple attempts to function correctly.

Structure

1Introduction to the legacy codebase problem
2Questioning the absence of tests
3Difficulty in finding the original developer
4Outdated branching strategies
5Unreliable code execution
6Complex database synchronization and user creation
7Long pipeline times and testing in production

On-screen text

pov: working on that one legacy codebase where are the tests? yeah good one the last guy who worked on this left the company 5 years ago let me see if I can email him main and master haven't been used in years you gotta pull from "stable/temp" you gotta run it like 8 times for it to work usually on like the 9th or 10th try it'll give you the bearer token logging? it's all on paper yeah do you want logs for yesterday? whenever you call get user it has to sync between our six different databases and it creates a new user every single time okay when the pipeline finishes in about 18 hours we should be good to test in production of course

Original caption

waiting 18 hours to check if your changes work👍🏽 #softwareengineer #sf #bigtech

More from @annoyinglysaucy

Their other posts in the index, biggest breakout first.

Transcript

where are the tests? yeah good one. the last guy who worked on this left the company 5 years ago. let me see if I can email him. main and master haven't been used in years. you gotta pull from stable/temp. you gotta run it like 8 times for it to work. usually on like the 9th or 10th try it'll give you the bearer token. logging? it's all on paper yeah. do you want logs for yesterday? whenever you call get user it has to sync between our six different databases and it creates a new user every single time. okay when the pipeline finishes in about 18 hours we should be good to test in production of course.