jvuygbbkuurx

That is exactly what is thought provoking. Usually we only learn glimpses of history, not a full distribution about it.

For example my draw died as a newborn (allegedly 50% died before 5), which made me think how many humans never really got to experience life.

Usually I don't care about the economy in MMOs, but in New World it was fun and different when it launched. I played almost exclusively for the economy. Buy and sell orders and separate auction houses between cities. There was many unexpected ways to make money with trading and crafting. The only major source of gold was a single main story quest early in the game, so if you weren't careful you would go broke and struggle. The economy wasn't that advanced, but it was fun watching the players ping pong back and forth with supply and demand.

No. Don't ask a question that AI can answer.

You didn't expect your telemetry system to be used as a telemetry system?

If it's to prevent accidents, it should just prompt user to confirm saving the screenshot with sensitive information.

As it is, it is just an annoyance that requires you to do stupid workarounds like taking a photo of your screen.

Imagine if a password manager didn't allow you to copy the password since you might accidentally paste it somewhere incorrect.

If that is better (and possible) it will be baked in the tools. But is a model that doesn't know python better or worse at swift is what I wonder.

It's actually solved by putting thieves in prison (by the help of flock cameras).

I found it follows conventions and documentation well. So if you have a well designed core, it can easily add independent features without increasing overall complexity. Maybe it doesn't work in some very tangled domains like games, but some basic crud and saas stuff is pretty much a solved problem now with agents. They will trivially add features that humans would have pushed to a backlog forever as not worth the effort.

I don't like the default explanations. But I prompt for small code snippets with explanations of a problem and the solution. This is in the context of extending features, fixing bugs, reviewing new code etc. I still skim the code, but it's nice to have a somewhat thoughtful overview of the key points like database schema, API spec, algorithm or abstraction. It makes it easier to skim a large diff without feeling lost. It also quite often catches some weird choices that might slip through it not carefully reasoning about the code. For me it is hard to understand code I didn't write myself so I have landed on this workflow.

You win some, you lose some. Maybe your coworker juniors became seniors and didn't negotiate higher pay.

Indeed. But there are also delays that cause good feelings.

I still remember the POS in my previous employers cafeteria. It had something like 100-200ms delay in processing a contactless payment card. It felt like an order of magnitude faster than any grocery store (exact same POS device). It was always very satisfying to pay for lunch. By the time you brought the card to the reader it felt like it was already printing the receipt.

I always wonder how it was so fast and if it was just some random dev optimising some obscure edge case.

Maybe download numbers are relatively low

He has served his time for those crimes

Infinity is a ridicilous statement. Even the work that wouldn't have been done before is now time away from work that needs to be done. At worst it's negative x.

Now I'm curious how many things did the AI try unsuccesfully. This sounds like some kind of brute force thing where every branch of exploit spawns N subagents trying to chain it. Just how deep did it go?

It has been quite a slippery slope. Services that used to allow password auth have retired them in favour of bank detail login. I can kind of get it, since it's offloading support to the banks, but it's also annoying since the bank logins themselves are a pain to setup, maintain and use (mobile app only).

It would be nice to have some good standard that is less invasive.

I found it eagerly reversing existing product decisions like changing a user given date into created date, since it thought creating something that is in the past is incorrect. This was not even related to the task at hand at all. I noticed this kind of stuff happens more with ultracode for some reason.

That only matters if you are an investor not if you are a consumer.

Unsafe doesn't disable the borrow checker

I think originally they had good intentions. But they just cannot afford not to pull up the ladder, they raised too much.

Yes, their entire existence relies on training on copyrighted content without permission being ok.

Especially in conditions where AI assisted PRs are tracked for performance.

I had some extra usage on claude yesterday and put several ultra workflows to look for code cleanup opportunities. It made -40 tasks and PRs just like that. This is 10% of all PRs/commits in the project history, but the before and after is arguably meaningless.

Did it take 30 seconds?

The market is priced at expecting AGI levels of breakthroughs. Just a very useful tool for programming is definitely not enough to keep the music playing.

That is literally what most online digital goods already do, like steam.

Explains why it made so many memories on my work machine, but never made one on my personal one. Maybe the project size also affects it.

I meant it like a retailer can buy it without the charge in bulk with a discount, but since the consumers can't, the retailer can increase the price. So the consumer pays more because of a middleman charging the difference.

Ideally there is enough competition between retailers, but obviously that is not true if the consumers are buying from china in the first place.

Instead of adding a fee, you should make the bulk imported item cheaper. If you can't compete then something is wrong, maybe something in single import being subsidized like air mail? If it's not then it's a more efficient system.

And I'm strictly talking about exact same products produced in china, not equivalent products of worse quality.

Why let a middleman rentseek?

I wanted to say thanks for this resource.

I'm founding a fintech startup and have been thinking about these things a lot. It is very helpful to have some general validation and guidance to make sure I'm not making huge mistakes.

I really wanted event sourcing, but thought it gets complicated when events have complex validation rules. I ended up with a mix of state and audit logs which works ok for now.

If the website implements it. What about email preferences? Removing account links? There are many use-cases you might want to redirect a user to, but having to make their own well known for it seems dumb instead of using a more generic one. I guess the more flexible it is, the harder adoption becomes as the usage within a spec might diverge, or it grows outside of the spec and becomes unofficial. So maybe password-reset is correct level of specification.

Anyway discord domain verification can tell in their onboarding docs to put it anywhere. It being well known does nothing. If there was a root level domain verification, then you might as well put it under that. But otherwise why go through a process?