120 karma · joined January 4, 2019
Furthermore, I compose both types of text in an iterative process where I got the general ideas down first and then improve the precision and completeness of the piece.
Lastly, I think deeply about the human meaning of the text before I consider it complete, at least for my side projects. I refactor the code so that it matches my human model of the problem as well as I can.
Your mileage my vary, but coding and prose feel similar in my experience.
I don’t think humans usually choose the “best” solution. They use solution that are a combination of readily available, easiest to get started with, and popular.
For my work patterns it’s too feature rich. I only use it for browsing directory structures. Everything else just gets in the way because I haven’t taken the time to learn the other features.
I’ve written build scripts in BASH, Python, and JavaScript and can definitely say BASH scripts produced the most difficult bugs.
I welcome another option for my glue code.
Lots of old gems being posted after years.
I think they specifically said, when piping, don’t force functions to handle the error of the upstream function.
Because each error needs to be handled differently, the downstream function’s implementation becomes tied to the upstream function. Then the downstream function is only usable with said upstream function.
I realize that people need to make decisions based on their personal experience, and I don’t have a good rule-of-thumb for when to try a variation of a “bad” idea.