element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum troubleshooting topics zooms past 1000 (now 6000)
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 35 replies
  • Subscribers 708 subscribers
  • Views 4658 views
  • Users 0 members are here
Related

troubleshooting topics zooms past 1000 (now 6000)

e14 Contributor
e14 Contributor over 14 years ago

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=10869

 

In my experience, when you have around 10 known issues, you can

discuss the status of each of them in a 1 hour weekly meeting.  You can

easily notice when two are duplicates of each other, and combine them.

You can keep track of which ones have been reproduced, and which

need further information in order to reproduce.  You can keep track of

who is assigned to work each issue, and in what order they should work

them.  You can remember from week to week what the issues are about,

without having to spend all your time coming up to speed again on each

issue.  You can ask whether each issue presents an opportunity to

improve the documentation, or to improve the QA process.  You can

ask to review in detail the proposed fix for each problem, until you are

satisfied that the fix actually solves the problem without creating other problems.

You can ask whether each problem was caused by a fault in the tools used,

or the process used, and if so, whether to make improvements in those.

You can notice when multiple problems relate to the same component,

and perhaps decide to redesign that component rather than continually

patch it.  You can thoughtfully decide whether to deliver a fix as an urgent

update, or wait to deliver it in the next general release.  You can develop

regression tests to prevent the same or similar problems from ever being

shipped again.  And when a problem is fixed and the fix delivered, you

can move it off your agenda.

 

When you have about 100 known issues, it becomes much more

difficult to do the same tasks.  You can try to prioritize and focus on

just the top 10, but then the others suffer.  When you have about 1000

known issues, it becomes impossible to manage, and you will completely

lose track of which issues are duplicates of others, which are fixed, and

which are urgent.  If you release a product update, you will have no idea

what to say in the release notes.

  • Sign in to reply
  • Cancel
