4 ms·
>"...advise to focus coding goals towards solving problems within his domain." Exactly. Every field is bound to have some common problem which is dying for an
by incision 13y ago
>"...advise to focus coding goals towards solving problems within his domain."
Exactly.
Every field is bound to have some common problem which is dying for an app to mobilize it, a site to collect and correlate it, some code to automate it or a framework to organize it.
Identify a problem in the native domain then figure out to leverage code to solve it.
This is exactly the sort of transition I'm eyeing, but I'm looking at it from the perspective of systems/operational tech rather than something entirely outside.
- tbassetto 13y ago> Every field is bound to have some common problem which is dying for an app to mobilize it, a site to collect and correlate it, some code to automate it or a framework to organize it. At first sight, we can not see one but he will keep trying to find one because it is definitely helping to work on a project that could help you in your current job. That said, I tend to agree with gofer's comment about how it could not evolve into a position of developer in his current field. There are definitely "IT people (developers included)" and "domain experts". Maybe mentalities could be changes…