|
|
|
|
|
|
by hiram112
1518 days ago
|
|
|
Bingo. There are at least a dozen tools and languages and syntaxes that I've used sporadically over the years - awk, sed, bash, Mongo, perl, etc. I don't use them often enough to remember exactly how they work, and so I always have to spend a few hours reviewing manuals or old code repos or an O'Reilly book. But if I do end up using it for a few days in a row, it starts to make sense, and I improve each time I use it. But not with jq. It just does not make sense to my brain, no matter how many times I've had to use it. Every single time I need to use it, it requires finding some Stack Exchange or blog and just copying and pasting. Even after seeing the solution, rarely do I then really understand why or how it works. Nor can I often take that knowledge and apply it to similar problems. About the only other syntax or language that gives me such problems is Elastic Search DSL. |
|
|