Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
I think it really depends on what your goal is. If you just want to finish an application of a certain size or requirement, these tips apply. But most of my projects are about picking up new technologies, trying new coding styles, and other experiments. I don't care if I finish or not, once I learn or make an informed decision I'm golden.
Although in some cases learning is also becomes more efficient if you finish the Thing. For example, you can realize that the database does not work in real world that well, or the stack is not that scalable, or it was a too complicated stack.
Learning within small (complete) iterations has its upsides!
BUT! Learning is good anyways. :)
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 it really depends on what your goal is. If you just want to finish an application of a certain size or requirement, these tips apply. But most of my projects are about picking up new technologies, trying new coding styles, and other experiments. I don't care if I finish or not, once I learn or make an informed decision I'm golden.
Yeap, totally valid.
Although in some cases learning is also becomes more efficient if you finish the Thing. For example, you can realize that the database does not work in real world that well, or the stack is not that scalable, or it was a too complicated stack.
Learning within small (complete) iterations has its upsides!
BUT! Learning is good anyways. :)