I think I started somewhere around 1990, at the age of 10ish. I have spend from a few hours a week to 100+ hours a week learning. I love to create software, and I have been doing it a lot. I have made it my work. If you want to compete with me with the amount of time I spend on learning to create software, you might as well give up right now! Because it is not a race.
In a previous comment I remarked that "My outside programming is done in dead tree format". Browsing dev.to (etc.) is also learning to create software. Reading an article, and then thinking about it is also learning to develop software. You are also learning to develop software while you are taking care of your daughter after you just read about something interesting. It is akin to to the "eureka effect". Read something, then do something else more tedious (as in, less mentally challenging) and you continue to learn because you are still thinking about the problem.
Note, I refuse to talk about "coding" because I object to the term. The craft is "software development", not codification of natural language to machine interpreterable code. We solve problems in the form of software. We do not codify. Solving software problems does not require physical access to computers. We can do this in our mind while we are on the toilet, under the shower, changing a diaper.
Thank you for the great advice. I read that I must become a problem solver, but never in that degree. I think adopting that mindset will make all the difference between a coder and a software engineer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think I started somewhere around 1990, at the age of 10ish. I have spend from a few hours a week to 100+ hours a week learning. I love to create software, and I have been doing it a lot. I have made it my work. If you want to compete with me with the amount of time I spend on learning to create software, you might as well give up right now! Because it is not a race.
In a previous comment I remarked that "My outside programming is done in dead tree format". Browsing dev.to (etc.) is also learning to create software. Reading an article, and then thinking about it is also learning to develop software. You are also learning to develop software while you are taking care of your daughter after you just read about something interesting. It is akin to to the "eureka effect". Read something, then do something else more tedious (as in, less mentally challenging) and you continue to learn because you are still thinking about the problem.
Note, I refuse to talk about "coding" because I object to the term. The craft is "software development", not codification of natural language to machine interpreterable code. We solve problems in the form of software. We do not codify. Solving software problems does not require physical access to computers. We can do this in our mind while we are on the toilet, under the shower, changing a diaper.
Thank you for the great advice. I read that I must become a problem solver, but never in that degree. I think adopting that mindset will make all the difference between a coder and a software engineer.