First, congrats on starting your new career! I’ve been a dev for over 20 years and trucking on still, so I can give you my 2 cents. If you’re just starting ou

First, congrats on starting your new career! I’ve been a dev for over 20 years and trucking on still, so I can give you my 2 cents. If you’re just starting out, your boss ought to be taking a more ‘mentoring’ style with you. Your reasoning is fair, and taking care to do things right is a good philosophy. However, there’s often a balance between time sensitive deadlines and doing things rigorously in development. Knowing what compromises you’re making as a developer and why you’re making them is something that comes with experience. Essentially, we’re making design decisions in the interest of time. As a manager, I’d be uncomfortable expecting a junior dev to get this right, but the fact you’re aware of the right way to do it, and what you’re being asked to do is a compromise, is a good signal that you’re a good developer . All my developers had their own ideas of how to do things and discussing whether a particular idea was worth the risks it brought to the deadline was all perfectly normal, reasonable and expected. Just normal project management mojo. So long as you and your boss can have productive conversations about your concerns, I wouldn’t be too hasty about leaving. I’d suggest you learn what you can where you are, realise what’s missing from your current role and keep an eye out for other job opportunities.