I could either take several tedious hours to write out several thousand regex patterns by hand to automatically recognize differing formats of notation for this thing I’m doing IRL…
or I could have an LLM do it in a few seconds, and it’ll get 99.99% of the cases, missing maybe one case every hundred thousand…
or I could have an LLM do it in a few seconds, and it’ll get 99.99% of the cases, missing maybe one case every hundred thousand…
Even if the LLM does things perfectly 100% of the time, how do you expect to maintain your skills if you offload all of your work onto a chatbot? What happens when you start offloading more and more until you’re not actually doing anything except typing in prompts?
My skillset is geared towards meatsacks and things that go boom. LLMs have been a massive boon to the 1% of my job that needs a code monkey.
As long as people still talk to each other, and things need exploding, I’ll have a job. Heck, if we somehow get to a point where money isnt needed, I’d still do what I do simply 'cuz I like it.
Frankly, your use case sounds like something has gone horribly wrong from the outset. If something needs several thousand regex patterns, then something is very very wrong, and there’s zero chance you have a comprehensive solution as it stands. Either trying to use regex for a use case that some natively AI approach might actually be warranted for, or regex is being used poorly and each one is too limited, or some other approach entirely is warranted.
Yeah I’m not a fan of slop merchants and PRs the size of battleships but anyone solving merge conflicts by hand because they hate LLMs is being a tad masochistic in my opinion. I’m in two minds about how much coding itself ought to be automated, but I’m a strong advocate of automating the tedious donkey work we’d absolutely have got rid of years ago some other way if possible.
It’s also good for avoiding tarpits, sometimes I literally don’t want to learn something because it’s too expensive relative to the value of retaining it. I would rather crawl over a mile of broken glass and hot coals than learn the detailed ins and outs of WSDL just to support a legacy feature which is firmly in the crosshairs of my deprecation gun, to use a totally neutral and not driven by personal bitterness example.
I could either take several tedious hours to write out several thousand regex patterns by hand to automatically recognize differing formats of notation for this thing I’m doing IRL…
or I could have an LLM do it in a few seconds, and it’ll get 99.99% of the cases, missing maybe one case every hundred thousand…
take your guess as to which option I chose.
LLMs are a tool. I use it as such.
Even if the LLM does things perfectly 100% of the time, how do you expect to maintain your skills if you offload all of your work onto a chatbot? What happens when you start offloading more and more until you’re not actually doing anything except typing in prompts?
My skillset is geared towards meatsacks and things that go boom. LLMs have been a massive boon to the 1% of my job that needs a code monkey.
As long as people still talk to each other, and things need exploding, I’ll have a job. Heck, if we somehow get to a point where money isnt needed, I’d still do what I do simply 'cuz I like it.
Frankly, your use case sounds like something has gone horribly wrong from the outset. If something needs several thousand regex patterns, then something is very very wrong, and there’s zero chance you have a comprehensive solution as it stands. Either trying to use regex for a use case that some natively AI approach might actually be warranted for, or regex is being used poorly and each one is too limited, or some other approach entirely is warranted.
well, it works, and i don’t need to touch it.
remaking what is already working would cost more time.
Yeah I’m not a fan of slop merchants and PRs the size of battleships but anyone solving merge conflicts by hand because they hate LLMs is being a tad masochistic in my opinion. I’m in two minds about how much coding itself ought to be automated, but I’m a strong advocate of automating the tedious donkey work we’d absolutely have got rid of years ago some other way if possible.
It’s also good for avoiding tarpits, sometimes I literally don’t want to learn something because it’s too expensive relative to the value of retaining it. I would rather crawl over a mile of broken glass and hot coals than learn the detailed ins and outs of WSDL just to support a legacy feature which is firmly in the crosshairs of my deprecation gun, to use a totally neutral and not driven by personal bitterness example.