Joel Spolsky at the Stack Exchange London office, June 2014.
|Born||1965 (age 50–51)
Albuquerque, New Mexico
|Nationality||American, New Zealand, Dual citizenship|
|Alma mater||Yale University|
CEO, Fog Creek Software
CEO, Stack Exchange Network
Avram Joel Spolsky (born 1965) is a software engineer and writer. He is the author of Joel on Software, a blog on software development, and the creator of the project management software Trello. He was a Program Manager on the Microsoft Excel team between 1991 and 1994. He later founded Fog Creek Software in 2000 and launched the Joel on Software blog. In 2008, he launched the Stack Overflow programmer Q&A site in collaboration with Jeff Atwood. Using the Stack Exchange software product which powers Stack Overflow, the Stack Exchange Network now hosts over 100 Q&A sites.
Spolsky grew up in Albuquerque, New Mexico, and lived there until he was 15. He then moved with his family to Jerusalem, Israel, where he attended high school and completed his military service in the Paratroopers Brigade. He was one of the founders of the kibbutz Hanaton in Lower Galilee. In 1987, he returned to the United States to attend college. He studied at the University of Pennsylvania for a year before transferring to Yale University, where he was a member of Pierson College and graduated in 1991 with a BS summa cum laude in Computer Science.
Spolsky started working at Microsoft in 1991 as a Program Manager on the Microsoft Excel team, where he designed Excel Basic and drove Microsoft's Visual Basic for Applications strategy. He moved to New York City in 1995 where he worked for Viacom and Juno Online Services. In 2000, he founded Fog Creek Software and created the Joel on Software blog. Joel on Software was "one of the first blogs set up by a business owner".
He is the author of five books, including User Interface Design for Programmers and Smart and Gets Things Done. He is also the creator of The Joel Test.
Spolsky coined the term fix it twice for a process improvement method. It implies a quick, immediate solution for fixing an incident and a second, slower fix for preventing the same problem from occurring again by targeting the root cause. His use of the term Shlemiel the painter's algorithm, referring to an algorithm that is not scalable due to performing too many redundant actions, was described by salon.com's Scott Rosenberg as an example of good writing "about their insular world in a way that wins the respect of their colleagues and the attention of outsiders."
Schlemiel the Painter's algorithm
In software development, a Shlemiel the painter's algorithm (sometimes, Shlemiel the painter algorithm) is a method that is inefficient because the programmer has overlooked some fundamental issues at the very lowest levels of software design. The term was coined in 2001 by Spolsky. The term is not to be confused with the Painter's algorithm (used in image compositing), as the two are entirely unrelated.
Spolsky used a Yiddish joke to illustrate a certain poor programming practice. In the joke, Schlemiel (also rendered Shlemiel) has a job painting the dotted lines down the middle of a road. Each day, Schlemiel paints less than he painted the day before. When he is asked why, Schlemiel complains that it is because each day he gets farther away from the paint can.
The inefficiency to which Spolsky was drawing an analogy was the poor programming practice of repeated concatenation of C-style null-terminated character arrays (that is, strings) in which the position of the destination string has to be recomputed from the beginning of the string each time because it is not carried over from a previous concatenation.
Spolsky condemned such inefficiencies as typical for programmers who had not been taught basic programming techniques before they began programming using higher level languages: "Generations of graduates are descending on us and creating Schlemiel The Painter algorithms right and left and they don't even realize it, since they fundamentally have no idea that strings are, at a very deep level, difficult."
The programming practice that Spolsky used to make his point was repeated concatenation of null-terminated character arrays ("strings").
The first step in every implementation of the standard C library function for concatenating strings is determining the length of the first string by checking each character in the array, starting from the beginning, to see if it is the terminating null character. Next, the second string is copied to the end of the first, effectively concatenating the two. At the end of the concatenation, the length of the combined string is discarded upon return to the calling code.
In Spolsky's example, the "Schlemiels" occur when multiple strings are concatenated together:
strcat( buffer, "John" );Here, the string "John" is appended to the buffer
strcat( buffer, "Paul" );Now the string "Paul" is appended to that
strcat( buffer, "George" );... and "George" is appended to that
strcat( buffer, "Ringo" );... and "Ringo" is appended to that
After "Paul" has been appended to "John", the length of "JohnPaul" (or, more precisely, the position of the terminating null character) is known within the scope of
strcat() but is discarded upon its return to the point after Paul and before George. Afterwards, when
strcat() is told to append "George" to "JohnPaul",
strcat() starts at the very first character of the array ("J") all over again just to find the terminating null character. Each subsequent call to
strcat() has to compute the length again before concatenating another name to the
Analogous to Schlemiel not carrying the paint-bucket (or the string's length) with him, all the subsequent
strcat()s have to "walk" the length of the string again to determine where the second string should be copied. As more data is added to
buffer with each call to
strcat(), that terminating null character also gets farther away from the beginning, meaning subsequent calls are increasingly slow—just as Schlemiel's path to his bucket keeps getting longer.
The problems illustrated by Spolsky's example are not noticed by a programmer who is using a high-level language and has little or no knowledge of its underlying principles and functions. "Some of the biggest mistakes people make even at the highest architectural levels come from having a weak or broken understanding of a few simple things at the very lowest levels."
- Spolsky, Joel; Atwood, Jeff (July 8, 2008). "Stack Overflow podcast #13". Retrieved August 4, 2013.
- Spolsky, Joel (October 30, 2005). "About Joel Spolsky". Joel on Software. Retrieved August 4, 2013.
- Spolsky, Joel. "Joel Spolsky". joel.spolsky.com. Retrieved August 4, 2013.
- Livingston, Jessica (2007). "Interview: Joel Spolsky Co-Founder, Fog Creek Software". Founders at Work: Stories of Startups' Early Days. Apress. ISBN 9781590597149. Retrieved August 4, 2013.
- "An Interview with Joel Spolsky". SoftLetter.com. Archived from the original on August 9, 2007. Retrieved August 4, 2013.
- Spolsky, Joel. "How Hard Could it Be". Inc. Retrieved August 4, 2013.
- "Joel Spolsky". Internet Movie Database. Retrieved August 4, 2013.
- Atwood, Jeff (April 16, 2008). "Introducing Stackoverflow.com". Coding Horror. Retrieved August 4, 2013.
- "Management Team". Stack Exchange Network. Retrieved August 4, 2013.
- Spolsky, Joel (January 6, 2012). "How Trello is different". Retrieved August 4, 2013.
- Spolsky, Joel (February 19, 2007). "Seven steps to remarkable customer service". Retrieved August 4, 2013.
- Rosenberg, Scott (December 9, 2004), The Shlemiel way of software, salon.com.
- "About Joel Spolsky". Retrieved 27 June 2015.
- "stackoverflow". Retrieved 27 June 2015.
- "Untitled (Joel Spolsky on Twitter)". Retrieved 27 June 2015.
- Spolsky, Joel (December 11, 2001), Back to Basics, Joel on Software, joelonsoftware.com.
- Spolsky, Joel (2001). User Interface Design for Programmers. Apress. ISBN 1-893115-94-1.
- Spolsky, Joel (2004). Joel on Software: And on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and Managers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity. Apress. ISBN 1-59059-389-8.
- Spolsky, Joel (2005). The Best Software Writing I: Selected and Introduced by Joel Spolsky. Apress. ISBN 1-59059-500-9.
- Spolsky, Joel (2007). Smart and Gets Things Done: Joel Spolsky's Concise Guide to Finding the Best Technical Talent. Apress. ISBN 1-59059-838-5.
- Spolsky, Joel (2008). More Joel on Software: Further Thoughts on Diverse and Occasionally Related Matters That Will Prove of Interest to Software Developers, Designers, and to Those Who, Whether by Good Fortune or Ill Luck, Work with Them in Some Capacity. Apress. ISBN 1-4302-0987-9.
|Wikiquote has quotations related to: Joel Spolsky|