I m curious how developers are handling review now that AI can generate fairly large pull requests. I tend to focus first on the overall architecture, changed files, tests, and possible edge cases rather than reading every line immediately. What does your review process look like before you merge AI generated code?
I've tried the build-in-public thing a few times. Sharing milestones, posting screenshots, writing little updates. And honestly? I'm not sure it ever moved the needle. A few likes, a couple of "this looks cool" replies, zero meaningful signups.
I see others do it and they seem to get traction from it. But I can't tell if that's because they have an existing audience, or because their updates are genuinely interesting, or because they've just been doing it consistently for years.
For anyone who's actually seen build-in-public convert into users or revenue: what was the specific thing that worked? Was it a particular format, a platform, a frequency? Or is it mostly just a slow compounding thing that only pays off over a long time?
I think a pitch deck is almost like a passport for a startup =)
It needs to contain all the important information about the business, but at the same time, it has to be presented in the right, clear, and aesthetic way.
I m realizing how difficult that balance actually is...
Too much information - nobody wants to read it. Too little - the business isn't clear. Too much design - the message gets lost. Too little - it becomes just another boring document. So, I have a lot of questions =D
