I've recently gotten into training grip strength and since it s a new area of strength training for me, I ve been asking Claude a lot of weird questions about training and recovery techniques. So now, my chat history is a ton of stuff about work with the occasional odd question about how often I should be using extensor bands haha
What are some of the strangest things you've asked AI to help with? Did it actually help?
Coming from an engineering and agency background, our default mindset was always to write clean, fully modular, and perfectly scalable code before pushing anything to production.
However, building our own Micro-SaaS products quickly shattered that mindset.
We learned the hard way that spending weeks over-architecting a feature that users might not even want is the fastest way to waste momentum. Shifting to "shipping fast and listening to user feedback" forced us to make uncomfortable trade-offs between technical debt and speed.
Most complaints I get are not new. They are old, quiet, and only turn into a complaint once someone finally runs out of patience. By the time I hear it, the person has usually been annoyed for weeks and just never said anything, or said something small that I did not register as a warning. Curious whether that pattern is just me, or whether the actual complaint almost always arrives later than the moment the person first felt it.
When you re building your first product, it s easy to become too close to the problem. As the creator, you already understand how everything works, so it can be difficult to notice confusing parts of the experience.
That s why testing with other people is so important.
AI is becoming a bigger part of software development every day. It can generate code, write tests, review pull requests, and even help with debugging.
But I don't think every part of development should be automated.
Understanding user needs, making architectural decisions, solving complex business problems, and thinking creatively still seem to require human judgment.
