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?