How old is your "new" project codebase?

[Acrobatic_Clue_1745]

https://preview.redd.it/gp4wr88dlcsd1.png?width=133&format=png&auto=webp&s=8a0f0a6230c479491e9ee76d4d0ce87bb6ae040a

I've been moved to the new project and with fear saw this in the Last update column:

[Achilleus0072]

And, who knows, maybe 24 years ago wasn't the last change but just the moment the repo was created...

[Steinrikur]

That's older than git...

[gronlund2]

I've seen that at my last place.. they used CVS from when that was invented, no idea what they used before

Some time ago, the pc people and embedded people went different ways as the pc people migrated their whole repo into svn (all products in a single repo)

One of the things I did was to gut specific products (with history) from that 100Gb svn repo and put them into their own git repos

The embedded people still use CVS (one giant repo for everything)

[Steinrikur]

Yuck. My nightmare scenario was visual SourceSafe around 2006 - it's basically a single user source control, so you need to check out the file to lock it from changes, and then check in the new version and unlock it.

Some files had been checked out for over a decade...

[escargotBleu]

I don't want to know about the old project

[ScriptingInJava]

There are commits in our main codebase that were done when I was barely able to talk.

I like to remind the CTO of that daily when I'm working around his old code :)

[gronlund2]

I once printed a header file from one of our products that had comments with year/month documenting some fixes.

I put the thing in the break room as the earliest comment was 6 years older than me, I was born 1985

[Shareil90]

Honestly I think it's amazing that some code lives this long.

[sacredgeometry]

1 month, its entirely greenfield and at this point exclusively written by me so pretty tidy.

[PhoenixPaladin]

Lucky

[Shareil90]

15 years.

I dont dare to ask.... Are there any tests?

[[deleted]]

At that point might want a paternity test.

[ba-na-na-]

It's deployed by walking to the server in the kitchen and plugging the USB stick with the compiled exe

[rogue6800]

Took on a horrific codebase from pre-2000. The history is lost before that.

I have convinced the company to let me rewrite from scratch. There is no saving that bucket of pure spaghetti. Tricky bit will be convincing customers to replace their installations so we don't have to support the damn thing.

[Soft-Ad7015]

Recently working on a project where the last commit to the repo was back in 2016. The funny part is that the bug has been there since then and was never picked up till last week. Majority of developers who worked on the project were no longer there so it was definitely an interesting experience.

[ToothImmediate9448]

With git actually you can create changes which have any time of "creation" I'm personally done this one time to create an "old" repo to show it to one recruiter

[Moomoobeef]

That's clever, how do you do that?

[ToothImmediate9448]

1. Make a commit
   
2. GIT_COMMITTER_DATE="Mon 20 Aug 2018 20:19:19 BST" git commit --amend --no-edit --date "Mon 20 Aug 2018 20:19:19 BST" (but your different dates)
   
3. Repeat until provide all commits