Ryan W. McClellan, MS

Yes. A while back, I tried the "move fast, iterate a lot, learn later" method with a video game (this was 2012 and even then it didn't work, either). We wanted to soft launch and the bugs were crazy. Characters loaded upside down; they fired on their teammates...the lesson was, we launched this crud to the public, hoping it would provide feedback when we forgot that we had our own feedback...

AI dependency syndrome. I'm glad you shared this, and that you learned from the causation. AI, believe it or not, is still in beta mode; we just do not realize it because we think it is smart enough. I've spent a lot of time with no-code editors that function on Claude's API and they do the same thing, and it seems almost like it's trying to find ways to gain tokens on things it already knows....

It's a bit frightening, to be honest. Personally, I'd rather a 50/50 exchange. With agents, as an example, I would never trust it 100%. We are in the beginning stages of a new era where data and privacy are of utmost concern, and it trumps the necessity. It's either a) move faster half-effectively, or b) move a bit slower but do so effectively.

I have a rule-of-thumb: offer your best for free, and the paid will follow. As a consultant, I often give my best advice away for free, and the person will remember I provided it to them. Half of the time, it comes back to: "Do this for me and I'll pay you to do it." This can be translated into a product mindset. Provide just enough value for free to showcase the benefits, and they'll...