You can comply with all the principles of clean architecture, but there will always be room for improvement in both performance and maintainability. The question you should ask yourself is when a software is ready to go into production

It's ready 4 weeks before you finish according to the PM

It is ready when it meets minimum functional requirements without blowing up the servers

Otherwise, it is never ready. We as customers get greedy asking for more and we as devs introduce bugs with more LoC and we as QEs fail to catch up with automation coverage ending up slipping bugs into Production

Did it compile successfully?

It did? It’s ready for production

I mean if it works and the tech debt/maintainability isn't too bad... That's probably already better than much of what is used currently

My goal is to use a clean architecture and clean code for most of the project and only sacrifice that where performance or some other requirement really is worth it.

And in those cases, isolate that code into a class or library to keep it contained.

There is never going to exist one best way, its alway depends on the overall goals.

@IdontHaveAName Rust like