willsmith72

so.. optimistic ui? like upvotes on hacker news since forever?

this is disgusting corruption, a direct wealth transfer from the many to the few. shame on everyone involved

aren't you conflating being 10x as smart with code that is 10x more complicated?

the relationship should be the opposite, the smartest people can write the most readable solutions

anyone else's claude code (native install) not able to update to 2.1.154 to get 4.8?

edit: nvm was just my library network

can we stop throwing around the term "profitable"? didn't they say "operating profit"? so so different to actually making a profit

i agree. but the parent was talking about share price. my point is exactly that "a profit perspective and revenue for shareholders" i.e. driving the share price up. if that's not the goal great, i would love if more companies took that approach. as long as employees are happy (ie their comp doesn't assume stock growth like many do), good for them

that's fine, to me it should be fine for companies to exist like that

but it doesn't match the archetype of a "growth" company. to the commenters talking about the share price, if you want a consistently growing stock, that's not the way to do it (not saying it's right or wrong)

the knock on them is exactly that, 20 years later they're just a file storage saas. the idea was they must be able to expand the surface area over time

thank you!! missed the public launch

wow thanks. I saw the initial announcement when it was still in private beta, but have been less online lately and missed the public launch. Awesome!!

Yep I made the switch a couple of years ago for all of my projects and never looked back. Workers, D1, R2, queues, containers, KV

Still using AWS for email sending so that will be great when it comes

There's feature flags then there's staged rollouts gated by multiple variables with statistical analysis

to be fair, even though they have "working backwards" and "customer obsession", amazon has always been about making lots of different experimental bets. Bezos:

> To invent you have to experiment, and if you know in advance that it’s going to work, it’s not an experiment. Most large organizations embrace the idea of invention, but are not willing to suffer the string of failed experiments necessary to get there. Outsized returns often come from betting against conventional wisdom, and conventional wisdom is usually right. Given a ten percent chance of a 100 times payoff, you should take that bet every time. But you’re still going to be wrong nine times out of ten. We all know that if you swing for the fences, you’re going to strike out a lot, but you’re also going to hit some home runs. The difference between baseball and business, however, is that baseball has a truncated outcome distribution. When you swing, no matter how well you connect with the ball, the most runs you can get is four. In business, every once in a while, when you step up to the plate, you can score 1,000 runs. This long-tailed distribution of returns is why it’s important to be bold. Big winners pay for so many experiments.”

Let's not make air travel the customer experience bar for anything please

People often build their career skills on proprietary tech. Photoshop, Figma, Java, AWS architects

at what volume is the membership worth it?

4 shops/year I wouldn't have thought would justify the cost

what does it say when you feed it a real Mickens article? (a recent one not in the training set)

i wouldn't be too impressed at n of 1

> If it’s $220 worth of value for $200 - I get it.

Wrong comparison. If a competitor gives you $230 of value for $200, of course you shouldn't pick the $220 one

But that's just paying per use right, not with the subscription which is way better value

it's an SMB, if you need redundancy on every 3rd party dependency your business will die anyway

better to take the risk for most things. if the worst case happens and you have to migrate, you migrate. otherwise you risk overengineering upfront and guaranteeing reduced productivity rather than risking it

You must be crawling on your bike I'd love to see that

Wait Kim and Selena are irrelevant? I guess I'm not keeping up with the times

Wow so that's why you did #2? The explanation in the CLI is really not clear. I thought it was just a suggestion to compact, no idea it was way more expensive than if I hadn't left it idle for an hour.

You guys really need to communicate that better in the CLI for people not on social

Being "more" open than something totally closed doesn't make you open. The name is still bs

That's such a poor way to communicate a number. I take it they mean an increase of up to 35%?

yeah they all suck at ui. have you given it a feedback loop? update code, screenshot, read image repeat etc. that's the best i've found as long as tokens aren't a concern

this sounds... really slow. for large changes for sure i'm investing time into planning. but such a rigid system can't possible be as good as a flexible approach with variable amounts of planning based on complexity

this doesn't add up. the 20k is in API costs. people talk about CC losing money because it's way more efficient than the API. I.e. the same work with efficient use of CC might have cost ~$5k.

but regardless, hiring is difficult and high-end talent is limited. If the costs were anywhere close to equivalent, the agents are a no-brainer

depends, "out the nose" is relative based on what else you could be doing and what else is out there

and no job i've had considered 9-5 40 hours after a 1 hour lunch break

including downdetector... that's annoying https://downdetector.com/status/npm/