e0qdk

Presumably Moo Deng would be the water type... would Punch be the fire type and Jimothy the grass type? Or, is it the other way around?

e. Two, but the real trick is getting them in there...

They had me at 40 for a while as it built up; 20 seems to be about right for me as a maintenance dose. I felt like I slept for a week when we cut the dose! :p

My docs put me on prozac (well, the generic version of it anyway; it's cheaper). ~20mg/day seems to be about what I needed. Hope your meds are working out well and you're less anxious now; get your docs to adjust them if not!

For me, I felt tense/"on edge" basically all the time. At some point I realized I couldn't really ever "relax" properly -- just distract myself for a while. I'd overthink trivial things and worry about stuff that didn't really matter... so much so that it was getting hard to just do normal interactions in my life (like take out the trash or check the mail or buy groceries). My heart was pounding all the time to the point that chest pain was fairly common for me but I'd already had heart issues ruled out (even going so far as to wear a monitor for a month) before they pinned it down as general anxiety. You can get a lot of weird transient/phantom issues as a result of anxiety as well.

If you think you've got it, go talk to your doctor.

Here you go. XKCD 1319

I've got boxes of spaghetti that are at least six years old (I know I had them on hand during COVID...) which I've cooked up successfully as recently as last week.

YMMV with other types (particularly if it's got any meaningful amount of oil/fat in it) but for spaghetti at least, I haven't yet found an upper bound on usability.

They sell farmed, ground venison in one of the grocery stores I go to. It's imported from New Zealand, IIRC. I got a couple packs of it once. The stuff I got, at least, had a more iron-forward flavor than what I'm used to from beef and was very lean -- which made it less satisfying than ground beef or lamb for most of the dishes I use ground meat for. It tasted like beef that, if I paid attention, was kind of off, but otherwise wasn't very notable. Edible, but not something I've felt much inclination to seek out again. I'd be willing to get it again if it was cheaper or if I need to change my diet to be lower in fat, but otherwise I'd rather just have beef or lamb. I have not tried it as a steak though, and I haven't had wild caught as far as I can recall.

If you just pulled the default version of qwen3.5 from ollama's repo you downloaded a mediocre one that only uses ~6GB.

Check ollama show qwen3.5 and see if you get something like this in the result:

  Model
    architecture        qwen35    
    parameters          9.7B      
    context length      262144    
    embedding length    4096      
    quantization        Q4_K_M 

This is the default version I got when I first tried using ollama without any experience. It worked, but it's a heavily quantized, lower parameter version of the model -- i.e. it's pretty dumb -- compared to what you can actually run on your hardware.

I started running LLMs a couple months ago on my own hardware. I have a Framework Desktop that I ordered last year and also recently picked up a refurbished 24GB AMD RX 7900 XTX which I'm doing some performance testing against. The dGPU is much better for dense models, and slightly faster for MoE if I'm willing to run them at a lower quant -- but uses more power and has annoying coil whine. The Framework Desktop uses ~100W under load, is quieter, and for the MoE models already runs them fast enough for most of my needs -- so most of my LLM use happens on that system still.

For software: I'm using ollama on the Framework currently, but I want to replace it with just using llama.cpp directly eventually. I've been using llama-cli for testing the dGPU. I wrote my own chat client to interact with ollama as well as a few other programs for specific tasks.

I've been using the LLMs for a mix of research (both personal and professional), entertainment, practical coding tasks (mostly debugging and brainstorming, plus a bit of UI prototyping, automatic generation of sequence diagrams for documentation, and light scripting), as well as automation of tedious tasks.

As an example of the latter, people often send me requests to prepare data sets by email but don't specify the sources they want precisely so I have to go match the name against the real name in our archives; LLMs are great for mapping the imperfect name -- with typos, missing prefixes, incorrect addition of spaces, addition/removal of hyphens, etc. -- to the exact name I actually need to pull the data off disk when given a lookup table to compare against.

As far as models go, I'm mostly using various Qwen 3.6 and Gemma4 variants. I have multiple versions of each for different purposes. llmfan46's uncensored Qwen 3.6 35B-A3B @ Q6_K (from Hugging Face) is my default model currently.

"Dry humor" maybe, for the style?

Did some searching and one term that came up was the German word "Schmunzeln" which I hadn't heard of before.

wiktionary describes it as:

to smile slightly, smirk (not smugly, but in an amused or contented way; e.g. when witnessing an amusing scene or conversation)

Not sure if that's quite right or not, but might be what you're looking for if you want a word to describe the reaction? (Maybe someone who actually speaks German can confirm...)

I'd suggest replacing the shell script with a Python script as a first step. If nothing else, it will probably be a hell of a lot easier to read... Your bots ought to be able to do a first pass at that. If it's actually tripping up on some particular bash/dash-ism like you think, that might even just bypass the issue entirely; if not it should be easier to debug with better readability.