Quote:
Originally Posted by ApK
Thank you for the generous offer.
I will check it out.
I have two comments at a first glance.
1. You may be an excellent engineer and have lots of great info to impart, but you really need to consider getting some professional editorial assistance. Perhaps consider collaborating on a revision with someone more expert in written English communication. Awkward sentence construction and poor copy editing, as is apparent from just the introductory materials, can make even the best technical advice too painful to slog through.
2. I think the lesson that should be taken from Kernighan's quote is NOT "Write clever code and rely on advanced machine tools to debug it." It should be "Don't write clever code." That is, whenever possible, make your code clear and easy to maintain.
Not always possible of course, especially in complex systems. Just sayin'....
|
Thanks for your comments, will consider it when I can generate some revenue. As per Kerninghan's quote is considered, without debugging tools, it is very difficult to find issues especially in embedded systems.