Google shipped Gemini 3.8 Flash this week and every post about it so far is coding benchmarks and "look what it built in one prompt" demos. Which is fine, but I don't write code for a living, so it's not telling me much.
Genuinely curious if anyone's actually thrown real work at it yet, not a toy prompt. I keep seeing "our best model yet" every few weeks now and I'm starting to tune it out a little, which probably isn't a great instinct given how fast this stuff moves. Anyone else feel that way, or am I just being lazy about keeping up?
I ve been scrolling through the platform today, seeing dozens of launches, upvotes, and celebrating teams. It s inspiring. But it also made me think about the personal sacrifices behind these numbers. Behind every "Successful Launch" post, the sleepless nights, impacted personal lives, and that anxious feeling that your self-worth is entirely tied to your metrics. How do we know if all our efforts will truly pay off? How do we actually distinguish between genuine persistence and just over-committing to an unviable idea?
While building an early-stage SaaS product, I have found that AI makes it surprisingly easy to turn an idea into a working feature but, deciding whether it is the right feature to build is much harder. At our stage, we rarely have enough usage data to be certain and we usually have to combine a handful of customer conversations, early usage pattern and our own judgment. When the signal is unclear, we try to build the smallest usable version first and learn from it.
For other early-stage founders, what gives you enough confidence to build a feature when the data is still limited? Do you rely more on repeated customer requests, observed behaviour, willingness to pay, or founder judgment?
Since I started developing saas, I always used the approach of first developing the saas and make it market ready and then ship it. But, after a few times and through a few post on different social media, I came to know that you should first conduct a research and ask your customer whether they would pay for your saas. I was very curious with this approach as, why would anyone willingly want to pay for the saas (in the future) which doesn't exist and the niche has competition. Does this approach work? What is your take on this?
My deploy config was rejected today before a single step ran. One argument was over 10,000 characters, and most of that argument was comments I'd written inside it to explain the flags. Comments outside that block are free. The ones inside count toward the limit. I didn't know there was a limit at all until the whole thing refused to start. What's the dumbest hard limit you've hit, and did you find it in a config file or in production?
Early on, we spent a lot of time trying to sell into a market built around long-standing vendor relationships.
When security and trust are involved, being the new company in the room is a pretty big disadvantage. Even if the product is good, getting an institution to switch is a whole different problem.
So we changed direction. Instead of selling to the institution, we started going directly to the people who would actually use the product.
It's definitely a slower path. We're building trust one person at a time instead of closing one deal that could potentially bring in thousands of users.
I ve noticed something weird when generating images with AI.
After generating and editing images for a while, sometimes the style or texture from earlier images starts showing up in completely unrelated generations.
For us this is a dilemma of letting the users to use our tools and generate content in our time travel platform or use it internally and building and delivering the high quality content. user can have the ownership and engagement in the UGC style but the QA and content control could be nightmare, but with high quality company generate curated content the quality and engagement is secured for users but we may give that ownership feeling away. which one you choose and how you think anyone can handle this situation?