Parents
  • e14 Contributor
    e14 Contributor over 13 years ago

    jamodio: "...Based on the volumes we are talking, even before they realized that demand was much much higher than anticipated, the $25 target, and the credit card size, are just BS. What's the difference between a $25 product that has design and reliability issues to a $28 that works properly?..."

     

    "...The $25/$35 is really a joke, when you factor in that you need to buy a keyboard, a mouse if you want to work in graphics mode, a power supply or several of them you need to try to make sure they work and don't blow up your TV, a collection of SD cards to figure which one works with your Pi, a powered USB hub (of which some were reported not to work properly) if you want to have some extra stuff or even power hungry USB devices connected to the Pi, the HDMI cable, and if you don't have one, a monitor. Plus if you want to provide some protection to the board, a case.     What one really can criticise now...."

     

    I really couldn't agree more with these sentiments (and the rest of your post). image

     

    It's all a bit late now but while "cheap and flaky" might be ok for experienced hackers who are looking for a project (or for those inexplicable ebay types who seem happy to take a punt on far Eastern junk that everbody else knows is a ripoff), but most consumers would want "reasonably priced and functions properly" and the UK educational system (which can be likened to an industrial grade customer imo) wouldn't settle for less than "rock solid at a reasonable premium and with Walk On Water support".

     

    The hardware cost of a classroom's worth of of Pi boards is pretty insignificant compared to the cost of training all those teachers in some pretty deep topics. Then there's the cost of peripherals and accessories for e.g. GPIO interfacing, study materials, SD card duplication, all those thousands of meetings...

     

    It made no sense to cheap out on the board to the current extent, but now that it appears to be pretty much finished then it makes even less sense to cheap out on getting it working bess poss. One guy with a USB sniffer devising workarounds in his spare time? Remember that the Foundation were initially hoping to shift 10,000 units eventually to finance the educational push. It now looks like that sales target will be exceeded by two orders of magnitude.That should pay for some development time. Or a new kitchen.*

     

    I'm sure this soap opera will run and run.

     

    *in-joke.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • morgaine
    morgaine over 13 years ago in reply to e14 Contributor

    It may have made some kind of marketting sense to sacrifice good design in order to get the first Model B under $35 in 10-30k volume quantities, but those original design choices no longer make any sense when half a million boards have been shipped.

     

    The BOM cost is now far below what it was originally for the Foundation, and as a result a huge range of improvements could be made to a new model of the board while still remaining below $35.  The fact that no such wholesale redesign is being undertaken by the Foundation (as far as we know) suggests many things, all bad.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • johnbeetem
    johnbeetem over 13 years ago in reply to morgaine

    Morgaine Dinova wrote:

     

    It may have made some kind of marketting sense to sacrifice good design in order to get the first Model B under $35 in 10-30k volume quantities, but those original design choices no longer make any sense when half a million boards have been shipped.

     

    The BOM cost is now far below what it was originally for the Foundation, and as a result a huge range of improvements could be made to a new model of the board while still remaining below $35.  The fact that no such wholesale redesign is being undertaken by the Foundation (as far as we know) suggests many things, all bad.

    I don't think they're doing wholesale re-design, since the basic combination of BCM2835 and LAN9512 still fits the goal of the Foundation: lowest-cost educational platform.  I do believe they're doing minor redesign to fix problems identified here at element14 and at the RasPi Forum, but the practice of the Foundation is to redesign in secret and the only way to find out things have improved is for alert RasPi buyers to wonder why their new RasPis doesn't look the same as the published PCB photos.  I think this is a Bad Approach, since if RasPi were to publish schematics and layouts before committing to a new rev, we'd have a chance to say things like: "Wait a tick, if you directly connect USB port A +5V to the 5V0 plane instead of using a 0 Ohm jumpers then you have no way to fix voltage dip and other problems."

     

    I fully expect to see a future RasPi Model B rev 3.x with switching regulators, but no announcement until after it's shipped.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • morgaine
    morgaine over 13 years ago in reply to johnbeetem

    John Beetem wrote:

     

    if RasPi were to publish schematics and layouts before committing to a new rev, we'd have a chance to say things like: "Wait a tick, if you directly connect USB port A +5V to the 5V0 plane instead of using a 0 Ohm jumpers then you have no way to fix voltage dip and other problems."

     

    I fully expect to see a future RasPi Model B rev 3.x with switching regulators, but no announcement until after it's shipped.

     

    Well they are inept organizationally, we know that.  But what's worse than their organizational ineptness is that their secretive approach results in a far worse product than if they did their work openly, as has already been demonstrated through the community identifying faults and other issues that could easily have been caught at design time.

     

    They really don't get it that hundreds or thousands of engineering eyes are better than the few that they have in-house.  I'm not sure if it's because of unwarranted confidence in their own abilities, or simply a matter of ego, but it's present and it's very strong.

     

    Everyone in the Pi ecosystem is suffering because of the Foundation's myopia, including Element 14 and RS who would benefit greatly from a product without faults.  But the most ridiculous part of the situation is that even RPF themselves would benefit, but are too short-sighted to realize.

     

    Morgaine.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • morgaine
    morgaine over 13 years ago in reply to johnbeetem

    John Beetem wrote:

     

    if RasPi were to publish schematics and layouts before committing to a new rev, we'd have a chance to say things like: "Wait a tick, if you directly connect USB port A +5V to the 5V0 plane instead of using a 0 Ohm jumpers then you have no way to fix voltage dip and other problems."

     

    I fully expect to see a future RasPi Model B rev 3.x with switching regulators, but no announcement until after it's shipped.

     

    Well they are inept organizationally, we know that.  But what's worse than their organizational ineptness is that their secretive approach results in a far worse product than if they did their work openly, as has already been demonstrated through the community identifying faults and other issues that could easily have been caught at design time.

     

    They really don't get it that hundreds or thousands of engineering eyes are better than the few that they have in-house.  I'm not sure if it's because of unwarranted confidence in their own abilities, or simply a matter of ego, but it's present and it's very strong.

     

    Everyone in the Pi ecosystem is suffering because of the Foundation's myopia, including Element 14 and RS who would benefit greatly from a product without faults.  But the most ridiculous part of the situation is that even RPF themselves would benefit, but are too short-sighted to realize.

     

    Morgaine.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube