I am especially interested to the manufacturing concept, finding a way to need it, part. How do you balance this component? Letting it to roll, "discipline", shaping priorities, ...?
I used to have a harder time with discipline and distractions before starting DEV. Now my time is pretty filled up and I like what I'm doing that I get tired pretty quickly with new things that aren't obviously helpful.
But sometimes I need to kick myself out of that and be more exploratory. Usually this is when we need to shift to a new approach as a company, but I need to learn more before I can have an opinion. In this case I don't know we need the new tech or concept, so I kind of pretend we do. That's the manufactured need I guess.
I think the big take away is knowing your own motivations and what trips you up and learning how to play the right games with yourself to get down to actual learning.
I am especially interested to the
manufacturingconcept, finding a way to need it, part. How do you balance this component? Letting it to roll, "discipline", shaping priorities, ...?I used to have a harder time with discipline and distractions before starting DEV. Now my time is pretty filled up and I like what I'm doing that I get tired pretty quickly with new things that aren't obviously helpful.
But sometimes I need to kick myself out of that and be more exploratory. Usually this is when we need to shift to a new approach as a company, but I need to learn more before I can have an opinion. In this case I don't know we need the new tech or concept, so I kind of pretend we do. That's the manufactured need I guess.
I think the big take away is knowing your own motivations and what trips you up and learning how to play the right games with yourself to get down to actual learning.
Thank you, your last sentence is extremely relevant. That's when things flow :)
EDIT:
As an aside, it already happened that the
manufactured needended up clashing withcompanyneeds?