Haha, excellent question, one I'd answer differently after ~25 years writing lines of code (than I would have had 10 or 20 years ago).
I came to programming in part owing to a very inductive / self driven approach to doing things. Where programming lets you engage concretely, as opposed to say, putting people in motion towards a goal (aka management). Yea sure that is not the whole story (or I might be a potter, or a cook, also very direct).
Guess what? Managing and connecting is often the faster, better way to get things done; Henry IV will agree. Another thing: the myth of reuse. The whole computing thing changes fast enough that, reuse often is not in the code - even languages do have a shelf life.
Took me perhaps a couple of decades to get out of the life optimizing mood. Enhancing life through programming... well it's not for me now. I find more enlightenment in mind practices vs mechanizing our relationship with the world.
Overall a day without coding is not a good day for me. But I also think more about, okay. What is this piece of code doing? Good code is about removing. Removing hassle. Removing unused APIs. Removing worries. The best is stable code that liberates us from... machines and a taylorized life style. Closing, let's pick a counter-example: automated recommendations. That is terrible code. It is removing choice, narrowing perspective, mechanizing preference. Not the programmer's fault, mind.
Loved your take, Tea. I relate to a lot of what you said, this one is my favorite bit:
Good code is about removing. Removing hassle. Removing unused APIs. Removing worries. The best is stable code that liberates us from... machines and a taylorized life style.
Having had some experience with management, I agree that nothing in tech is faster than a capable and motivated group of people.
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.
Haha, excellent question, one I'd answer differently after ~25 years writing lines of code (than I would have had 10 or 20 years ago).
I came to programming in part owing to a very inductive / self driven approach to doing things. Where programming lets you engage concretely, as opposed to say, putting people in motion towards a goal (aka management). Yea sure that is not the whole story (or I might be a potter, or a cook, also very direct).
Guess what? Managing and connecting is often the faster, better way to get things done; Henry IV will agree. Another thing: the myth of reuse. The whole computing thing changes fast enough that, reuse often is not in the code - even languages do have a shelf life.
Took me perhaps a couple of decades to get out of the life optimizing mood. Enhancing life through programming... well it's not for me now. I find more enlightenment in mind practices vs mechanizing our relationship with the world.
Overall a day without coding is not a good day for me. But I also think more about, okay. What is this piece of code doing? Good code is about removing. Removing hassle. Removing unused APIs. Removing worries. The best is stable code that liberates us from... machines and a taylorized life style. Closing, let's pick a counter-example: automated recommendations. That is terrible code. It is removing choice, narrowing perspective, mechanizing preference. Not the programmer's fault, mind.
Loved your take, Tea. I relate to a lot of what you said, this one is my favorite bit:
Having had some experience with management, I agree that nothing in tech is faster than a capable and motivated group of people.