←back to thread

Be Aware of the Makefile Effect

(blog.yossarian.net)
431 points thunderbong | 2 comments | 11 Jan 25 04:13 UTC | HN request time: 0.416s | source
Show context
rednafi ◴[11 Jan 25 16:38 UTC] No.42666976[source]▶
This also happens with tools you have to use but don’t get much payoff from—like internal tooling. At work, we have a shitty in-house feature flag service. It breaks all the time and is super finicky. Learning it properly doesn’t really help me, so I mostly copy and paste my way through it.

Another example is jq. I use it occasionally, and ChatGPT handles the syntax pretty well. For me, learning it properly just isn’t worth the time or effort.

replies(3): >>42667099 #>>42672395 #>>42674553 #
1. stefr- ◴[12 Jan 25 09:47 UTC] No.42672395[source]▶
> Another example is jq. I use it occasionally, and ChatGPT handles the syntax pretty well. For me, learning it properly just isn’t worth the time or effort.

This resonates with me, I was in exactly the same position when I needed to do something with `kubectl` JSON output - just ask ChatGPT because I couldn't be bothered to learn the unintuitive syntax.

Interestingly I _can_ blame the tool, because I started using Nushell[1] which has built-in JSON manipulation that provides a MUCH simpler syntax, and I have learnt this properly because it was that easy.

1: https://www.nushell.sh/

replies(1): >>42681989 #
2. rednafi ◴[13 Jan 25 10:26 UTC] No.42681989[source]▶
Nushell is awesome. Too bad the incompatibilities are still a bit too much for me to use it as a daily driver.

It’s easy to blame the tool, but sometimes the problem space is inherently complex. With limited time, building the right abstraction is an immensely difficult job. LLMs fixed this issue for me, and I’ve stopped complaining about unintuitive but ubiquitous tools.