There&#x27;s a couple modes of engineering mindsets I&#x27;m conscious of.<p>1) Being careful of every change and addition I make.  Trying to figure out and predict the effects, scalability, and maintainability of the code I produce.  I find that most engineering positions are looking for this, as most employers already have an existing production code base and would not like wild things like crashes and service disruptions to happen to their audience.<p>2) Occasionally, I get to start on something completely new. Not new as in just a blank page, but new as in blank project, or even blank idea.  As exciting as this sounds, over 90% of the time, the idea will die as there is some undiscovered flaw or expectation almost always external to an exceptionally well thought out implementation.  The only thing clear about this is the urgency of the deadline, and the failure associated with missing it (missed management expectations, no demo, no presentation... etc). Many know this as building a Minimum Viable Product.  In this case, all rules go out the window.  Choose expedient tools, create copious crap code and internal design, as long as it works OKish in the end. Having it violently done tomorrow as opposed to 3 days later, or a week later, or a month later, is key. If you&#x27;re lucky and it limps along (not canned as uninteresting), just change hats and become the step (1) engineer.<p>Sounds like you desire some more experience with (2), but both types of people are needed.  You, yourself, will become more valuable if you can put on both hats, but I wouldn&#x27;t say that one hat is absolutely better than the other.