> I work at a startup where business evolves really fast, and requirements change frequently, so it's easy to end up with big piles of code stacked together without a clear structure, specially with tight deadlines
That smells.
It sounds like the team could benefit from better stack technologies and a bit more discipline in how it is applied to solutioning.
> Enforcing some dependency rules that allow/forbid dependencies between different parts of the application.
What is the alternative to this tool that lowers the cognitive barrier / builds the right muscles for the team to understand what they should / shouldnt depend on?
> I work at a startup where business evolves really fast, and requirements change frequently, so it's easy to end up with big piles of code stacked together without a clear structure, specially with tight deadlines
That smells.
It sounds like the team could benefit from better stack technologies and a bit more discipline in how it is applied to solutioning.
> Enforcing some dependency rules that allow/forbid dependencies between different parts of the application.
What is the alternative to this tool that lowers the cognitive barrier / builds the right muscles for the team to understand what they should / shouldnt depend on?