I am not familiar with technical debt but what I know is that it is something you cannot avoid. Especially when we are in a world to push out software features as much as possible.

Since it is unavoidable, the next important step is to plan for it. Have processes set up to flag it out and manage it, for  instance, every week a time period for code reviews or clearing it, bootstrapping, documentation, etc.

Another thing, shared by my good friend and co-founder on a lot of initiatives together, Thia Kai Xin, is that we need to be smart about it. Understand the strengths and weaknesses of the team and incur technical debts that the team can manage easily. This will still mean that you need accompanying processes  to continuously manage it.

It's a great point thus I decided to share it with my readers especially most of you are in the data space and have to push scripts to the development environment.

For  the less experienced data professionals, just a point to note. These are seldom taught in programs and bootcamps, so the best way to learn about it is to be thrown to the deep end of the pool, however, you still  can read up a bit on other people's experience sharing and think about how you will manage it so at least you are prepared to a certain extent for what is to come.

Thanks for taking the time to read till here. Please feel free to link up on LinkedIn or Twitter (@PSkoo). Do consider signing up for my newsletter too. Thank you!