A recipe for massive technical debt: π π« Throw a large number of...
A recipe for massive technical debt: π
π« Throw a large number of developers at an empty project...and tell them to hurry.
π« Don't bother with communication, planning, or collaboration. We don't have time for that.
π« Give them no clear technical guidelines or direction. Assume they'll figure it out.
π« Skip types. Assume we can move faster in a "dynamic, fast-paced environment".
π« Ignore key aspects of quality like security, performance, accessibility, readability, and reuse. Assume we can tack those on at the end.
π« Skip reviews / pairing. Assume whatever everyone writes is fine.
π« Donβt configure CI, source control, testing, formatting, or linting up front. Assume weβll do these things later.
Good luck.π€
The solution? Build in quality from the beginning.
β Clear technical vision
β Robust communication
β Thoughtful planning and pre-work
β Automate quality checks at the start