@halcwb.bsky.social

Ok, I am now definitely have learned my lesson now, having a LLM write code is a really, really bad idee. Explaining code, explore, etc.. fine. But actually writing, bad idee. In the end I am losing more time trying the LLM what I want then just write the code myself.

And Opus 4.7 is making it up as it goes: Honest answer: I shouldn't have gone along with the "namespaced under the integration branch" framing earlier. Pfff

Imagine running multiple AI agents working on your projects, from your phone. And these kinds of errors can be made by the AI? Luckily, I don't do that!

Bild

AI is great, for knowledge, not understanding. I use it to: 1. Improve my understanding and skills 2. To test and challenge my coding 3. Write code (or have the AI do it) Using Claude the quantity doesn't go up, but the quality does. And, by the way, #fsharp and AI are a great match!

Everybody is talking about how AI is going to take over programmer jobs. I just asked Claude Opus 4.6 to align markdown tables in a document. A very simple and humble question. It proceeded with some python script that really messed up things. I think I will continue writing my own code.😅

I told claude code to NEVER EVER touch my #fsharp code base files, i.e. anything *.fs, but instead do all implementations in script files, so I can first check what is going on. And I am so glad I did this.

And again when using Rider with #fsharp, I run into serious usability problems. Right now the only reliable alternative (on non Windows systems) is VSCode. I really hope VSCode, i.e. the Ionide extension keeps working, otherwise I am in trouble.

One thing is sure, when coding #fsharp, Copilot can destroy more code than I care for. So, no more Copilot writing code for me, it's easy enough to write my own #fsharp code. Just using Copilot to write comments, tests or checking coding logic.

I am going to experiment with #AdventOfCode. I will be using #AI, but with one command: "implement". The only context I can provide is an #fsharp type domain model. Comments that describe what to do are not allowed. Just types! The only implementation provided are let bindings. Day1:

Bild

With #fsharp, the hard part is not writing the code, the hard part (as always is) is; the domain modelling and coming up with the right algorithms. But the #fun fact is, the #fsharp code I wrote, helps reverse engineering the conceptual modelling.

Although I love #paket with my #fsharp projects. With the evolution of nuget, and the current dotnet 10 version, is there still an advantage of using #paket over nuget? Specifically as nuget solved transient package resolution, has its own lock file and introduced package pruning?

Compositional IT used to have some very interesting #fsharp blogs. Unfortunately, the site is down and so are those blogs. Any means to get them back or host them somewhere else?