Bookmarked from Qreates @qreates
Come through 🔥
Simply upload your product photo, prompt & generate!
Simples :)
keep going and keep creating, it’s hard to lose with these actions in daily motion
5633 bookmarks · page 122 of 226
Come through 🔥
Simply upload your product photo, prompt & generate!
Simples :)
You can Crawl entire website with Claude 3.5 or GPT4 with @firecrawl 💯
Its open-sourced and code in github
-----
Some benefits of firecrawl
1. handles crawling (with or without sitemaps)
2. runs headless browsers scalably
3. handles bot protections and proxies
4. a team of dedicated engineers to solve the millions of edge-cases on the web for you
5. quality formatting to markdown by default
Beautiful soup doesn't generalize, thats why we built firecrawl
keep going and keep creating, it’s hard to lose with these actions in daily motion
I've submitted my 15th app. Someday my turn will come. Luck favors those who don't give up.
Chasing Reusable Code is Futile. Reimplementable Ideas survive better across time, platforms and languages.
"You have to assemble your life yourself, action by action." — Marcus Aurelius
Nur wenige Monate vor dem terroristischen Überfall der Hamas auf Israel, haben wir Prinz @PahlaviReza in München interviewt und ihm einige Fragen über Israel und den Iran gestellt. Hier ist eine seiner Antworten.
SUCCESS
“Waiting is painful. Forgetting is painful. But not knowing which to do is the worst kind of suffering.”
― Paulo Coelho
Too many founders are building financial management tools that help you track your net worth—when the real determinant of quality of life (literally: the house you are qualified to buy and live in) is borrowing ability.
Measuring and tracking this is far more important—and virtually impossible with today’s tools.
All you need to hit $10k/month with SaaS is:
Combine those with time and consistency, and growth will follow.
Understand the superior value of getting what you want through hard work.
You’re lovable when you’re not liked by everyone.
Sleeping Squirrels in their nest on someone's window ledge.
Just tried dumping a draft of a blog post I’m working into NotebookLM and having it generate a podcast conversation out of it… and I think this might be a genuinely useful writing review tool
It offers useful alternative lens for checking that the points I’m trying to get across are present and clear-enough that a weird AI thing spots them - plus it helps extract the core themes so I can make sure I’ve covered what I wanted to cover
I've gone from idea to execution 3x on this playbook in one year.
RizzGPT ($2.4m arr), Umax ($5m arr), and Cal AI ($8m arr).
I'm no longer doing it. Ask me anything and I'll share all of the secrets.
My fav anti-under-engineering trick is to use timestamps instead of booleans in the database.
that way you know when it was set to true
super useful for debugging later
So over.
Biological Neural Networks:
In quantum mechanics, the observer effect boils down to the idea that the world state is lazily evaluated (i.e. you only compute something when the result is causally needed to evaluate something else). This makes the many-world interpretation very icky: MWI requires "compute" and "storage" in the below-world substrate to be free and in infinite supply. But the entire point of lazy evaluation is to save compute and storage!
Basically: if the universe has made the design choice of lazy evaluation, it implies that whatever resources it runs on must cost something, which in turn rules out the infinitely resource-hungry many-world design choice.
We built and launched a viral AI product in 2 months (at Google!). Here's how: Our little NotebookLM team has had a crazy few months and is proving that small, nimble teams not only exist within Google, but can move fast and have significant impact.
Our newest feature “Audio Overviews” has taken over the internet the past few days. The team has been sprinting - we went from idea to prototype in weeks, then launched publicly in under 2 months.
It’s not perfect (yet!), but that’s the point. Here are a few takeaways:
1. It's about building products with our users, not just for them. We’re not waiting to launch, we’re shipping early and iterating. Tech is evolving faster than users can possibly know what they want. We're often anticipating needs for V1 then working alongside them to improve. Example: Very quickly we saw a massive user desire for in-line citations so our team quickly pivoted to build and launch. (Join our discord!)
2. Built-in not bolted-on: We’re building net-new, AI native products. This isn’t just AI for the sake of “AI”, we’re working to bridge the gap between state-of-the-art research and human problems. Audio Overviews are great because they sound amazing, yes -- but useful because they are (1) source grounded and (2) an easy one-click way to study and digest your own information.
3. Meetings are spent building, not just talking about building. We’re collaborating, deeply. I am the only UX designer on the team so we have to make every moment count. @raiza_abubakar, @stevenbjohnson and I are constantly strategizing and iterating together.
NotebookLM represents a new era of product development within Labs at Google. We're putting user feedback and community engagement at the heart of everything we do. We’re building quickly and have a lot more coming soon..
The audio below is made with the NotebookLM Audio Overview feature using only my LinkedIn post! If you haven’t tried it, I highly recommend it. We want to make it better for you!
It’s been awesome to see so much investigation into the product by @karpathy and @emollick.
I recently discovered a part of the internet where a bunch of cracked 18-22yr old indie hacker kids from no-name unis run bootstrapped mobile apps growth-hacked on TikTok.
Each app has 100k+ monthly users and makes $1M-5M/yr.
Never underestimate the kids.
My September 2024 numbers for ScreenshotOne.com for friends and to reflect in public:
💰 $10,506 (+$793), 8.2% growth rate.
☘️ 28 months since the launch.
🫂 267 (+8) paying customers
👌 $39 ARPU and $1,348 average lifetime value.
💔 7.1% (-1%) revenue churn rate and 10% customer churn rate (-0.4%).
📸 17,163,877 (+2,977,137) API requests.
Of course, crossing $10K was huge, but my best win was that I could travel for the whole month in Asia working only for a few hours per week—answering only support tickets.
I am finally back home and ready to ship for fun and for my customers happiness—already pushing to production 🔥