Joel on software quotes fortunes cookies shlomi fishs. He also hosts a very popular blog at joel on software, though his. And its gone the true cost of interruptions jaxenter. Software development trends to look out in 2019 0 chapters updated nov 30, 2018 01. How to explain a layperson why a developer should not be. Interruptions are one of the biggest sources of inefficiency for programmers. People need roughly 23 minutes to go back to their tasks after a major interruption, but the plot deepens if youre a programmer. Interruptions kill my productivity because it can take me 1015.
Do programmers have quiet working conditions free of interruptions. Joel on software but why interruptions cost so much. He graduated from yale university, and has worked as a programmer and manager at. For programmers, there is less evidence of the effects and prevalence of interruptions. Noise, phone calls, going out for lunch, having to drive 5 minutes to starbucks for coffee, and interruptions by coworkers especially interruptions by coworkers all knock you out of the zone.
Add at least 10 minutes to the forced break the minimum amount of time you need to start editing code again and there you go thats a solid half hour you lose whenever someone approaches you. Ive read joel s and other comments on how a workplace can be rated on how much the programmer is interrupted. According to joel spolsky, founder of fog creek software and author of the joel on software blog, there should be less fluff and more stuff i guess i. Workers have to work in a fragmented state as 57% of tasks are interrupted mark. To understand what i mean, lets take someone whose job is in sales. Joel on software excerpt from ui design for programmers. Now, to be fair, theyre probably a big source of inefficiency for everyone, but relatively speaking, theyre worse for programmers. Joel spolsky is the founder of fog creek software, a small software company in new york city. Just shut up and let your devs concentrate, advises joel spolsky. Quotations from or relating to the site joel on software by joel spolsky see.
Since this site is for programmers, im going to warm up your brains a little bit with a programming problem. Ceo, stack exchange network cofounder, stack overflow, fog creek software and trello. Developer flow state and its impact on productivity stack overflow. Our ceo joel spolsky said it best put yourself in the job candidates shoes. Im joel spolsky, a software developer in new york city. Noise, phone calls, going out for lunch, having to drive 5 minutes to starbucks for coffee, and interruptions by coworkers especially interruptions by. Of course hed like the guy whos obsessed with shipping products and not with quality code after all, hes the beneficiary of shipping products, and he doesnt have to be the one tearing his. Search careerbuilder for software programmer jobs and browse our platform. Joel spolsky on stack overflow, inclusion, and how he broke it.
They found that the minimum accommodation for each developer. Writers, programmers, scientists, and even basketball players will tell. Human task switches considered harmful joel on software. Joel spolsky is a software engineer, writer and entrepreneur. Joel has some odd ideas when it comes to software i think it has to do with the fact that he manages a software company and isnt an engineer himself. In this talk full of humor, joel spolsky captivates and entertains the audience by talking about how how he built and grew stack overflow, and more broadly on the software industry today. I was having a mildly frustrating time when i took a break to read jos and posted the first time.
If a coworker asks you a question, causing a 1 minute interruption, but this knocks you out of the zone badly enough that it takes you half an hour to get productive again, your overall productivity is in serious trouble. Developing software is like driving a car in a very busy road for. How to destroy programmer productivity george stocker. Joel spolsky talks about this in one of his blog posts. Thats just a fivedollar word for giving people things to do. Programmers, teach nongeeks the true cost of interruptions. A weblog by joel spolsky, a programmer working in new york city, about software and software companies. This book covers every imaginable aspect of softward programming, from the best way to write a code to the best way. Typically, the number that gets tossed around for getting back into the zone is at least 15 minutes after an interruption.
Hes also the name behind the joel on software blog, which consistently ranks top or top ten on software mustread lists. Joel spolsky once said, productivity depends on being able to juggle a lot of little details in short term memory all at once. Avram joel spolsky born 1965 is a software engineer and writer. This is why you shouldnt interrupt a programmer the. I dont think that the state of reverie that joel describes is technical. The ceo of stack overflow, joel spolsky, laid out some of the reasons programmers prefer their.
1439 553 695 605 1252 122 1468 193 1062 591 1393 107 238 816 890 1082 257 89 1485 761 355 1463 38 316 896 235 1206 929 725 1065 579 962 1018 564 956 735