I get your point but let me say this: you develop a framework for problem solving as you advance in your career, which can sometimes constrain you. But that's why you have to keep being open to experimentation. That's how you actually grow and improve. Otherwise you can easily fall into the "use the hammer for everything" problem…
Def. 💯 But that idea itself (let's get meta...) is part of a problem-solving framework itself 😜.
I agree that a very rigid way of solving problems everywhere is def. going to constrain you 100%.
But even in times of experimentation, your experience should guide you in knowing:
what to experiment with
how to do it
how long to take until giving up
how to detect potentially successful experiments
etc.
So even the process of experimentation itself has some over-arching framework that you implicitly and explicitly are aware of - which, in the end, should be informed and improved by your past experience.
That's a bit more philosophical than most would like 😂.
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 get your point but let me say this: you develop a framework for problem solving as you advance in your career, which can sometimes constrain you. But that's why you have to keep being open to experimentation. That's how you actually grow and improve. Otherwise you can easily fall into the "use the hammer for everything" problem…
Def. 💯 But that idea itself (let's get meta...) is part of a problem-solving framework itself 😜.
I agree that a very rigid way of solving problems everywhere is def. going to constrain you 100%.
But even in times of experimentation, your experience should guide you in knowing:
So even the process of experimentation itself has some over-arching framework that you implicitly and explicitly are aware of - which, in the end, should be informed and improved by your past experience.
That's a bit more philosophical than most would like 😂.