Was reading a very interesting rant, and then devRant crashed 🤨
(Am I supposed to post rants here?)

Looking at code in our workplace.. I realized one thing. Like Devops, legacy code is actually a mindset.

So here goes my thought:

A piece of code is not legacy because it was written ten years ago.

A piece of code is legacy because it looks like a piece of legacy code.

With the legacy code mindset, you end up writing legacy code no matter where you are, when you wrote it.

I was looking at some part of our code which we written in just the last few months, and I can’t help but think that they were legacy, so it really doesn’t matter when it was written!

It is more about how you write your code that determines whether it is legacy :)

Hopefully this was not crazily confusing anyone. Have a good day guys & gals!

Guys, I think they are asking about Big Data Loss. People thought it's about Data Loss.

My Big Data Loss experience is when everyone in Hong Kong starts talking about big data using spreadsheets. So lost.