Joel Spolsky
A software engineer, technical blogger, and co-founder of Stack Overflow, known for his 2002 blog series Joel on Software. His writing on the strategy of commoditizing complementary products is widely cited in technology business analysis.
Core Facts
The Law of Leaky Abstractions was proposed by Joel Spolsky in 2002, with the core thesis that all non-trivial abstractions leak to some degree.
The core idea of the Law of Leaky Abstractions is that all non-trivial abstractions are leaky, and underlying details will eventually surface, forcing developers to understand them.
Joel Spolsky is the co-founder of Stack Overflow; in his essay 'Things You Should Never Do' published in 2000, he argued that rewriting code from scratch is the single worst strategic mistake a software company can make.
Timeline (last 90 days)
In his 2002 "Strategy Letter V," Joel Spolsky argued that smart companies work to commoditize their complements in order to increase demand for their own products.
The core idea of the Law of Leaky Abstractions is that all non-trivial abstractions are leaky, and underlying details will eventually surface, forcing developers to understand them.
Joel Spolsky criticized the tear-down-and-rebuild approach in his article "Things You Should Never Do," primarily targeting large and complex systems.
Unified computing abstractions may introduce abstraction leakage problems, where the complexity of the underlying implementation penetrates the abstraction layer and is exposed to users
All Facts (6)
The Law of Leaky Abstractions was proposed by Joel Spolsky in 2002, with the core thesis that all non-trivial abstractions leak to some degree.
80%VerifiedThe core idea of the Law of Leaky Abstractions is that all non-trivial abstractions are leaky, and underlying details will eventually surface, forcing developers to understand them.
65%VerifiedJoel Spolsky is the co-founder of Stack Overflow; in his essay 'Things You Should Never Do' published in 2000, he argued that rewriting code from scratch is the single worst strategic mistake a software company can make.
65%UnverifiedIn his 2002 "Strategy Letter V," Joel Spolsky argued that smart companies work to commoditize their complements in order to increase demand for their own products.
50%UnverifiedJoel Spolsky criticized the tear-down-and-rebuild approach in his article "Things You Should Never Do," primarily targeting large and complex systems.
50%UnverifiedUnified computing abstractions may introduce abstraction leakage problems, where the complexity of the underlying implementation penetrates the abstraction layer and is exposed to users
50%