"AI is gonne take our jobs." The AI:
"AI is gonne take our jobs." The AI:
45 comments
-
Management: Fuck it, ship it.
The people at the top honestly don't give a fuck if it barely works as long as it's an excuse to cut costs. In things like Customer Service, barely working is a bonus, because it makes customers give up before they try to get their issue solved.
-
I mean, I bet it failed at making a regex that worked much faster than you could fail at writing a regex that worked. Sounds like progress! :D
-
I am always suspicious if a regex I write doesn't throw some form of pattern compilation error. It usually means I'm not even close to the correct solution.
-
-
You know what? If your management is telling you to use AI generated code to “go faster”, just go ahead and do it. But fork the repo first, in case you’re still around when they get fired and someone sensible says to put it back how it was before.
-
The problem is - you are far more likely to get fired when things go wrong :(
-
Well, if you just swap your CI to point af the fork, and then port over the non-ML delta of business logic, then you’re a fuckin hero and can write your own check, so long as you play it right. Depending on the company. And the leadership. And where you live. And how much of the kool-aid you drink. And-
But I digress. I do think it’d be quite possible to wrangle a promo out of a situation like that if you play it right.
-
-
Just outta curiosity:
Full o1 model
"\\id:\[]]+\\\\[]]+\\\"
Claude 3.5 Haiku:
Never used elisp, no idea of any of this is right lmao
-
Claude at least created an elisp function that looks ok
-
3.5 sonnet might do a lot better, idk I'm on the free plan with Claude lmao
-
-
o1 without Markdown misformatting:
regex
\\id:\\[^]]+\\\\\[^]]+\\\
No idea what the rectangles are supposed to be, I just copy-pasted it
-
I swear to god,someone must have written an intermediary language between regex and actual programming, or I'm going to eventaully do it before I blow my fucking brains out.
-
How do you think that would look? Regex isn't particularly complicated, just a bit to remember. I'm trying to picture how you would represent a regex expression in a higher level language. I think one of its biggest benefits is the ability to shove so much information into a random looking string. I suppose you could write functions like, startswith, endswith, alpha(4), or something like that, but in the end, is that better?
-
intermediary language between regex and actual programming
It's called Haskell.
-
-
-
As it learns from our data, no wonder it fucks up at regexps. They are the arcane knowledge not accessible to us mere mortals, nor to LLMs.
-
If you know even a little about how an LLM works it's obvious why regex is basically impossible for it. I suspect perl has similar problems, but no one is capable of actually validating that.
-
-
that looks like a fork bomb
-
I don't speak elisp, but I speak regexp. Looks like the LLM speaks neither.
-
I love regex. I know, most don't, but I do. GPT/Claude can write some convincing code, but their regexes can be spotted a mile away.
-
That's a lot of dollars, ching ching ching
-
Try breaking each character in the string into its own token, it’ll have an easier time because it’ll actually know what the string is
-
Gpt4-mini, the model that’s worse at everything but like 100 times smaller or whatever. Really cutting insight you have here.
This is like interviewing the child of a programmer and hiring based off of that.
Next you’ll be making hiring decisions based off of optical illusions and riddles.
-
This is like interviewing the child of a programmer and hiring based off of that.
I could land a job that way, but I'm just that fucking good. Lol.
-
45 comments