What seems to serve me best is keep things as simple as possible. If you add abstractions, do so to make the rest of the code easier and less complex. If you

What seems to serve me best is keep things as simple as possible. If you add abstractions, do so to make the rest of the code easier and less complex. If you must do something complicated, break it apart as pragmatically as possible and do it in the simplest way possible. Favor YAGNI (you aren't going to need it) over corporate-wide libraries that lock you in. Keep your codebase discoverable first. Structure by feature/function not type. Favor the local developer experience first. If you cannot open, follow and run the code easily, your developers won't be able to onboard quickly. Someone else will have to continue with your mess, make it as orderly as possible. I find that docker-compose can help a lot on this front, as can developer containers.