4 ms·

I just read this article & even skimmed the study, but I can't figure out what the relation of stress to code quality is. Poor quality is high stress? Or hi

I just read this article & even skimmed the study, but I can't figure out what the relation of stress to code quality is. Poor quality is high stress? Or high stress means that you are meticulous and are likely to produce higher quality code?

vibrato 10y ago
I understood the conclusion to be that perceived difficulty (stress) while writing code is linked to poor quality. "code elements that are perceived more difficult by developers also end up having more quality concerns found in peer code reviews"
- p4wnc6 10y ago
  It would be interesting to see this linked to interviews too where the entire situation, mannerisms of the interviewer, and presentation of a given exercise are all specifically tailored to make sure it is perceived as difficult.
jonobird1 10y ago
I am obviously making an educated guess based on experience here, however I believe that answer to why the stress is high is what causes reduced code quality rather than the stress itself. For example, if you're under the pump and have unrealistic deadlines, you are more likely going to write less quality code. Not because you're trying to cut corners, but because when you have the time, you go over your code an improve it about five times before submitting it and have a freer mind to do that. What are your thoughts?
- Falkon1313 10y ago
  IMO, experience indicates that the best code quality comes well away from deadlines. Code written just before a tight deadline or during the recovery period afterward could always use extra scrutiny. Is it really a surprise that the distractions, disruptions, and fatigue of stress affect a task that requires significant focus, concentration, and creativity? Or that not having much time to review and revise your work will result in lower quality than if you did have the chance to improve it? Kind of strikes me as a "Breaking news - water is wet!" announcement.
  - jonobird1 10y ago
    I agree with that. Seems like fairly common sense. Process for a developer is to be immersed into their code and to constantly improve it so when there's no time to do that and high pressure, then it's obviously going to be lower end result quality. Water is wet.

vibrato 10y ago

I understood the conclusion to be that perceived difficulty (stress) while writing code is linked to poor quality. "code elements that are perceived more difficult by developers also end up having more quality concerns found in peer code reviews"

p4wnc6 10y ago
It would be interesting to see this linked to interviews too where the entire situation, mannerisms of the interviewer, and presentation of a given exercise are all specifically tailored to make sure it is perceived as difficult.

jonobird1 10y ago

I am obviously making an educated guess based on experience here, however I believe that answer to why the stress is high is what causes reduced code quality rather than the stress itself. For example, if you're under the pump and have unrealistic deadlines, you are more likely going to write less quality code. Not because you're trying to cut corners, but because when you have the time, you go over your code an improve it about five times before submitting it and have a freer mind to do that. What are your thoughts?

Falkon1313 10y ago
IMO, experience indicates that the best code quality comes well away from deadlines. Code written just before a tight deadline or during the recovery period afterward could always use extra scrutiny. Is it really a surprise that the distractions, disruptions, and fatigue of stress affect a task that requires significant focus, concentration, and creativity? Or that not having much time to review and revise your work will result in lower quality than if you did have the chance to improve it? Kind of strikes me as a "Breaking news - water is wet!" announcement.
- jonobird1 10y ago
  I agree with that. Seems like fairly common sense. Process for a developer is to be immersed into their code and to constantly improve it so when there's no time to do that and high pressure, then it's obviously going to be lower end result quality. Water is wet.