Project14 | You Decide the Next Monthly Project Competition!

Thank you for your feedback

DAB is spot on! I started off in real time systems (what it was called before embedded) working on brake dynomometer control, then got into writing video games for Atari and Commodore. From my time writing games, I discovered nothing exercises the capabilities of a computer as much as a game, and nothing requires more general knowledge of a system's operation that writing games. To this day, whether I am writing code for a controller, a diagnostic monitor, a simulator, what I see is a video game. The difference is just the consequence when something goes wrong.

balearicdynamics hit on my thinking for what to use for platforms. There are several platforms out there, depending on the application Raspberry Pi, Arduino, and Beagle are a few more. The projects that are available for these platforms focus on the how. I think where I am aiming with this is working on the why question. Why should I use one platform over another? Why do I need a database? Why did I want to solve this?

Jack

I have started a discussion at If I Had a Hammer covering the same topic.

Jack, IMHO the question of Why is strictly depending on the project. Here in most of the cases the approach is: I have this platform and want to do this. I try to give suggestions as I can but I am aware that a better approach is just I want to reach this goal, what platform should I use? Better Better

Enrico

The "whys" of an investigation can be endless. The weighing of cost and benefit sometimes seems to have no solution. The other factors for determining why is dealing with opinion over fact and what sometimes rise to the level of religious wars.  Used to be fights over Intel v AMD, or worse x86 v 68000. Zealots were everywhere.

As you point out, often the platform is "the one that is available" which is why, when I write code, I always try to maintain platform independence whenever possible.

A couple of wise thoughts I have picked up:

1. Arguing with an engineer is like wrestling with a pig in the mud. You both get covered from head to toe, and the pig loves it.
2. If there is a room full of N engineers you will always get at least N+1 "best" solutions

The "whys" of an investigation can be endless. The weighing of cost and benefit sometimes seems to have no solution. The other factors for determining why is dealing with opinion over fact and what sometimes rise to the level of religious wars.  Used to be fights over Intel v AMD, or worse x86 v 68000. Zealots were everywhere.

As you point out, often the platform is "the one that is available" which is why, when I write code, I always try to maintain platform independence whenever possible.

A couple of wise thoughts I have picked up:

1. Arguing with an engineer is like wrestling with a pig in the mud. You both get covered from head to toe, and the pig loves it.
2. If there is a room full of N engineers you will always get at least N+1 "best" solutions