jamel

AI has allowed me to quickly create an MVP by automating the process of coding and adding features has been a breeze.

However, the trouble appeared only much later.

Each newly added feature would introduce a new dependency or edge case, or even a duplicate of the existing logic. The project looked slick but changing anything meant breaking something else.

This experience taught me that fast development is not only about the speed at which we can introduce features but also about the simplicity of further changes to the code base.

It's been about a month since I started posting as a founder in English. Blog posts go to Dev.to and Indie Hackers, and I post on X, Threads, Instagram and Facebook too. The one I'm stuck on is LinkedIn.

I've always posted there in Japanese, and I have around 5,000 followers, but almost no connections in the English-speaking world. LinkedIn isn't that big in Japan, and a lot of people here aren't comfortable with English. If I suddenly switched to English, I think a lot of my existing connections would just tune out.

I thought about a separate account just for English, but it looks like LinkedIn only allows one account per person. If they built in auto-translation the way X has, the language barrier would mostly go away.

Anyone else dealing with this? How did you handle it?

Apple's App Review Guidelines say you must disclose where personal data goes to third-party AI and get explicit permission first. A privacy policy paragraph doesn't do that.

Most of us read Apple's November 2025 guideline update, saw "AI" in it, and filed it under things for the big players. I did too, until I reread it as someone who sends people's journal entries to a language model.