Lanfranco Iwanaga

recently i was checking out the scraper services and it seemed like easy to build at first but when i thought about scaling it, that's when it got really difficult.
still i wanted to know the opinions of the people who use the scraper services and what services do they use commonly in general and their pain point, that way i will just focus on those points and try to build the first iterations.
really appreciate your thoughts on this matter.

Hey everyone,

I don't come from a formal engineering background, but I've been experimenting with how far pure natural language prompting can push a functional full-stack app.

I recently shipped an interactive daily bidding leaderboard where users displace ranks dynamically, resetting every midnight UTC.

Credits look like a solution to variable cost. They're really a way of moving the variance onto the user without telling them.

In Arteza a quick edit and a full multi shot render are about 12x apart in what they cost us to run. Both are priced in the same unit. So someone learns an exchange rate from the cheap action, builds a mental model, then spends a third of their balance in one click and feels robbed. That isn't a pricing bug. We asked them to hold a cost model in their head that we never showed them.

What's worked is putting the credit cost on the button before the click instead of in a docs table. Boring fix, and it cut the where did my credits go messages more than any price change we made.

The part I haven't solved is failures. A bad output still burned the compute. Refund it and people retry until they like the result. Don't refund and credits feel like a slot machine. We refund and eat it, which won't scale.