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.
that looks like a fork bomb
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.
Git revert --hard no need to copy anything
git push --force
I know I can do --force-with-lease. I meant what I typed.
Shove it in there lol
If violence isn’t working, you’re not using enough violence
I don't speak elisp, but I speak regexp. Looks like the LLM speaks neither.
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.
What do you mean it's impossible for it? I know how LLMs work but I don't know if any such limitations
Write me a regex that matches a letter repeated four times, followed by a 3 or 4 digit number
Here’s your regex:
([a-zA-Z])\1{3}\d{3,4}
They aren't context aware, it's using statistical probability. It can replicate things it's seen a lot of like a tutorial regex. It can't apply that to make a more complicated one. Regex in the wild isn't really standard at all, because it's rarely used to solve common problems. It has a bunch of random regexs from code it analyzed and will spit something out that looks similar.
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:
\\id:\\[^]]+\\\\\[^]]+\\\
No idea what the rectangles are supposed to be, I just copy-pasted it
They are valid unicode points that your font doesn't know about.
... or at least they represent that, but I think there's a character that looks like one too.
It's U+E001 from a Private Use Area. The UnicodePad app renders it as something between 鉮 and 鋁 (separate boxes stricken through; I wasn't able to find it even with Google Lens)
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?
People have unironically done that. No, it isn't better. The fundamental mental model is the same.
I want to see their unironic attempts, maybe they're useful to me at least if they're not better.
The fundamental mental model is the same.
It's not the fundemental model that I have a problem with for Regex, it's the fucking brainfuck tier syntax
I honestly think it can be a lot more readable, especially when the regex would have been in the thousands of characters.
There's a built-in feature that Perl has that only a few of the languages claiming PCRE have actually done, and it makes things a lot more readable. The /x modifier lets you put in whitespace and comments. That alone helps a lot if you stick to good indentation practices.
If all other code was written like an obfuscated C contest, it would be horrible. For some reason, we put up with this on regex, and we don't have to.
I agree, but then there's also some other niceties that come from expression parsers in the language itself (as noted in the article): syntax highlighting, LSP, a more complete AST for editors like helix.
Syntax highlighting works fine as long as your language has a way to distinguish regexes from common strings. Another place where Perl did it right decades ago and the industry ignored it.
Nah, the language itself should be as simple as possible. Bloating it with endless extensibility and features is exactly what makes Perl a write-only language in many cases and why it is becoming less and less relevant with time.
Except it has some really good ideas that should be copied. There are other languages that have a syntax for denoting regex, such as ~r'foo' in Elixir. This gets the syntax highlighting you need without a big addition to the language.
I suppose you could write functions like, startswith, endswith, alpha(4), or something like that,
yes.
but in the end, is that better?
YES.
startswith('text');
lengthMustBe(5);
onlyContain(CHARSETS.ALPHANUMERICS);
endswith('text');
is much more legible than []],[.<{}>,]'text'[[]]][][)()(a-z,0-9){}{><}<>{}'text'{}][][
Assuming "text" in your example is a placeholder for a 5 digit alpha string, it can be written like this in regex: /[a-zA-Z0-9]{5}/
If ”text" is literal, then your statement is impossible.
I think that when it gets to more complex expressions like a phone number with country code that accepts different formats, the verbosity of a higher level language will be more confusing, or at least more difficult to take in quickly.
Exactly. It's a lot like Java to me. Looks readable on the surface, but it's actually adding a bunch of crap you don't need and does not help anything.
They also have to implement a long list of features. These projects tend to focus on the handful of features the authors specifically use, and the rest get sent by the wayside. Taking the Melody language that was mentioned in another message, it hasn't even fully implemented [^A] or [abc]. We're not even talking about somewhat obscure stuff like zero width assertions or lookaheads. These are very basic.
string.contains("something")
Just do that repeatedly
The "something" is where the regex goes. For simple cases contains by itself does just fine, but for almost anything kind of dynamic input, it's going to not be capable of what regex does.
You're right, but it was a joke.
intermediary language between regex and actual programming
It's called Haskell.
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.
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
That's a lot of dollars, ching ching ching
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.