One time-honoured way is to find an open-source tool that you use a lot and
that's missing a feature you'd like. Before working on the feature, find a
bug on the bug list and take a stab at it: mail the dev mailing list or
community and ask where to start ('I'm going to take a look at bug XXX, any
ideas where in the code I should start looking?' is more likely to get a
response than 'Can you tell me how the code works?'). Then once you've
committed the bug fix, look at implementing your feature.I've always found learning hackery to be much more effective when done as part of implementing (or fixing) something specific. Good luck! W On 25 February 2013 10:37, [email protected] <[email protected]> wrote: > Where do I start? > > I know some C, python, php > > Currently my strategy is to delve deeper into C to attempt to understand > raw sockets better > > Looking to develop p2p software of all kinds. > > Looking for excellent resources/books on p2p > > Thanks, sorry if this is intrusive/unwanted > > _______________________________________________ > p2p-hackers mailing list > [email protected] > http://lists.zooko.com/mailman/listinfo/p2p-hackers > >
_______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
