4 ms·

Does someone have a problem? Can you build a solution to that problem? If not can you learn to build a solution to that problem? Once built, can you learn to im

Does someone have a problem? Can you build a solution to that problem? If not can you learn to build a solution to that problem? Once built, can you learn to improve that solution? The best advice on the profession that I was ever given was simply, "Learn to learn." The vast majority of this profession is just being interested in figuring out how to solve different problems. Sometimes that means it's all you and sometimes it means learning new things or doing research. You know that you are not a good programmer when you don't see any problems that need to be solved.

johnfn 9y ago
In that case, what do you do?
- mercer 9y ago
  I'd say: go look for those problems! I'm sure others can do a better job elaborating on this process. I only recently made a mental switch to treat programming as a thing in itself that I enjoy, and it really has made me a happier person. I'm learning faster and more than ever before (even with coding as my only source of income, which should have provided incentive), I'm having an amazing time exploring things for the sake of just exploring and learning. And as a bonus, it has made me both enjoy and do better at my job as well! I feel like my toolset has rapidly expanded, and as a result I can (justifiably) use those tools to help clients (and get paid), scratch actual code-solvable itches I've had for years, and see potential ways to generate recurring income. And, with some trepidation, I even think I've learned at least some things that I can use to 'make the world a better' place! EDIT: more specifically, aside from looking for problems to solve, I decided to create my own problems, or consider them worth solving, and then went and solved them.
- mrisoli 9y ago
  If your code is bulletproof and you don't have any problem to solve then you move onto the next piece of software, I've never heard a programmer saying he has too much free time and not enough projects to work on.
spo81rty 9y ago
I couldn't agree more. It's all about problem solving. The coding part is just how you do it. If you have to be told how to write code or architect a solution, you are not a good programmer... yet!

johnfn 9y ago

In that case, what do you do?

mercer 9y ago
I'd say: go look for those problems! I'm sure others can do a better job elaborating on this process. I only recently made a mental switch to treat programming as a thing in itself that I enjoy, and it really has made me a happier person. I'm learning faster and more than ever before (even with coding as my only source of income, which should have provided incentive), I'm having an amazing time exploring things for the sake of just exploring and learning. And as a bonus, it has made me both enjoy and do better at my job as well! I feel like my toolset has rapidly expanded, and as a result I can (justifiably) use those tools to help clients (and get paid), scratch actual code-solvable itches I've had for years, and see potential ways to generate recurring income. And, with some trepidation, I even think I've learned at least some things that I can use to 'make the world a better' place! EDIT: more specifically, aside from looking for problems to solve, I decided to create my own problems, or consider them worth solving, and then went and solved them.
mrisoli 9y ago
If your code is bulletproof and you don't have any problem to solve then you move onto the next piece of software, I've never heard a programmer saying he has too much free time and not enough projects to work on.

spo81rty 9y ago

I couldn't agree more. It's all about problem solving. The coding part is just how you do it. If you have to be told how to write code or architect a solution, you are not a good programmer... yet!