Dealing with a fundamental design flaw when you're new to the project

Posted by Matt Phillips on Programmers See other posts from Programmers or by Matt Phillips
Published on 2011-01-06T00:09:12Z Indexed on 2011/01/06 1:00 UTC
Read the original article Hit count: 691

Filed under:
|
|

I've just started working on an open source project with around 30 developers in it. I'm working on fixing some of the bugs as a way to get into the "loop" and become a regular committer to the project. The problem is I think I've uncovered a fundamental design flaw that's causing one of the bugs I'm working on. But I feel like if I blast this on the mailing list I'm going to come off as arrogant, and some of the discussions I've had about the issue are butting heads with some of the people. How should I go about this?

© Programmers or respective owner

Related posts about new-job

  • Exciting New Job Announcement!

    as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
    I’m extremely excited to announce that I’ve accepted a position with Applied Information Sciences (AIS).  The innovative work and company values at AIS are aligned with what I was seeking in my next position.  Also, over the past year or so, I’ve met some really talented individuals who work at AIS… >>> More

  • My New Job

    as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
    Last year I started a new job with a logistics company in the North of England, where I was responsible for the management, design and development of IT Integration strategies, architectures and solutions using BizTalk Server 2009.  This included the design and implementation of the BizTalk Server 2009… >>> More

  • Advice on starting a new job

    as seen on Programmers - Search for 'Programmers'
    In a week I will start a new job at a manufacturing company managing the development of a new eCommerce site. The company scores about a 3 on the "Joel" test. I will inherit 3 programmers who developed the company web site and do general IT programming. I have the grey hair and credentials to have… >>> More

  • What should you leave behind for your successors?

    as seen on Programmers - Search for 'Programmers'
    Assume that you're a sole developer leaving a job. What kind of information/material, outside of the code itself, should you create and leave behind for your replacement? An obvious answer is "whatever you would want at a new job" for sure, but it's been a while since I started a new job, and I forget… >>> More

  • What should you leave behind for your successors?

    as seen on Programmers - Search for 'Programmers'
    Assume that you're a sole developer leaving a job. What kind of information/material, outside of the code itself, should you create and leave behind for your replacement? An obvious answer is "whatever you would want at a new job" for sure, but it's been a while since I started a new job, and I forget… >>> More

Related posts about collaboration