They could also do a plan 3 where they discourage others so they can use it to, say, rapidly build many new products but competitors would have to pay a fortune for the same luxury
> They could also do a plan 3 where they discourage others so they can use it to, say, rapidly build many new products but competitors would have to pay a fortune for the same luxury
Unlikely that they all decided to do this within weeks of each other. Still, like you said, you were spit-balling, not asserting :-)
Fair point. We only have clear evidence they're being more transparent about credit pricing and value, but it's unclear whether that'll make people burn through usage faster or slower.
The fuzziness is intentional. It gives them wiggle room and obscures how much "value" you actually get from $200, a 5-hour block, or a week. That keeps the tension manageable between subscription pricing and pay-per-token API pricing, especially for larger businesses on enterprise plans who want transparent $-per-MTok rates.
If they were fully transparent, like "your $200 sub gets you up to $2,000 of equivalent API usage," it would be a constant fight. People would track pennies and scream any time 5-hour blocks got throttled during peak hours. Businesses would push harder for pay-per-token discounts seeing that juicy $200 sub value.
It's really not. As a one-person IT department I'm now able to build things in hours or days that it previously would have taken my weeks or even months to build (and thus they didn't get done). Things people have wanted for years that I didn't ever have the time for, I can now say "yes" to.
Yeah the ops alone is a huge win. It’s such a win I didn’t even think to mention it ha.
Dangerous too of course. So many times I’ve had subtle unexpected side effects. But it’s all about pinning thins down well and that’s what we’re all still figuring out well
> Is writing it by hand the old-fashioned way not on the table?
Of course it is. I started a (commercial) product in Jan, on track for in-field testing at the end of April.
Of course, it's not my f/time job, so I've only been working on it a/hours, but, with the exception of two functions, everything else is hand-coded.
I rubber-ducked with AI, but they never wrote the product for me (other than those two functions which I felt too lazy to copy from an existing project and fixup to work in the new project).
Absolutely not. I took on some thins that would normally take 5-10 people and many months.
Some people are turn out slop. I was really excited to try and make some impressive shit. My whole life has been dedicated to trying to embody what Apple preached in the early days.
I knew this was coming, but I thought I had a little more time to try and get them over the finish line, ya know?
Maintenance by hand might be achievable, but it’s extremely hard when you’ve built something really big.
I’ve only got so much savings left to live on.
I’m not saying anyone owes me anything, but we all need to pivot and in a lot less sure my pivot is going to work out now
> I took on some thins that would normally take 5-10 people and many months.
Based on what, exactly?
It's very easy to claim some software would've taken you months to make, but this is ridiculous. Estimating project duration is well known to be impossible in this field. A few years ago you'd get laughed out the room for making such predictions.
> I’ve only got so much savings left to live on.
Respectfully, what are you doing here?
Yeah sure, the Apple dream. But supposing AI did in fact make you this legendary 100x developer, so it would to everyone else including those with significantly more resources. You'd still be run out of the market by those with bigger budgets or more marketing, and end up penniless all the same.
I would strongly recommend you not put all your proverbial eggs in this basket.
I’ve pivoted to writing native iOS, macOS, windows, Linux apps. Most of my career has been front end web. It would take me awhile just to learn and practice, vs having my visions working in hours or days
I’m not ready to unveil the thing I alluded to, it’s important to me that it’s good and polished. But I’ve done quite well so far developing in Swift, Rust, Go, and coming up with marketing and design — things I definitely couldn’t do by hand without a lot more time and effort.
https://poolometer.com/
Is one of the things I’m almost ready to call ready. So much domain expertise or tedious math involved — I simply wouldn’t have bothered on my own, pre-AI
I agree it’s a huge existential risk that everyone is also amazing. So far that’s not true. I get hung up on a lot of little quirks, like getting Dolby Vision to play properly on Apple Silicon without Vulcan. Something I accomplished after about 2 weeks of relentless determination.
To be clear I’m just trying to answer your questions honestly. I understand the situation. It’s almost to my benefit the harder it is for non Software Engineers. But in our current reality, when I’m not launched yet, it’s more stress
> So much domain expertise or tedious math involved — I simply wouldn’t have bothered on my own, pre-AI
This is what I was alluding to. AI did not let you write software you couldn't otherwise make, or let you write it faster. You skipped doing the research because AI gave you plausible results, but without doing the research yourself you cannot be sure of it's accuracy.
That isn't faster software development, it's reckless software development, and nothing really stopped you from doing it before other than your own recognition that pulling numbers out of your ass is a bad idea.
> I agree it’s a huge existential risk that everyone is also amazing. So far that’s not true. I get hung up on a lot of little quirks, like getting Dolby Vision to play properly on Apple Silicon without Vulcan. Something I accomplished after about 2 weeks of relentless determination.
That would be "doing the research", and as you have observed, is the slow part then and now.
The only catch is that you’ve spent many $1 and you don’t get any of those $10s unless you get over the finish line
In that sense your analogy is kinda good. I totally agree the current situation is like getting my solo start up funded and subsidized … but with only like 4 months runway now that the prices are skyrocketing, vs ~2+ for a typical YC venture
Yeah, but... it's rocketing for everyone at the same time on all the providers at once.
IOW, you are no further behind nor further ahead than your competitors compared to 1 week ago, 1 month ago, 1 year ago and 1 decade ago.
Everyone has the same tools you have. The only advantage you get is if you make your own tools (I did that, and pre-AI, was able to modify my LoB WebApps at a rate of 1x new API endpoint, tested and pushed to production, every 15m).
My comment was about the rapid and sudden cost spike of something happening unexpectedly.
They announced 2x tokens with months of notice. This announced this with no notice.
Me as an individual making a go solo is not the same as thousands of funded businesses having free credits, subsidized plans and bottomless AI budgets.
For a short period this was a massive equalizer. Now it’s a tool for those who can afford it. That’s a big shift.
—
Why is it that a person cannot express their own circumstances or opinions on this site without it turning into an argument? It’s so deflating.
Ultimately, we need to know the true cost of this technology to evaluate how effectively or ineffectively it can displace the workforce that existed before it.
If my math is right, assuming a mix of around 70% cached tokens, 20% input tokens, and 10% output tokens, it breaks even with the old pricing at around 130k tokens per message, or about 13k output tokens per message.
With the hidden reasoning tokens and tool calls, I have no idea how many tokens I typically use per message. I would guess maybe a quarter of that, which would make the new pricing cheaper.
MiniMax M2.7, MiMo-V2-Pro, GLM-5, GLM5-turbo, Kimi K2.5, DeepSeek V3.2, Step 3.5 Flash (this last one is particularly cheap while still being powerful).
But it was well understood that the subscription was heavily subsidized. Whether or not it was a "separate product" doesn't matter as much as the fact that pricing was not sustainable.
It was not well understood that it would stop being subsidized without notice.
Does that just not matter in modern society? I’m an asshole for expecting the product I pay for on day 1 to be the same on day 8 and 29 of a 30-days subscription?
I agree with you there, but I think that may be the only reason this app isn’t cast in a darker light.
I can also imagine that with SF living expenses that there are a lot of people without a big safety net
I don’t really mean for this to be related to any one person. The general population doesn’t have a choice but to sign terms and get the severance , in general, in America
Nobody forced her to break her contract and thus come up against that. She would have been perfectly fine on the leftovers from ~$500k/y while searching for her next job. The parent makes out like she simply had to get the extra money, lest she starve to death. Which is patently ridiculous.
I'm pretty sure that the infotainment hack was completely orthogonal to whether it was Beethoven, Iron Maiden, or blissful silence.
Having said that, a successful car infotainment system attack on android auto or apple carplay could, of course, compromise your phone.
So it's up to you whether you decide to cope with that possibility by breaking the law and navigating with a handheld device, or simply declining to do banking on your phone, since successful car exploits mean the attack surface against your phone is much larger than you might presume.
I was responding to a comment about the security implications of letting the infotainment system interact with the vehicle controls, and I referenced an incident where someone compromised a car via that.
I have no idea how CarPlay would compromise your phone given apples sandbox but whomever finds it is gonna have a multimillion dollar payday since iOS jailbreaks are quite valuable.
> Paying with your phone just seems like one of those separation of concerns problem.
Followed by:
> You could then separate the audio system from your car and drive around with a boombox
The first discusses behaviors of end-users. The second was a lame attempt to take the mickey of that, which is why my response was that clearly indicated that, to my knowledge there are zero security implications of playing your music on your car.
This remains true.
You are discussing design flaws, not user behavior flaws, which is why I pointed out that the design flaws you bring up, in addition to doing you bodily harm, could conceivably also be part of an exploit chain that validates the original poster's concern about using his phone for banking.
But I still sincerely doubt that the choice of playing Beethoven or Iron Maiden either directly places you at risk, or makes a difference to the ease of exploiting any design flaws in your vehicle.
It’s increasingly apparent to me that even when it’s not the republicans, it’s still the republicans. Eg education and how incredibly stupid many otherwise good, lovable and loving people are. They cheer for growing the population AND suppressing them so that they can extract their votes.
It’s so blatant and so disgusting.. and yet the realization has no effect. Just like when the church pedophiles were exposed (literally next door) it had no effect whatsoever on their congregation.
As an outside observer (of some decades), the US Democrats are enablers of the Republican / MAGA excesses.
They haven't pushed back hard enough against Citizen's United, the obvious creeping threat of the Federalists takeover of the judicial pipeline into the Supreme Court; the criminal conviction of a POTUS was left to slide, and the list goes on.
Things like properly independant election oversight, district boundary setting (no party partisan gerry mandering), and a host of other boring details matter to keeping a democracy clean and fair.
yeah it’s totally plausible that Google would risk the reputation and legal status of its global multi-trillion empire to dunk on one of the handful of people who have the near-unilateral authority to dismantle them
Also - there's zero chance any employees at Google could decide to leak the contents of a specific inbox. That'd be an insane security hole which would've been exploited multiple times already.
Just spitballing.
reply