Category: MyXPostsArchive

AI pair programming is super fast now. It’s all about problem-solving. It generates code on the fly, then walks you through it, breaking it down into module-like pseudocode to clarify the logic. If there’s a module it doesn’t understand, it’ll whip up a minimized project to explain. That’s how I learn—hope it helps you too. But 🤡 don’t get a sudden urge to quit your job and go indie like I did 😭 It’s a classic fail… Big risks involved. I’m currently teetering between making ends meet and not 🤣

Under a bunch of fancy terms, your brain feels mystically profound. After several subconscious judgments of uncertainty, you end up choosing to believe. Remember, if it’s too complex and you don’t understand it, just reject it or don’t waste your time playing word games. Our purpose of communication is to exchange ideas, theirs is to deceive.

I intentionally talk to these people, even play dumb at dinner parties, constantly asking, "What's this? Oh, is it supposed to mean this? What do you mean by that? What's…

Just sharing my thoughts here because I’ve used comfyui and other workflow building tools—prompts are actually just a small (but important) part of the whole process. Personally, I don’t think there’s a need to systematically study prompts, and it’s definitely not about writing essays. It’s more about guiding AI, and there are various ways to do this, like using controlnet lora, depth maps, normal maps, Cenny edge detection, and open pose. When these models first came out, there was even a job called a Prompt Engineer, but that role has faded over time. Mastering a model’s prompts doesn’t guarantee that the same prompts will work effectively after the model upgrades or integrates other guiding models.