47478569
submission
BorgeStrand writes:
I'm reviving an open source project and need to read up on a lot of existing code written by others. What are your tricks for quickly getting to grips with code written by others? The project is written in C++ using several APIs which are unknown to me. I know embedded C pretty well, so both the syntax, the APIs and the general functionality are things I wish to explore before I can contribute to the project.
6424507
submission
BorgeStrand writes:
Patenting is an expensive process, even coming up with some sort of proof that your idea is unique (and thereby try to attract financing) may be prohibitive for the lone inventor. So what do you folks out there do when you come up with a good idea but don't have the means to patent it or market it to someone who will pay for the patenting process? And how much sense does it really make for the lone inventor to patent something? Would it make more sense to publish the whole idea, and make it (and my inventive brainpower) up for grabs? If my ideas are indeed valuable, what is the best way to gain anything from them without investing too much financially? What is your experience?
