[sdiy] Audio hardware platforms?

[Thomas Strathmann]

On 13.10.13 09:52, Tom Farrand wrote:
> 3) Buy off-the-shelf hardware that is capable of hosting the software
> functions required.  Don't design new hardware for the whole damned
> thing.  Buy the complex pieces off-the-shelf and custom design only
> the bits of glue or peripherals minimally necessary to carry out those
> functions not natively provided on the off-the-shelf boards.  Keep the
> design of custom bits straightforward and as simple as possible.  Now,
> write the code to match the comments documented previously.

This! I've seen projects fail because the majority of the development
team did not heed this advice. But it is true for both software and
hardware. When it comes to sofware I would probably not start by
designing at the level of individual procedurers or even concrete data
structures but use something like a flow-chart or other types of
diagrams. Maybe do a sort of prototype in a high-level (visual)
language. But I guess the most important thing is to sit down with the
intent of not writing code but solving a problem by breaking it down
into manageable chunks and only later executing the plan that you came
up with during this planning stage. Not doing this is another reason why
development projects fail (especially if there is more than one person
involved).

	Thomas