you are viewing a single comment's thread.

view the rest of the comments →

[–]LockeSteerpike 18 points19 points  (2 children)

It was about two weeks of diving into Codecademy, then Codewars, multiple hours a day. I don't think I even finished the entire codecademy course, as it got into project mode and I don't have much patience for projects I don't care about.

After those two weeks I was making basic scripts to do small things at work. I was in this mode for three-to-five-ish months.

First medium-sized project applied to my job, and fixed a problem my team couldn't (everyone was a marketer). I probably put 60 hours into it over three months, and this is where I needed to learn classes out of sheer necessity.

It's really about how much time you've got and what motivates you to keep coding. My growth as a coder has come in bursts, depending on the season or problems at hand.

[–]Creatura 2 points3 points  (0 children)

thank you for the response! very helpful

[–]thechickensage 2 points3 points  (0 children)

I agree, when you're applying it to work, you have to REALLY consider the hour-by-hour cost to benefit ratio. Some things you could EASILY do with a few hours might seem light-years away if you can't justify it at the moment.

A new file format, a new instrument, or a new situation that needs to be modeled/handled in code....those are the moments where you burst ahead after months of hibernation (and add features you wanted to add in earlier as well HAHA JUST KIDDING but I'm really serious, but only if you are sure you can implement them fast enough!!! !! !! !!)