In my experience, both Claude and codex are way too good these days that I don’t have to selectively create a prompt with just the right files. I just say something like “look at the current changes in the repo and generate a good commit message”. In most cases it does a good enough job that I only have to add some small specific details or take out something irrelevant.
Rarely do I have to prep a prompt like this nowadays.
I am curious, what kind of work do you use Claude for that sometimes requires hours of working. In my case, I have never seen it go off for more than 10 mins and even that is very rare.
I had the same thought. TBH there is nothing in those individual sentences that read like AI but when you read them all together I could see it too. I dunno what it is, only way I can describe it is that it does not sound like a normal human but rather a monologue from a character trying to sound impressive with each successive sentence.
My introduction to Feynman was more from other science communicators either quoting him or retelling some story about him and initially it formed a mental picture in my mind that he might be one of those personalities more famous culturally than for his actual scientific achievements. Like how in sports often the more popular players may not be the actual “best” one purely from the sporting skills pov.
But then I read more about him and yeah, he is indeed the real deal.
Hi there, I was looking to get a NAS that I can just install and not have to worry about maintenance too much and senility was at the top of the list. If not synology what would you suggest?
One benefit is that it makes these operations lazy. There are no intermediate lists created when you call a map on a stream. If map were a method in a list, it would need to return a new list. And if you have multiple such maps etc, it would create more such lists for each map invocation.
From what I recall, Reddit uses AWS extensively. Could they not have replaced RabbitMQ with SQS? You get the near unlimited horizontal scalability, extremely good uptime, guaranteed at least once message delivery and for the case of a worker crash, the messages will become visible again after the visibility timeout (since they wouldn’t have been deleted by the worker).
A while ago, I had attempted to do it the Rust style with a Result type in Java (where it is called Data oriented programming) and the result is not great. I was fighting a losing battle in a naive attempt to replace checked exceptions but still retain compile time type safety.
They thought Alexa will enable users to buy more from Amazon just by voice. But most users turned out like me. I would not spend a single dollar on Amazon without actually seeing the item on my mobile or desktop. I wouldn’t even add to cart via Alexa. That’s not an ideal user for device and service that requires hundreds of millions to run.
Not really. I have done multiple AWS pricing and costing exercises while launching services and there was never a direction from the VP to sell it lower than what it costs to build and operate. Cost to build and operate includes everything from salaries, infrastructure and many other line items. And usually things are projected 3-5 years into the future and P&L analysis must show that eventually the service will make a profit. It does make some assumptions about minimum customer adoption for the profit margins to materialize which eventually becomes part of the product and sales teams goals.
The costing model does allow losses to be incurred in the initial years because building the thing is more expensive at first but then it should settle down and revenue should outpace expenses.
What can happen with these open source products being launched as a service is that that initial cost can be cut down by as much as 50-75% but rarely more than that because you still need to build all the surrounding infrastructure, documentation, UI. It still gives AWS an advantage by relying on an existing body of work they can start with where many problems have been thought through and solved. Also you will likely get a good product roadmap skeleton ready to be prioritized which otherwise can be a huge time sink.
In a nutshell, no. AWS won’t sell a service at a loss (there are exceptions of course) but there is room to incur a loss at the beginning but it is priced to eventually turn a profit. Whether that happens for every service in reality is a different story.
Rarely do I have to prep a prompt like this nowadays.