On Aug 21, 2018, at 8:06 AM, Andy Reichert <andy_r@...> wrote:
I'd be very doubtful about trying to adapt a large complex set of software, with lots of semi-autonomous actions, designed to operate one complex system definition, to a quite differently purposed and defined complex system. I'd anticipate a lot of unexpected surprises and unintended consequences.
And yet, that’s what we do around here. Continually. Not particularly efficiently, sometimes having to backtrack, but often successfully.
My career experience has favored understanding and defining the user/market requirements fully first, then designing a suitable functional architecture and matching implementation second. (hardware and software).
But this is a hobby, not a career. And the costs of experimentation are much smaller.
So I encourage people to just write a little bit of code and try it, for this timetable project or anything else. Start with implementing your own initial ideas, or following something somebody else has suggested, or even implement an approach from elsewhere. If you can build on it to something bigger, that’s great. If you find an problem that nobody had thought of and have to backtrack, well, that’s still valuable knowledge, and it’s still progress.
Bob
--
Bob Jacobsen
rgj1927@...
Bob Jacobsen