Random question. How do you name you Data Engineering repos?

I can tell you how I would NOT name them again: starting with any kind of identifier for a team, etc. etc.. We had "analytics-team-data-transformer" and so on as repository names. Terrible practice, is only useful for people who seldomly work with the repositories, super annoying for the actual data engineers. Another one I felt weird about: we had. "data-transformer" for quite some time. Now we had to explain to everyone all the time that it's the dbt repository. I'd say: name for what it is. Don't try to be clever about it. Make it short and useful for the people who work with it (the data engineers).

Thanks @Sven Balnojan I agree with you. I have decided to go with the rather dry name of

data-pipelines

. Short and to the point.

Good decision 😄

Thank you!