Earlier quoted context omitted.
What I’ve found is that you can care about things like craftsmanship, problem solving, and quality while not being bothered by the day to day short term project level thinking.
The problem is that writing good code requires more time than writing shitty one.. and if there is a lot of external pressure to finish the project, it’s quite difficult for me to stay focused on quality
At the end of the day, YOU are the professional. If an amateur decides that you are going too slow, that doesn't mean anything--they can feel free to hire more engineers or whatever needs to be done, but the onus is on _them_ to ante up. No matter how much you love your job, you're probably going to have multiple throughout your career so you need to focus on yourself first and foremost.