@technocounselor Well… Let me be honest with you. There are lots of people who use Claude Code to well, code their apps. That's called vibe coding. That means that they don't interact with a single line of program code, they don't even know anything about languages, compilers, building, tests and stuff. But I personally prefer double-check what I'm doing, so I don't vibe-code properly speaking, I rather use Claude as an assistant and productivity boost. So yeah, I use Claude extensively, it codes for me, writes documentation and tests, pinpoints errors, we discuss ideas and do brainstorms. But every line of code (except for automated tests) gets rechecked by me manually at the very time of coding or afterwards. #ClaudeCode #AI

I've been using #ClaudeCode for several months now, and like for two or three months with the Max plan. And only now did I find time to read some good documentation. Hopefully I'll use it even more efficiently. #AI

Quoting Gabriella Gonzalez @GabriellaG439 on #vibecoding:

[…] This example is pretty representative of my experiences using vibe coding. Every time I try out vibe coding for real (and not for demos) I start out feeling hopeful and excited and leave feeling let down and disappointed. I don't want to produce throwaway code: I want to build things that will last and won't blow up in my face later and I don't want to handhold/babysit/cajole the tool to get the results I want. I want vibe coding to improve the quality of my work, not deteriorate it.

https://haskellforall.com/2026/02/my-experience-with-vibe-coding

#theaicon #aihype #claudecode #nix