FR version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 486 words in the discussion.
Trending Topics
#point#analysis#synthesis#derivative#differentiation#functions#differentiable#expertise#author#integration

Discussion (10 Comments)Read Original on HackerNews
I get the author's point but this is not completely true; there exist functions that are not differentiable at certain places (e.g. ideal square waves) and others that are not differentiable anywhere (e.g. Weierstrass functions).
https://en.wikipedia.org/wiki/Weierstrass_function
In general, to even ask what it means to compute a derivative we need to specify some input language which describes functions in finite terms; we are necessarily in the world of constructions rather than (say) arbitrary set-theoretical maps between infinite sets. With this in mind, the claim that differentiation is always a straightforward computation is a strong one.
It seems like malpractice to not even check this.
Who would be looking up the integral of one of the most common functions in applied math in a random philosophical article aimed mostly at SREs?
Analysis expertise is about knowing the limitations of specific languages, libraries, and frameworks, and this is easy to recognize and evaluate. But synthesis expertise, by its nature, is about 'combining systems within a specific company.' When you change jobs, it's hard to apply that combination to a completely different system.
For example, even if you know why a company's API design and structure were shaped the way they are, that doesn't necessarily mean you can use that knowledge directly at your next company. Maybe that's why.
Might be differentiation and integration, might be dental plaque. ;)