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.
> 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
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
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.
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.
It’s kind of a rug pull to effectively raise the price like 10x. I can’t afford to finish some of my projects with this change
Is writing it by hand the old-fashioned way not on the table?
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.
5 replies →
> 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
4 replies →
Not really. Many scenarios where that would mean spending 50x the time or hiring a team.
What am I an assembler programmer now?!? Am I to plug wires and flip switches!?!
/s
Sounds like saying my plan to get rich buying up $10 bills for $1 hit kind of a rug pull in that people aren't selling them for that price anymore.
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
1 reply →
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.
I don't think you can call it a rug pull when everybody saw it coming from miles away
I avoided Claude code and such the first few months because I thought it was all billed by the API. Which I knew was not worth it to me at all.
Then I realized I was an idiot and this was magic.
But it now seems more like an introductory offer to use the API, as opposed to an alternative product / way to use their API product.
I thought it would get increasingly expensive, like say the $200 plan becomes $400.
Switching these plans to API metering doesn’t feel like it’s a separate product anymore?
1 reply →
That is okay.
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.
Agreed, this has to happen and the sooner the better.
There are plenty of good models on Openrouter that are very cheap, maybe it's time to experiment with alternatives.
what are some of them?
3 replies →
[dead]