HN user

schwede

136 karma
Posts3
Comments64
View on HN
Understand Anything 3 months ago

I agree with the sentiment on many of these comments. Understanding something is work and that can’t be offloaded to others or even LLMs.

Isn’t this still true for the large language models and math is detected and handled by an external tool? Anything you can give as a source for the latest state of the art?

One reason is that AI can create PRs at a scale that can just overwhelm maintainers not to mention drowning out non-AI PRs.

This account seems like LLM slop looking at the post history. Who starts every post ‘from Japan’?

I don’t want to interact with hidden chat bots on HN. The irony of this comment about accountability is also frustrating.

Sending power outage context to the vehicles does not seem like enough of a response. I hope at least they have internal plans for more. For large, complex systems, you want multiple layers of protections. The response feels way too reactive when they could use this incident to guide improvements across the board.

Maybe I’m just a skeptic, but it seems like a software engineer or SRE familiar with the application should be able to come to the conclusion of load testing fairly easily. For sure not as fast like 80 seconds though which is impressive. As noted you still need an engineer to review the data and complete those proposed action items.

I think the idea is you could still have a page in the UI that shows archived data but you wouldn’t do that normally with a soft delete. The lifecycle thing makes it up front with the user instead of hiding soft delete as an implementation detail.

No YAML 5 years ago

My interpretation is that since json is JavaScript Object Notation, JS objects can clearly have comments so why limit their usage in json?

TypeScript 4.1 6 years ago

They are probably talking about accepting serialized data coming from a network request. Typescript doesn’t help at the edge if you just cast your JSON blob into your application model.