By pointing out the obvious you miss out jumping on the bandwagon of everyone writhing in pain over how devastated they are for the environmental impact. Whenever AI is brought up you have to remind people how unsustainable it is and how it’s all about to fall apart and how the value isn’t there, among other topics. Off topic/on topic I’m reminded of death reports during COVID for particular states. When I went to go and look at the statistics of years prior to compare, they were at par if not less than the few previous years. Just an example of uncontrolled (mostly manipulative) outrage in action. I’d like to expect better of HN but I don’t: I’ve lost all respect for the moderation (dang and now tom) here over the years.
What he is (was) talking about and what you are talking about are two different things. He saw that opening scene as an introduction of a Fantastical movie. One that would continuously pit the small and insignificant man against a noble but ultimately indifferent nature that far dwarfs anything in size. It’s the kind of stuff that you get concept artists to drool over. Imagine the kind of scenes you could have with that.
The rest of the movie compared to that expectation is a creature feature with standard elements. The one you refer to is simple foreshadowing. It’s not a cause for master class labeling. The staff that made all those dinosaurs deserves that credit, as they pulled off something very brilliant.
Yeah that’s juvenile trolling that gets people kvetching. That’s the whole point of it. It’s toilet humour level bait and the publications get a kick out of posting it acting all shocked.
MechaHitler? Fucking lol.
If you don’t want to stoop down to Musk’s level of rhetoric, then grow up and ignore the clown.
No. The “new generation” now knows what the outcasts and the undesirables of the “old generation” felt like. The more I speak to the younger crowd the more parallels I find which just means the “default” shifted towards a society of people who don’t know a different way, but are unaware of what goes on around them. The undesirables of the old knew, but couldn’t do anything about it.
It’s like people who are bewildered when newspapers say bankers got caught having a massive orgy of some 50+ attendees in a hotel in Switzerland. There is always a party, but you’re not invited. Simple as.
Correct. This data doesn’t meet criteria for polymorphism because insured and uninsured processes from a book keeping perspective have very distinct flows and requirements in reality. Using OOP here is a mistake. Straight forward procedural code in-flight as well as any batch jobs should deal separately with insured and uninsured data and there should be zero overlap unless we need to extract aggregate data like how many payments in total and what’s the total amount. For those situations you can use a separate domain model that distinctly deals with these queries as value objects themselves if you want to go down that rats nest.
Other top level comments covered what I wanted to say but my comment is the OG one. I deal with payments, transactions and all that with multiple currencies and other complexities. Just keep it simple and don’t use OOP for this stuff it’s the wrong tool for the job.
There is no polymorphism. There’s nothing polymorphic about the 2 types of payments. And furthermore you’re likely to run into situations where you have to have both an insured amount and an uninsured amount for a given treatment/procedure. So now you’re dealing with arrays of heterogenous data.
The process for handling the two cases is distinct. This is the classic OOP issue of trying to use a Shape object to represent both Box and Sphere. Just don’t. Stick with transaction/linear code and use transforms as it makes sense for certain cases (ie, MVVM style). Handle the two cases distinctly so there is no room for ambiguity.
People get this confused and they think it can’t be simpler.
I wouldn’t do this personally because the downstream code very often has to handle differences where polymorphism breaks and you end up having to query the type. Polymorphism shouldn’t be used for data, only behavior, and only in very specific circumstances. Subclassing is a different topic.