I found just now that my telecom operator - Airtel - randomly subscribed me for OTT services and charged me for it. But upon calling them and contesting, they just asked if I want to unsubscribe and then reverted the charges. No threats, pleading, or back-and-forth involved from either side. Mildly surreal.
I wonder that's a new corporate strategy - charge randomly till someone goes through the pain of IVR and spends 15 mins with support. Must generate quite an upside for them if it is indeed a strategy.
> Must generate quite an upside for them if it is indeed a strategy.
This is the same Airtel that auto opened payments bank accounts without customer consent or knowledge while getting a sim card. They even got cash deposited into those accounts from the govt direct benefit schemes while keeping their customers in the dark.
I'm sure its completely "accidental" and they'll have more of these glitches and mistakes in the future.
Very interesting... with the marginal cost of basic software dev decreasing but distribution costs remaining high, I have been wondering how that changes software consumption (1).
I suppose this is one interesting pattern for that.
There's also some more light CBT-inspired stuff: like reminders when you're stuck, off-screen break suggestions (I consider breaks essential to long term momentum), and automatic summaries showing how far you've come when you feel like you've been just stuck in the weeds (I frequently judge myself a bit too harshly till I see the numbers and am sometime pleasantly surprised)
I made this primarily for myself – I'm someone who gets stuck between "I should be productive" and "I literally cannot decide what to do right now." The pattern I noticed: starting anything small breaks the spell, then I can think about actual goals.
The (optional) AI suggestions are deliberately constrained to be actionable (15-60 minutes tasks that ladder up to your goal) rather than generic productivity advice.
Would love to hear if this resonates with anyone else, or if you have thoughts on the approach.
It's fascinating ...didn't think about the Bus Factor at all wrt vibe coding. Feels obvious in retrospect. But I feel there's the other side of software beyond the maintanable, professional-grade software requirements. There are a lot of use cases for basic software to solve that one problem in that one specific way and get it over with. A bit like customized software with little scope and little expectation of long-term support. Vibe-coding excels there.
In a way, I have been thinking about it [1] as the difference between writing a book and a writing a blog post - the production qualities expected in both are wildly different. And that's expected, almost as a feature!
I think as “writing” and distributing new software keeps getting easier - as easy as writing a new blog post - the way we consume software is going to change.
Unfortunately, that's the exact problem here: Google tried to force their Indian application internationally without exactly understanding the differences between different markets (big one is forced mobile number registration, which I understand is not a big deal in India but it's a significant friction in the US). For users outside of India, it is a mess compared to how Apple (and even Samsung at this point) does it.
Is this down through the old Google Pay app, not through the newer Wallet app? I use "Google Pay", as in the payment processor, every day, but it is being done through the wallet app.
Probably, but LLMs seem to gain more understanding from seeing lots of different examples than they do from a few examples of good code so people won't stop scraping stackoverflow.
They also have a voice input only version if you still would like to keep your typing keyboard: https://voiceinput.futo.org/
reply