Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Bug Programming Security

October, November the Worst Months For Writing Buggy Code 136

chicksdaddy writes "Data from application testing firm Veracode suggests that the quality of application code submitted for auditing is pretty much constant throughout the year — except for the months of October and November, when the average density of vulnerabilities in the code jumps considerably. But why? Is it the pressure of deadlines? The stress of developers' lives (kids back to school, etc.)?"
This discussion has been archived. No new comments can be posted.

October, November the Worst Months For Writing Buggy Code

Comments Filter:
  • Budgets, schedules (Score:5, Informative)

    by br00tus ( 528477 ) on Tuesday December 20, 2011 @05:49PM (#38440614)
    Most businesses I've seen, a list of things to do is drawn up in the beginning of the year and set as a goal. Achieving those goals goes into consideration for how one did in a year, bonus, next year's budget etc. The list is usually unrealistic due to pressure from above (or other executives whose title may be the same level as the CTO/CIO, but who are for all intents and purposes, at a higher level due to being so-called "profit centers"). The code base being built on is usually old and broken, the equipment it runs on not the best, the team so-so with a few bright people, and a lot of dumb managers. Things not counted in the schedule are long-time experienced employees getting fed up and leaving, equipment breakdowns, bugs and emergencies that have to be dealt with, or business units who change what they want all year long from the original specification. Plus other things - a third party product is bought, and is very difficult to integrate in the existing system, with more time than initially planned for. By October not many things on the year-end checklist are done and the CTO starts having meetings and banging on the table that he needs checks on the lists to show the CEO what his team has done this year. So people stop writing good, long-term code and start writing crap, so they can check off the list for the end of the year. Things slow down by the end of December, that a few things on the list won't get done becomes accepted, people go on Christmas vacation. That's why bugs go in in October/November.
  • by Anonymous Coward on Tuesday December 20, 2011 @06:14PM (#38440984)

    I work for a large utility company. We see a significant increase in injuries and accidents during these months as well. I don't have the numbers and graphs with me, but it's been notably consistent over the past 8 years.

  • bad heading (Score:5, Informative)

    by roc97007 ( 608802 ) on Tuesday December 20, 2011 @08:46PM (#38442858) Journal

    Should read "October, November are the *best* days for writing buggy code." They're the worst days, apparently, for writing bug-free code.

COMPASS [for the CDC-6000 series] is the sort of assembler one expects from a corporation whose president codes in octal. -- J.N. Gray