The bigger fails I've found in my dev career are over-architecture. Devs that though they were able to ideate quasi magical architectures that handle every single use case and adapt to any future changes. The result: very custom architectures that force devs to do things in weird and complex ways and get outdated as soon as the promoter leaves the company. Everything becomes slow and devs get frustrated. Many projects are already using the architecture and it turns very difficult to remove.
My advice: choose between the existing architecture options and stick to the standard as much as possible. Use existing tools and keep them up to date. Innovate in architecture only if your company has a specific interest in the architecture itself and they want to invest in maintaining it as one of their products (documentation, maintainers...)
- OSS - Stricture, a linter to prevent architecture drift https://github.com/stricture-dev/stricture
- OSS - Enforma, super-productive react forms https://github.com/jacarma/enforma
reply