commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject Re: how to refine programming skill
Date Mon, 20 Jul 2015 04:41:34 GMT
As one idea, I would (if I didn't have too many demands on my time):

1) Browse through the APIs/Code for a piece of code that intrigues you.
2) Read it, write a blog on it, tweet about your blog (or whatever other
social networks you're into).
3) Learn about Caliper (https://github.com/google/caliper)
4) Write a Benchmark for that piece of code. Blog about doing that,
explaining how you did it.
5) Consider whether you can optimize the code and use Caliper to make your
case.
6) Goto #1.

Hen


On Fri, Jul 10, 2015 at 10:56 AM, Phil Steitz <phil.steitz@gmail.com> wrote:

> On 7/10/15 4:35 AM, Daniel C. S. Yeh wrote:
> > Dear all,
> >
> > I am newer here. I want to involve in open source project development.
> >
> > By this way, I can see the good software architecture and bugs fixing
> > practice.
> >
> > could anyone kind tell me how to do it step by step, slowly?
>
> Siegfried did a great job describing how to get involved.   One
> thing that he mentioned that worked for me when I first started is
> working on unit tests and documentation.  The great thing about OSS
> is that most projects have a lot of unit tests and you can use them
> to understand how the code works and how small changes affect it.
> For Commons components, sometimes our javadoc is not as clear as it
> could be.  Unit tests can confirm exact behavior and javadoc can be
> improved.  I remember when I first started working on [lang], that's
> how I started - asking on the mailing list what exactly was meant by
> some vague javadoc, then confirming with unit tests and also
> improving the javadoc.  I got to learn and the tests and javadoc
> were improved.  Adding unit tests to open bug reports is also a
> great service and a good way to get into the code.
>
> Don't be bashful to ask questions about how the code works or how to
> get set up.  Sometimes it may take a while to get a response because
> we have a lot of components and some don't have many active
> contributors; but we welcome questions about the code and documentation.
>
> Welcome to Commons!
>
> Phil
>
>
> >
> > Many thanks
> > Daniel
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message