In this time and age it's so much more important to define what your project/protocol is NOT than what it IS. And then follow these limitations strictly. Knowing the boundaries is extremely useful as then you can carefully plan and build within them not inflating the purpose.

Reply to this note

Please Login to reply.

Discussion

No replies yet.