Hi all,
I've been toying with the idea of getting into the development process lightly, so I'm looking for some suggestions and a little feedback. My day job is not coding (wrangling Cisco routers and switches, mostly), but I have some mostly-quick-and-dirty coding experience in Perl, Java, and C.
So, I expect that a prerequisite is figuring out where all the repository stuff is and making sure that I can check things out and back in again correctly; assuming that, are there some basic tickets that I could start with that are pretty simple and could serve to 1) get some annoying, boring, or trivial stuff out of the way so the more experienced folks don't have it on their list, 2) serve as an aid to me familiarizing myself with the existing code base, and 3) serve as an aid to me shaking off the rust on my very rust-encrusted C skills?
Given that, any hints, tips, suggestions, pointers, or direction that anyone might suggest?
Cheers,
-Chris
I've been toying with the idea of getting into the development process lightly, so I'm looking for some suggestions and a little feedback. My day job is not coding (wrangling Cisco routers and switches, mostly), but I have some mostly-quick-and-dirty coding experience in Perl, Java, and C.
So, I expect that a prerequisite is figuring out where all the repository stuff is and making sure that I can check things out and back in again correctly; assuming that, are there some basic tickets that I could start with that are pretty simple and could serve to 1) get some annoying, boring, or trivial stuff out of the way so the more experienced folks don't have it on their list, 2) serve as an aid to me familiarizing myself with the existing code base, and 3) serve as an aid to me shaking off the rust on my very rust-encrusted C skills?
Given that, any hints, tips, suggestions, pointers, or direction that anyone might suggest?
Cheers,
-Chris
Comment