Exactly. People forget that all the output of these LLMs is only as good as the input data. The moment they stop getting fed the latest data, they get stale. If there's no data to scrape about [LANGUAGE] - then the LLM can't help with it. (Or even if that data is out of date enough)
IE: The death of SO, while deserved, will end up hurting LLMs in the long run.
I disagree. This case is very controversial, at least from the point of view of the parent.
Being reported may be seen as betrayal by the parent, even if it is objectively justified. That could also be the reason why „everyone around“ failed to act, even if they agree.
>Being reported may be seen as betrayal by the parent,
It kind of is no matter how you slice it. You're prioritizing other interests above theirs specifically to their detriment and then saying "it's justified because X". No value for X no matter how legitimate is gonna change the fundametal reality.
>even if it is objectively justified. That could also be the reason why „everyone around“ failed to act,
If everyone around thinks it's justified then they'll have no problem supporting the guy who does want to act. Buuuut, and this is a big bug. "Will support someone narcing on someone to cause the state to take action" is a way higher bar "will support a DIY solution". Showing up to or organizing your friend's intervention is a way lower bar than throwing them under the bus to the cops. What we're discussing here is basically the "lite" version of the latter.
I don‘t like dismissing technologies on the basis of being „magic“, since the magic could often just as well be called abstraction, and the line between them is often personal preference.
The abstracted-away logic in a Laravel application can either be called magic or abstraction, but so can the optimizations of a database query planner.
I think often you still need to know the underlying mechanism, but it is still useful to get the innards out of the way.
It's useful to get "glue" code out of the way while building, but to the point in the article it all becomes very difficult to debug and maintain once there are problems in the that layer.
Spring Boot and other similar frameworks come to mind; by forcing huge amounts of indirection you lose a lot of visibility of your call stack because the convenient "glue" code is now orchestrating everything at runtime, but that code isn't yours, and it isn't easily inspected or fixed.
Generally, they're on the lines of "regulations hurt my capacity to make unlimited money at whomever's in my way's expense.", except with less candidness.
The larger cables tend to have strength members with higher physical bend radius restrictions, i.e. you can't bend the steel or kevlar elements that tightly without breaking things.
The exclamation mark has a reason: if the newly created records fails validations, an exception is raised. Without the exclamation mark, the error is silenced (and the method returns a falsey value). This is a convention across Rails.
Ruby itself mostly uses it for mutating methods (e.g. #gsub("a", "b") replaces the character a with b in a string and returns a new string, but #gsub!("a", "b") mutates the original.
reply