3 ms·
I am a software engineer. I recognize the need for good tools, as computers. In the end of the piece I imply that tool use in and of itself is not bad of course
by satvikpendem 7y ago
I am a software engineer. I recognize the need for good tools, as computers. In the end of the piece I imply that tool use in and of itself is not bad of course, nor that one shouldn't strive to use better tools. However, one should not strive to research tools as a end in and of itself rather than the means to do real work. Don't spend a literal week of time researching. This is the crux of what I aimed to say.
I spent so much time researching tools that I forgot what I really wanted to do, and in that same amount of time, had I spent it doing the work I wanted to do, I would have finished the project. I talk about true obsession over material things rather than mere research of them. The latter is fine, but the former can have severe psychological consequences.
- coldtea 7y ago>Don't spend a literal week of time researching. This is the crux of what I aimed to say. Why not? For one, how is "week of time" defined? Is it "over the course of a week", while also working, taking the kids to school and so on? E.g. a few hours each day perhaps? If so, why not? >I spent so much time researching tools that I forgot what I really wanted to do, and in that same amount of time, had I spent it doing the work I wanted to do, I would have finished the project. In the above case, that would make it a weekly project. If you do a week's research to buy a PC (or other tool) for a week-long project, then sure, you have a problem. If you do a week's research to buy a PC you'll use for 4-6 years, then by all means, do it. I agree with analysis paralysis, and pixel peeping, and too much obsessing over specs. Just not with the way its phrased, and the examples given, which all seem not very far from the right way to go about things.