Teachers not having the time to muse about such ideas and instead needing to package everything into a presentation appropriate for an entire room full of children is one of the more obvious failure modes of industrialized education.
10 / 3 will never = 3.0.
It is sad you still haven't learned this lesson after many decades.
I hope I'm never on a bridge you build or plane built to the specs you write if you truly think 10 / 3 = 3.00000.
It is perfectly reasonable to define 3: ℕ = succ(succ(succ(zero))). It's also perfectly reasonable to define 3: ℝ as the image of succ(succ(succ(zero))): ℕ under the canonical embedding. Or you can define 3: ℚ with the obvious element. You can also define 3.0: ℚ or 3.0: ℝ as the obvious elements. If you were really a deviant, I suppose you could even define 3.0: ℕ, and people would roll their eyes, but everyone would understand you. Obviously, there are reasonable ways to define things so that `3 = 3.0` is a meaningful sentence (typechecks) and also literally true.
Again, different conventions are used in different contexts. The "user" of mathematics should pick the conventions and notations that make sense for what they're doing to communicate what they're trying to say. That itself is an important lesson. The sigfig convention you learned in middle school isn't the word of God.
Not being aware of these things to be capable of musing about them is I suppose another issue with our education system.
Similarly, we calculated those ± values using the chain rule/uncertainty propagation, not with the simple decimal place rules you learn as a kid. I assume no one serious uses the child rules when CAD software can just as easily use the real ones.
> we calculated those ± values using the chain rule/uncertainty propagation
Yes, that's common in detailed engineering documents. It still doesn't change the fact if I ask for 3.000 and you give me 3.001 I'm not going to consider that in-spec despite not giving a ±. It's assumed if I wrote it out to that decimal point I'm caring about that level of precision.
> Using decimal points to indicate uncertainty was not a thing I believe I did after high school
Well, I'd imagine since the topic of lesson was understanding whole numbers at a basic level this was probably a high school or lower class, probably more like elementary or middle school. You know, in that time when you did use decimal places to indicate precision. This person wasn't talking about losing points at their engineering job.
>
> 10 / 3 will never = 3.0.
You should read what they wrote again. They wrote with `≈`, which is a different operator than `=`.
What they wrote is correct.
.
> It is sad you still haven't learned this lesson after many decades.
>
> I hope I'm never on a bridge you build or plane built to the specs you write if you truly think 10 / 3 = 3.00000.
HN doesn't allow this sort of behavior.
10 / 3 != 3.000000000000000000000000 no matter how many times you refute it. You should really learn to accept it and continue on and look deeper inside yourself into this. It's sad you still haven't learned this lesson from elementary education. Maybe they should have suspended you.
In no world does 10 / 3 = 3.0. This is just a falsehood as much as 2 + 2. = 5. I don't care about your large values of 2.