This is the first startup I'm part of (big company before that), so it's hard for me to say what's the norm in other place. From what I talked with friends in other small startups (R&D of <40 people), it's quite common to almost NEVER spend the time on deleting stuff.
Maybe it's bad habits, or bad culture, but I'm 100% sure we are not alo…
This is the first startup I'm part of (big company before that), so it's hard for me to say what's the norm in other place. From what I talked with friends in other small startups (R&D of <40 people), it's quite common to almost NEVER spend the time on deleting stuff.
Maybe it's bad habits, or bad culture, but I'm 100% sure we are not alone. And if you are already in that situtation - such an effort can help to kickstart a better way forward.
For example, we changed policies to automatically delete merged branches which was not enabled in most repos.
We added dead code analyzers that will help us identify dead code in the future.
And similar steps to avoid being in the same deep shit in the future.
It’s clear that what you’re doing to address these issues is really important.
Implementing measures like automatic deletion of merged branches and dead code analyzers is a smart approach to prevent this kind of problem from piling up again in the future.
And honestly I'm looking forward to reading more about the steps you’re taking to ensure this doesn’t happen again
I'm not sure I'm going to cover them in future articles, but in addition to those mentioned we:
- Do a weekly analysis of the cloud costs, quickly killing any anomalies and cleaning up unused resources.
- When we create a feature flag, we also create a ticket to delete it, putting it in the relevant sprint (usually couple of weeks after the release).
For the Jenkins/Kubeflow jobs and unused repositories I hope that the awareness will be enough. If we do a similar event sometime in the future, I believe that the score will be much lower :)
This is the first startup I'm part of (big company before that), so it's hard for me to say what's the norm in other place. From what I talked with friends in other small startups (R&D of <40 people), it's quite common to almost NEVER spend the time on deleting stuff.
Maybe it's bad habits, or bad culture, but I'm 100% sure we are not alone. And if you are already in that situtation - such an effort can help to kickstart a better way forward.
For example, we changed policies to automatically delete merged branches which was not enabled in most repos.
We added dead code analyzers that will help us identify dead code in the future.
And similar steps to avoid being in the same deep shit in the future.
Anton, I totally agree with you!
It’s clear that what you’re doing to address these issues is really important.
Implementing measures like automatic deletion of merged branches and dead code analyzers is a smart approach to prevent this kind of problem from piling up again in the future.
And honestly I'm looking forward to reading more about the steps you’re taking to ensure this doesn’t happen again
I'm not sure I'm going to cover them in future articles, but in addition to those mentioned we:
- Do a weekly analysis of the cloud costs, quickly killing any anomalies and cleaning up unused resources.
- When we create a feature flag, we also create a ticket to delete it, putting it in the relevant sprint (usually couple of weeks after the release).
For the Jenkins/Kubeflow jobs and unused repositories I hope that the awareness will be enough. If we do a similar event sometime in the future, I believe that the score will be much lower :)
wow, these missing explanation parts how you preventing this happening in future,
for sure must be written down in this post 💪
Yep, that's a good tip. I kind of focused only on the cleaning part, edited it now! :)