HN user

jvuygbbkuurx

89 karma
Posts0
Comments42
View on HN
No posts found.

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.

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.

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.

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?

Why are they so specific?

Why password-reset instead of a more generic link tree?

Why discord domain verification instead of domain-verifications with a dynamic list on entries?

Seems like a waste of time. I would just define my own spec outside of well known for my use case.

All of these post are missing actual comparisons on results. I read exactly opposite 'you should do x' everyday. If TDD actually was better it would simply be in the system prompts already.

The problem wasn't the view didn't work. The problem was the view didn't work after something else had been done.

You can't test every permutation of app usage. You actually need good architechture so you can trust your test and changes to be local with minimal side-effects.

Maybe it depends on the application, but web servers are effortless with something like axum. Libraries can do a lot of heavy lifting to expose straightforward coding patterns. Never had any problems like you desribed with database connections and such. In rust with db pools things just work and get closed on drop etc. I would never even consider making a higher order function for that.

Only other language that I think gets close to rust ergonomics is Kotlin, but it suffers from having too many possibilities for abstractions.

My problem with bevy isn't the basics, but the architecture. I always feel like I'm making wrong decisions on if something should be a component or a field, and how it interacts with other stuff in systems. I just feel like I'm making an unmaintainable mess, but I'm not sure how it could be improved.

I think that is what makes it great, because it makes it sound absurd.

If it was just talking about carbon based lifeforms it wouldn't land the same way.

That's what the contract would typically say. But it's not uncommon to have accelerated vesting either when parting on good terms or with severance.