Learning that AI models do a decent job of learning your coding style. Adding overrides to ANTLR output, as the parser progresses, has gone from, "What? That code is garbage! Stop!", to, "Okay, you have even managed to copy my naming conventions and method structure. Can't iterate the expression context like that as the grammar file doesn't define it that way but not bad"

Okay. Belay last post. I need to shape up what I have with exception handling before I go forward. Seat of the pants is fun and all but this IS work after all.

Language parser now handles compound assignments (+=, -=, *= /=, ^=), the full complement of comparison operators, increment and decrement operators, Round, LimitMin(floor), and LimitMax(ceil) functions….

I guess I need to bite the bullet and do the flow control bits. (while, do - while, repeat - until, for, switch - case, goto LABEL, etc)

Oh and add a ternary operator because I never got round to it in the original, C++/ANTLR2 version.

The porting of our tax formula language to ANTLR4, C# and Blazor is progressing nicely. Amazingly, no native code injection has been required in the grammar files apart from some header pragmas to stifle pedantic warnings.

And, on the AI coding front, I report that it has some, limited, merit in code completion. If you are boilerplating a simple class, it's nice that you can hit TAB and complete a skeletal outline. Good time saver. If you are doing something complicated, it's best to turn it off as the constant "Hey, try this!…Holy hell! No!" dance gets old fast.

It does a surprisingly good job with ANTLR grammar rules though its labeling conventions are a bit daft.

Eventually, I disable it altogether as it can become truly annoying. This effort is mostly so I can get a feel for what is going on currently. All in all, I do NOT like what I am seeing.

As it continues to scrape the Internet for content, it will increasingly feed upon the output of VIBE coders who don't actually create. Thus, the rot will progress like a degenerative disease would. Doesn't take a genius to see that.

The legal and ethical ramifications of what has been done pretty much guarantees it will remain a taboo topic.

//

matigo.ca.

Just got through telling someone that I fear for the future of software development in that respect. The western AAA gaming industry is already reeling and on the ropes due to that kind of short-sightedness.

matigo.ca.

I'm highly amused right now. I decided to not be a luddite and give AI code generation a shot.

It is going about as well as I figured it would. That is to say, it automates scraping sites like Stack Exchange and copy/pasting. Some of the non-free models make a passable attempt to refactor and integrate into a current project. The best you can hope for is, "It compiles".

Asking it to "Generate logic to parse an ANTLR grammar and send the compiled results to a MySQL database" produces truly comical results.

I fear for a lot of software projects in the future.

If you are good at what you do, AI poses absolutely no danger to you at present.

Teetering on the edge of 60, I was more than a little concerned that the days of voraciously absorbing new technologies and concepts were probably behind me. I'm pleased to report that this isn't the case.

The only marked change is that I can no longer hack for four days straight without sleep. I can live with that.

Me being me. I agreed to dive into a Blazor Hybrid Web Assembly project without knowing a whole hell of a lot about it. I'm just now getting acquainted with the stuff. Fortunately, I like what I am seeing so far. Especially from a performance standpoint.

Bonus points for it being so easy to deploy from Apache on Ubuntu. I was literally done in three minutes. My past experiences with wedging stuff into Apache were not pleasant so this is a surprise.