What if you believe the project requires clean architecture, but the manager insists on delivering quickly with a dirty architecture?

In such a situation, it is important to find a balance between architecture quality and business requirements. The following steps can be suggested:

• Explain to the manager the benefits of clean architecture: maintainability, scalability, reduction of technical debt.
• Propose an iterative approach: start with a minimally viable version and then gradually improve the architecture.
• Highlight critical parts where clean architecture is most important, and focus on them.
• If the manager insists on speed, a compromise can be agreed upon, but it is essential to document technical debt and risks.

Ultimately, it is important to maintain an open dialogue and seek solutions that consider both business goals and code quality.