I don’t think there is any amount of explanation or detail that will satisfy everyone’s different views and ideologies around this topic. That is also not where I want to spend my limited time. I would rather focus that time on building and improving the product.
On the AI usage point, I understand why people on Reddit or Lemmy react strongly to it, but I also think the discussion often gets reduced to an extreme and inaccurate generalization. So calling anything which has AI usage "slop" or "vibe-coded" without actually doing any analysis is wrong.
Writing code has never been the hardest or most expensive part of building real software. The harder parts are product design, architecture, long-term maintenance, production readiness, scalability, support, debugging, and making responsible trade-offs over time. Anyone who has built and maintained software professionally knows this already.
AI is a tool that can speed up one part of the software development. That does not replace engineering judgment, experience, ownership, or accountability. A good analogy is a car: if you know how to drive, it helps you get to your destination faster. If you don’t know how to drive, you can hurt yourself and others along the way.
At this point, I don’t think continuing this discussion is useful for me or for the project, so I’ll leave the thread here from my side.
Thank you.
Thank you. It has been a lot of work to get the integration seamless. But finally it is getting there.
Shared journals has been heavily asked for feature but I have not been able to get it to due to lack of time from full time job and family and in whatever time I get from that I try to focus on building stuff which I need as first priority. In my use, I don't have a need for a shared journal. But I will try to see if I can get to it. Probably in summers during some time off.