TedDallas

I had created my own chat tool that can render html responses directly in the chat interface, if needed. It is very handy for when I am needing rich(er) responses dealing for mathematical expressions. But it burns more tokens. It is useful, but I don’t need it for coding.

Ask yourself what monks did when scribes were replaced by the printing press.

If I was a scribe at the time I’d be thrilled because of all that extra time available to work on beer productivity metrics.

About 20 years ago I maintained a shop floor control client/server application. I asked my manager why we didn't have any independent Q/A. He said we didn't need any testers because we have 500 in the building.

Wild west days then.

Looks like we are back.

Microslop? Its more like they are taking a Macro-crap.

Ugh, memories. I'm so old my first web browser was Mosaic and I think I saw this. I used a provider called Texas MetroNet that served up dial-up PPP connections for $45 a month on a speedy 28.8K baud modem. Days of wonder, I tell ya.

New days of wonder seem to be ahead, though. That said, there's about 100X more angst involved these days.

On a related note, when the sales and popularity of the automobile really started to take off, some farmers and rural residents would deliberately block roads with wagons and refused to yield right-of-way.

Per Anthropic’s RCA linked in Ops post for September 2025 issues:

“… To state it plainly: We never reduce model quality due to demand, time of day, or server load. …”

So according to Anthropic they are not tweaking quality setting due to demand.

Ask this question in the 1940s and they would tell you it’s math. We are making machines that do math to kill Nazis. Now take this vacuum tube and plug it in over there and then go get me a cigarette.

Three words to solve this problem: direct mail marketing.

Just kidding, that just goes into my RL trash can.

It is like SQL injection. Probably worse. If you are using unsupervised data for context that ultimately generates executable code you will have this security problem. Duh.

HeidiSQL is written with Lazarus/FPC.

It was kind or that way in early days of high end personal computing. I remember seeing an ad in the early 90s for a 486 laptop that was $6,000. Historically prices have always gone down. You just have to wait. SoTA is always going to go for a premium.

Yeah, the problem is if you don't understand the problem space then you are going to lean heavy on the LLM. And that can lead you astray. Which is why you still need people who are experts to validate solutions and provide feedback like Op.

My most productive experiences with LLMs is to have my design well thought out first, ask it to help me implement, and then help me debug my shitty design. :-)

I’m seriously thinking about getting a custom made bumper sticker with the following text: ‘; select 1/0;

DRY is more about support and maintenance than anything else.

I see a lot of attacks on DRY these days, and it boggles my mind. Maybe it is being conflated with over-engineering/paramterization/architecting. I don't know.

But I do know that having to fix the same bug twice in the same code base is not a good look.

Note to self: invest in a used book store ASAP.

I experimented with cc65 and wrote a simple game that ran on my actual C64 hardware. It was a lot of direct memory access, unrolling loops, and avoiding stack usage. A fun time overall, and it ultimately ran smoothly, but I see do why people who attempt anything serious on a C64 tend to focus on using ASM.

OK MS. The first thing I'll do is rebind it to run llamafile.exe

That is correct. I have lived in Tornado Alley for a half century. Serious tornadoes have landed all over my local area over the years, but I have also never even seen so much as a funnel cloud. They can be devastating though, but are also very localized and do not last long. That said, I do take tornado alerts seriously.

The thing about learning in general is that it inherently introduces biases. I imagine you could train up a genocidal maniac LLM with the right data sets.

Tic-80 is what you are looking for.

Low code has been a thing in ETL data integration space for a long time. Anecdotally the most consternation I have experienced lately has been supporting buggy low code implementations which seem to becoming worse and not better over the last 20 years or so.

Ernie stating Nixon as its favorite president is not really surprising. This is a common opinion among those in mainland PRC. Nixon and Kissinger are perceived as good guys that helped open up China to the West. When I have asked people in the PRC about Watergate, the common response is that the Watergate break-in was an internal issue for the US to deal with.

At a certain level of complexity it is easier to write the damn SQL than it is to explain your query to GPT.

Nice to see a cool looking cross platform editor written in Free Pascal with Lazarus. Pascal is a surprisingly expressive language.

Agile cargo cult software development there. Got to get that 4 byte change in this sprint in order to prove that the team's fantasy points are burning down.

Does it support a syntax for recursive queries? In T-SQL we use recursive CTEs which are ugly as hell.

This is very cool though. There are lot of features that would make my life easier. Group By All is noice.

If you liked Delphi then Lazarus is a great open source alternative for WYSIWYG Linux and Windows forms based application programming.

Recently I used it to create a little SQL editor with syntax highlighting for Maria DB. It only took a few hours which was mostly due to me trying to remember my Pascal syntax.

Lazarus also has a nice online package manager with a 1.5 zillion components available.

Object Pascal can feel antiquated. But Free Pascal remains fast, stable, and reasonably feature rich without much syntax bloat over the years.

Er ... SQL Server Management Studio is based on Visual Studio shell, and it does a fine job debugging stored procedures. I also code in C# and agree it also works well for that.

Recursion in SQL is one of the questions I always ask Data Engineers during interviews. The answer in MS T-SQL is to use a recursive CTE. It is not a common problem, but it comes up once in a while. Using a CTE is a better solution than calling an SP recursively because you can only nest 32 calls deep. In the MS Azure SQL Data Warehouse product you are simply fucked if you need to do recursion.