determination is a tricky thing. but i think there's also the ability to 'program yourself' to be determined. this usually means figuring out how to make whatever project you're working on fun -- and figuring out how to make sure the projects you're working on now and in the future are at least related to some long-term interest.
great discussion though. there is probably a 'language' of determination. and more efficient ways of being determined than others. i mean determination etymologically is related to a terminus or boundary. it is literally the ability or quality of getting to a boundary.
so if we infuse the meaning of determination with the idea of getting to a successful terminus -- we're referring to the ability to get the transaction done. in the case of startup space, one has to analyze what are the common set of obstacles that prevent getting the transaction done.
well (1) the manner in which the final terminus needs to be renegotiated as the project changes and competing views about the desired end result are brought into view -- so negotiation of the final result is key. (2) taking advantage of previous solutions, not reinventing the wheel but (3) not using any wheels which are limited or limiting and (4) spending maximum time and energy on the specific product.
but i think the most important thing is to regularly analyze whether or not one is on the optimal path to one's goal (first-round funding, e.g.) and also whether one can make the process of the development so bloody fun that one wants to spend as much time on the project as literally possible.
the most undervalued link in the whole network of the problem space is between the founders and their problem space. i.e., figuring out how to spend as much time as possible in your REPL, with your design diagrams, or otherwise amongst your code.
and now, i am just going to press 'add comment'. but yeah, nice article.
great discussion though. there is probably a 'language' of determination. and more efficient ways of being determined than others. i mean determination etymologically is related to a terminus or boundary. it is literally the ability or quality of getting to a boundary.
so if we infuse the meaning of determination with the idea of getting to a successful terminus -- we're referring to the ability to get the transaction done. in the case of startup space, one has to analyze what are the common set of obstacles that prevent getting the transaction done.
well (1) the manner in which the final terminus needs to be renegotiated as the project changes and competing views about the desired end result are brought into view -- so negotiation of the final result is key. (2) taking advantage of previous solutions, not reinventing the wheel but (3) not using any wheels which are limited or limiting and (4) spending maximum time and energy on the specific product.
but i think the most important thing is to regularly analyze whether or not one is on the optimal path to one's goal (first-round funding, e.g.) and also whether one can make the process of the development so bloody fun that one wants to spend as much time on the project as literally possible.
the most undervalued link in the whole network of the problem space is between the founders and their problem space. i.e., figuring out how to spend as much time as possible in your REPL, with your design diagrams, or otherwise amongst your code.
and now, i am just going to press 'add comment'. but yeah, nice article.