Software engineering is generating a lot of attention at the moment, so much so that a lot of people are willing to put their hands to the test in order to find out if writing code is for them. Something a lot of interested people say that I find funny is "I'm just going to code for one hour... ".
Any software engineer who hears such a thing will laugh (and with good reason) because software engineering isn't a sprint, while coding for one hour isn't impossible, it's hard to grow sustainably that way, you either lose track of time (like most people who become passionate about coding) or you begin to watch the clock, praying for an hour to be up so you can escape the frustrations associated with writing code that isn't running.
There's so much to learn when you're starting out, at one hour your brain is just getting warmed up. If there's something that software engineering imbibes in people, it's perfectionism, and because of that there's an irresistible urge to push boundaries and improve.
For those who would like to save time, it's important to speak to an experienced software engineer who can help you figure out what stack and languages you're interested in. Once that is done you have to select very specific resources and follow through.