Any prompt jockey can make a faster ripgrep. The spec is "faster ripgrep".
What is the one thing that only you can specify, where your competitive advantage is maximized? Find that thing and pursue it with all your energy!
Any prompt jockey can make a faster ripgrep. The spec is "faster ripgrep".
What is the one thing that only you can specify, where your competitive advantage is maximized? Find that thing and pursue it with all your energy!
Typechecking with my own algorithm. Simple enough to specify in Python. Annoying with much boilerplate in CUDA. Similarly annoying to test.
the difficulty now is finishing.
However you can set up loops where the AI do improving by themselves and you just have to steer
Sigh. It was always like this.
I agree with the sibling comment: the difficulty [now, but also before] is finishing.
I'm currently experimenting with some custom hardware + software, composed in a way that seems novel, for a niche domain. This is with a new kid coming soon. There's just no way I would have crossed the activation threshold to do that without having LLMs provide assistance.
Can you give some examples where people have done that?
If somebody's passion is faster command line tools, let them make a faster ripgrep. First results may be disappointing, but those who don't give up will figure out how to do it right.
Or just look around for people who are doing this and then tell the LLM "faster <thing that the other guy did>"