Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
- 117
- 1
Jump in the discussion.
No email address required.
Notes -
Well, it's happened. The pressures of our workload have driven a push to use AI to help with some of the bitchwork of coding. There is going to be a push to use AI to generate unit tests.
The toolchain involves OpenCode, so I figured I'd install it locally to get familiar with it before I start burning GPU time at work. Also, for reasons, we aren't allowed to use the GPUs. So last night I installed Ollama, OpenCode and the gemma4:e4b model on my humble RTX 4070 Super with 12 GB of VRAM. I tried to have it do the simplest of tasks. Create a Hello World project in dotnet10, and write a single unit test to verify it's output.
The first thing that happened was it created a new project. New projects actually begin with hello world output already. It then added a second hello world output. This poisoned the well, as now the AI was horribly confused about why there were two hello world lines. It never fully recovered. The project was generated without it's int main format which I prefer, so I tried to have it restructure the project to use that. After several missteps because it couldn't get over the fact that there were duplicate hello world statements, it finally figured it out.
Next came the unit tests. It created a unit test project, but then didn't actually populate the tests or link the projects. Then it wanted to refactor hello world, and pull in all sorts of abstraction frameworks, so it could test the output without redirecting stdout. I told it forget all that and redirect stdout. It had already done half the refactoring in a state that could not compile, and then never undid it, and then the whole project was totally broken and it couldn't figure out how to fix it.
I remind you, this was a "Hello world" and a single unit test. I told the AI it fucked everything up, it asked what it could do to fix it, and I told it that it could shutdown. It did. I think.
I know a lot of people reading this are AI evangelist. Where did I go wrong? What the fuck do people see in this shit?
Well, it's happened. The pressures of our household have driven a push to use a fire to help with some of the bitchwork of cooking. There is going to be a push to use fire to cook our meat.
The method involves using fire to heat up a vessel that will contain meat. So I figured I'd get this set up in the backyard so I could be familiar with it. Also, for reasons, we aren't going to be allowed to use metal. so last night I dug a pit, put wood in it and got my humble plastic bowl. I tried to cook the simplest meal, some steak and berries.
The first thing that happened as I put the steak in the plastic bowl and placed it directly in the burning fire is that the bowl started to melt almost immediately. This poisoned the meat. No matter how I moved the bowl within the fire the melting only got worse and I burned my hands painfully in the process. Next I tried to throw the berries into the blaze and was rewarded only with foul smelling smoke.
You used tools no one would ever have advised you to use, in a way no one would ever advise you to use them in. There isn't like one or two things that you could tweak to fix this performance. open up a free chat gpt chat and just ask it what you should do to to get started.
More options
Context Copy link
More options
Context Copy link