From another thread,
Indeed. They are both overly ambitious projects with very vague descriptions what they will do. If you have not coded say 5,000 to 10,000 lines of code in the past, not cut and paste, and mainly in C/C++, you will never complete it. Start with something small. Arduino is not legos, you can't just plug everything together and expect them to "work".
That may sound harsh at first, but of course it is exactly the opposite, attempting to redirect the energy towards a smaller but achievable goal. Spot on. Much better to have a small success than a gigantic failure (accompanied by potentially large hardware costs).
The "overly ambitious project" is a recurring theme that I continually shake my head at. Often It seems difficult to comment in such a way that the poster will not be discouraged, so usually I will just walk away.
With that in mind, I propose that the community develop a list, perhaps entitled, "The Top Ten Ways to Make Absolutely Sure Your Arduino Project Fails". This would be more or less in the spirit of "How to use this forum
". The overall aim is to help the newcomer achieve early success, avoid pitfalls, and build a good foundation for additional and more complex projects.
In his one post, @liudr has given us material for several items on the list, and more importantly, has suggested a possible framework: Point out not only the shortcoming, but the approach to overcome it ("If you have not coded say 5,000 to 10,000 lines of code...").
If this idea generates a good amount of input, I would also like to see a discussion regarding how to triage and prioritize potential items on the list.