Synthesis is harder than analysis

apsurd

Yes, this is documented in Bloom's Taxonomy for learning/education. Creating is the highest level of understanding. Remember – Recall facts, definitions, formulas (memorization). Understand – Explain ideas in your own words. Apply – Use knowledge to solve problems or perform tasks. Analyze – Break information into parts and identify relationships. Evaluate – Judge, critique, or justify decisions. Create – Synthesize ideas to produce something new.

dcrazy

> (Note: I asked AI for the integral of the Gaussian, I hope it got it right!) It seems like malpractice to not even check this.

dreamcompiler

> And it turns out that it’s quite straightforward to calculate a derivative, no matter what type of function it is. 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

ajeet

I loved reading this article. It was reasonably short to not make the reader lose interest. It jumped around in different domains to make a core point at the end about SREs managing complex systems. This gets even more difficult with the rate of change each of those systems has with coding agents. I don't know if I agree with the terms "synthesis" and "analysis" as the equivalent of global and local respectively, but it was a great read.

taneq

> However, when someone says “calculus” without modification […] there’s no ambiguity about which calculus they are referring to Might be differentiation and integration, might be dental plaque. ;)

jdw64

The reason synthesis expertise is not easily recognized as expertise might be because it's hard to evaluate when moving to another system. 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.