Comment on Which guides to trust for novice / normie getting started?
Fedegenerate@lemmynsfw.com 4 days agoFor all its flaws. Low level tech support, rubber duck, command explainer is something LLMs do really well. Kept my early mistakes off the web and got me where I needed to be most times.
theotherbelow@lemmynsfw.com 4 days ago
I haven’t had that experience. More often than not I’ve found properly made software breaks in ways that tell you why. I seem to get stuck going in a circle of doom with llms.
Fedegenerate@lemmynsfw.com 4 days ago
I must have been having more basic problems than you. I found LLMs to present the most common solution, and generally the most common way of setting it up is the “right-way”, At least for a beginner. Then I’d quiz it on what docker compose environments do, what “ports: ####:####” meant, how I could route one container through another. All very basic stuff.
By the time I wanted to do non-standard stuff I was better equipped with the fundamentals of hobbiest deployment and how to coax an LLM into doing what I needed.
Goes without saying I’d take the output of the LLM to Google for verification, then back to the LLM for a hobbiest’s explaination, back to Google for verification…
Properly made software has great documentation and logs. If you know how to access those logs and read documentation (both skills in themselves)… Not to mention not all software is “properly made” some of it is bare bones and just works ™.
theotherbelow@lemmynsfw.com 4 days ago
Fair enough. LLMs and even Google have nuanced drawbacks, I personally try to give the creator of software some say into its usage simply because the intended usage is better tested than any changes I may need in the future.
At the and of the day learning is key.