IDK if that's the reason I'd given for calculus. I might not literally solve integrals, but the base knowledge of what an integral is, what a derivative is, yes

IDK if that's the reason I'd given for calculus. I might not literally solve integrals, but the base knowledge of what an integral is, what a derivative is, yes, I absolutely use those. I'm also a SWE/SRE, so … there's that. But how often I see graphs from products whose entire job is metrics that are just labelled wrong, e.g., w/ the base unit instead of the rate, or what actually use the base unit instead of the rate, making for a difficult UX¹. If the devs of those products understood … calculus (let alone stats!) maybe the products would be less garbage? As it is, I still need to know that as a user. But yeah, I've not taking a literal integral in a while. Usually I'm doing some sort of very crude integration. Similar w/ the CS degree and everybody in this field going "it isn't needed" and then going "why isn't the database answering this query quickly, when there is an index on those fields?²" and follow that with a discussion of how B-trees work (or rather, don't)… And should I ever need to solve an integral, I will recognize that problem when I see it, and know what Wikipedia articles I need to page back into my brain. ¹what I mean here is, e.g., like what Azure Metrics does. E.g., there's a graph I use that measures throughput, but the unit is just "Bytes". But each point is "number of bytes transmitted during the window of time represented by that point" so it's really "bytes / 5 minutes" or something. But of course, then, you zoom, and now it is "bytes / 10 mintues" … but the axis doesn't tell you that. This has the effect that as you zoom in or out … the numbers change! Which makes no sense (obviously the effect of zooming a graph does not go back in time and alter the readings) … but only if you were properly measuring bytes/sec. (But as it is, there's a constant / divisor caught up in there.) (And that ignores harder problems with zooming metrics, like aliasing or resolution, or other metrics problems like percentiles on aggregates or efficient computation of calculated values and where to put windows, etc. … but pfft I'm in the stone age over here.) ²and it's almost always a 2D range query or a range + exact value and the exact value is the second column in the index…