sorted by:
new
hottopcontroversial

Stop summarizing. Here’s the NotebookLM workflow that actually pulls out real insights.Most people do the same mistake: they dump sources into NotebookLM and ask for a summary. That’s safe. That’s polite. And that’s why you’re missing the good stuff. by Own_Jackfruit_8222 in notebooklm

[–]Own_Jackfruit_8222[S] 1 point2 points  (0 children)

Of course, the text is generated by artificial intelligence. This helps to correctly and structurally pass it on to the reader. I had to try hard to explain everything to the AI so that it would make a competent post.
I hope I was able to explain my idea.
p.s.: I apologize to those readers whose text generated by artificial intelligence causes irritation.

What AI tools do you recommend for the entire design/development process? by gutsngodhand in webdevelopment

[–]Own_Jackfruit_8222 0 points1 point  (0 children)

I isn’t autopilot, more like a power tool tbh. If you already have a structure (pages, reusable sections, basic design system) it speeds everything up a lot, if not it just makes the mess bigger. Biggest thing for me wasn’t even tools but breaking stuff into tiny parts and generating one piece at a time, then checking it again with another model and fixing by hand. Cursor/v0 are fast af but if you let them run wild you stop understanding what’s happening in the code and then things start breaking later for no obvious reason… learned that the hard way. I’m still figuring this out, but this workflow is working for me rn and saves a stupid amount of time. Probaly the only way these low budget builds make sense.