??? 07/21/09 13:48 Read: times |
#167655 - Not exactly Responding to: ???'s previous message |
You see, there's a reason I've not coded much 'C' since then. First of all, it hasn't been my job. I design the system, manage the project flow, ensure adherence to design criteria, and, above all, ensure that test requirements are met, so we can get paid, but I do make sure the coding is done to acceptable standards and in keeping with the predetermined spec's and documentation. After all, I have to take responsibility for what's delivered. Coding is just one of several major tasks, and I leave it to those who are expert at it. I do sometimes code portions of the task, but generally design but don't always implement the firmware.
As for my experience with Turbo-C, and Turbo-Pascal for any sort of signigican project, yes, that's 20-25 years out of date. If I hadn't decided to focus on the hardware, and if I hadn't decided it was easier to get someone more focused on the firmware to join the team, it might have been different. I still use Turbo-C to drive test fixtures from a PC, of course, but that's normally pretty simple stuff. RE |