After frustrating runs at trying to reduce, reuse, and recycle old C #code, I plan to write a book detailing real strategies to exploit open source code that is what it is: poorly written, poorly documented, and poorly tested.
While it may seem like free software ( free as in free beer in the Stallman sense) may be a starting point, but the reality lots of partly done solutions involve almost as much time to understand, hard to port, and requires modification to change to meet your expectations.
Eric Stallman's belief that you should be able to modify code just like you modify cars and trucks may seem ideal, and it is: idyllic. Most software coders are lazy or rushed: or both. That isn't a put down, it's a reality. So you need to accept some learning and investigation to take on new code.
I plan to write a book about sensible strategies that don't lock you into wasting many hours trying to make a square peg software base fit into a round design.
What are the three strategies (that work)? Read my book.
While it may seem like free software ( free as in free beer in the Stallman sense) may be a starting point, but the reality lots of partly done solutions involve almost as much time to understand, hard to port, and requires modification to change to meet your expectations.
Eric Stallman's belief that you should be able to modify code just like you modify cars and trucks may seem ideal, and it is: idyllic. Most software coders are lazy or rushed: or both. That isn't a put down, it's a reality. So you need to accept some learning and investigation to take on new code.
I plan to write a book about sensible strategies that don't lock you into wasting many hours trying to make a square peg software base fit into a round design.
What are the three strategies (that work)? Read my book.
