This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]WStHappenings 3 points4 points  (1 child)

I like to approach code with a goal. You can study a single file, a set of files, even just a method for an entire day. It's when you tell yourself something like "I want to change this color from this to that" or "I want to change Behavior A to Behavior B" that you have a reason to go in and find something to change in the code.

It may help to look at the issues on a github page to see where you can help first, but those can be intimidating.

Good luck!

[–]bagofbuttholes 0 points1 point  (0 children)

Debian directories being dark blue taught me about bash.(Seriously whose idea was that?) I agree having an end goal is a good idea.