sebastialonso
HN is very cesspool-ly indeed
Granted, grandparent comment used _charged_ words. Let's rephrase: labor is used to ultimately provide owners more money than they put in.
Is that not a fair assesment of the real world? Who starts a company to lose money? Who starts a company solely for "creating jobs"?
What exactly is the beef with grandparent comment? Is it just the negatively charged words? It's the rephrased version beef-inducing as well?
Every action in the known universe (and surely in some unknown ones too) results in a trade-off. This is maybe the only precept on software architecture that doesn't "depends" on anything and is closer to natural law.
It's not measuring the "useful" kind of stress, like when you're on-call or in active incident handling.
It's just measuring how you approach problem solving and coding while being judged and looked at, on the spot, which is *hardly* a common scenario in real life!
As an system-oriented person, give me a healthy combination of available, battle tested, new and promising solutions, fine-tuning weaknesses with strengths.
Go to the stadium to solve your local team/visiting team issues. You are all falling to Big Fossil antics.
"Time is not a thing in math" is not understanding what math is. Time is another ideal object following certain rules under a given domain. Programming is coming up with objects of different size, with different characteristics, with interact at different points in time, i.e. following certain rules.
I've always found the car metaphor to work very good to understand this: A car is a machine that can transport itself to point A to B (some other rules apply). There are different types of cars, but you certainly haven't understood the definition of you say that something is not a car because is not a Volvo, or because it doesn't look like a Ford, when it's clearly able to transport itself.
Math is the study of ideal objects and the way they behave or are related to each others. We have many branches of mathematics because people have invented so many objects and rules to play with them. Programming is nothing if not this very definition. The fact that you don't have to "use math" when programming is not really addressing the point, it's like saying a car is not a car because it has no discernible brand.
I agree is not a useful grouping in practice. I'm just interested in what makes you think like you do.
The thing is, you didn't mention that bit to the LLM. You mentioned a completely different scenario, basically two persons who happen to be cousins. But you used the same style when presenting it. The issue is not a hidden contradiction or a riddle, the issue is that the LLM completely ignored the logical consequences of the scenario you presented.
It's like asking it about the name of the brave greek hero in the battle where the famous Trojan Cow was present. If you get "Achilles" is obviously wrong, there was never a Trojan Cow to begin with!
Sharks are not vicious killing machines. Hungry and aggressive instances of sharks are killing machines.
Networks that don't work with that model, tend to be much more wholesome. And they work.
It's like complaining about how dangerous an axe is because it's super sharp. You don't complain, you just don't grab the blade section, you grab it by the handle. And
jj has no evidence today to support the idea that it will be a main tool in the future. An even heavier burden of proof comes from the idea that it could be adopted by mainstream forges, so it's certainly not an argument on how jj is better than git.
> The centrality of computing stems from the fact that it is a technology that has been changing the world for the past 80 years, ever since the British used early computing to change the tide of war in World War II.
I take issue with the idea hinted at here. Just like Algebra and other branches of mathematics were invented to deal with daily down-to-earth issues like accounting or farming, you'd be hard pressed to find a consensus that mathematics "aims to explain the real world".
The historical origin is very clear, but the train left the "real world" station pretty fast, "unreasonable effectiveness" notwithstanding. Am I to understand that because Enigma was broken using a physical machine, the field is bound to study physical reality? To me this feels as uncomfortable as to refer to astronomy as "telescope studies".
> I believe that thinking of TCS as a branch of mathematics is harmful to the discipline. [...] > Theories that fail at this “explain/predict” task would ultimately be discarded. Analogously, I’d argue that the role of TCS is to explain/predict real-life computing
Yeah, if you hired me to design harmful approaches, not in a year I would have come up with something as harmful as this.
To me the point is not concerned with usefulness, is with reliability. You could get correct answers out of the agent, but how often do you get correct data versus gibberish? It's an extremely important metric to consider, and it's the same reason you wouldn't hop into a self-driving car in the real world if it can drive flawlessly in a straight line, but once every three intersections turns the wrong way.
Instead of showing rules as a linear list, I'd suggest it's easier to visualise it as a tree, or simpler still, as a series of nested ifs.
Maybe it's easier to stop projecting our ideas of what "ought to be" into entities who inhabit a system in which those ideas don't have value, like for-profit businesses, no?