When you get handed a repository URL and told to check out the system specs via TortoiseSVN, you naturally expect Markdown files, architecture diagrams, or at least a link to a Confluence space. Instead, the checkout log fills up with binary .xlsx workbooks—where every row and column has been resized into tiny, uniform squares to turn Excel into 100% graph paper for UI mockups.

In traditional enterprise environments, version control isn't for line-by-line diffs or pull requests; it's a glorified shared drive. Since you can't auto-merge binary spreadsheets, survival depends on manually typing revision notes into Sheet 2 and remembering to acquire a hard SVN file lock before touching a single cell. Welcome to the daily reality of legacy enterprise IT.

Transcript

Totolis: Alex, I just emailed you the repo URL. Check out the design specs locally via TortoiseSVN.

Alex: ...Wait. Did you just say design specs... and not source code?

Totolis: Yeah.

Alex: ...Wait, why are design specs in SVN?

Totolis: You're the new guy, so I'll walk you through it from scratch. Just open your laptop.

Alex: Uh... Totolis-san?

Alex: The checkout log is flying by right now...

Alex: And for some reason... every single file is an Excel workbook...?

Totolis: Were you even listening when I said we're checking out the design specs?

Alex: ...Hold on a second.

Alex: The design specs are spreadsheets? Not to mention... these are all binary files.

Totolis: So what?

Alex: If you dump binary files into version control... you can't even run a diff on them.

Alex: The commit log gives you zero clue who changed what.

Totolis: ...Yeah, obviously.

Totolis: Just open one of the files you checked out.

Alex: ...Okay, it's open. I'm looking at a cover page.

Totolis: Check the next tab. There's a changelog sheet, right?

Alex: ...Someone manually typed out a revision history in the cells.

Totolis: Good for you. Now you can track the changes.

Alex: ...Remind me again why version control systems even exist?

Totolis: Around here, it's basically a glorified shared backup drive.

Alex: ...You've got to be kidding me.

Alex: By the way... I have one more question.

Totolis: Go ahead.

Alex: Why is every single row and column resized into tiny perfect squares...?

Totolis: It's a classic Japanese IT specialty. Drawing architecture diagrams in Excel cells.

Totolis: Aren't you glad you get to experience traditional Japanese culture firsthand?

Alex: ...This is Japanese culture?

Alex: Using Excel as an IDE... to paint pixel-art specs on a spreadsheet... That's how Japan designs enterprise systems?

Totolis: I've never written a design spec in anything other than Excel.

Totolis: Forgot to mention. Whenever you edit a file, make sure you acquire a lock in SVN first.

Alex: ...A lock? Wait... what do you mean?

Totolis: You know what happens if two people edit the same file at the same time, right?

Totolis: You can't auto-merge binaries.

Totolis: So to prevent conflicts, you put a hard lock on the file beforehand.

Alex: ...So this is what purgatory looks like.

Totolis: Welcome to ENTERPRISE.

Have you ever had to maintain binary design specs in SVN, or draw architecture diagrams on Excel "graph paper"? Share your war stories in the comments!

If you enjoyed this, I post more animated skits about real-world enterprise IT on my YouTube channel: TotolisIT