I'm a solo developer that works as a consultant to clients. While I've gotten my head around things like GIT there's a big part of it that I still don't understand as I don't get to practice it in a 'collaborative' setting often. For instance, while I can clean up an accidental push to a repo I fully own and control myself, it's harder to do that if you've pushed something to another repo with lots of other devs involved, and it's been accepted etc.
Which is one reason why I like tinkering and contributing to GitHub projects in my spare time, so I can connect with other devs and get a bit more experience that way. It also combats that "loneliness" feeling you get as a solo dev.
I started just by looking at projects with similar topics and interests of mine, eg Wordpress development (where I came across github.com/pojome/elementor and ended up becoming a contributor of code, after writing a feature I had on my wish list) - for me it's essential to contribute to these kinds of projects as you learn so much from them and get to give something back to the projects that help you make money.
Yeah that's true. I started looking at projects that needed small things done like documentation, cleanup of typos in code, etc. and then eventually contributed more serious stuff when the time was right.
And I don't take pull requests too personally, if I submit something and it's rejected I usually try to find out why and then learn from it. If it gets accepted I thank the project manager and high five my cat :)
Really nice !!!! I guess I will try and start like you did :). I guess sometimes the fear of rejection makes it harder to just go for it, and it ain't a win if the cat doesn't get a "hi five" lol
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm a solo developer that works as a consultant to clients. While I've gotten my head around things like GIT there's a big part of it that I still don't understand as I don't get to practice it in a 'collaborative' setting often. For instance, while I can clean up an accidental push to a repo I fully own and control myself, it's harder to do that if you've pushed something to another repo with lots of other devs involved, and it's been accepted etc.
Which is one reason why I like tinkering and contributing to GitHub projects in my spare time, so I can connect with other devs and get a bit more experience that way. It also combats that "loneliness" feeling you get as a solo dev.
Love the open source suggestion. I need to figure out how to get into that world.
I started just by looking at projects with similar topics and interests of mine, eg Wordpress development (where I came across github.com/pojome/elementor and ended up becoming a contributor of code, after writing a feature I had on my wish list) - for me it's essential to contribute to these kinds of projects as you learn so much from them and get to give something back to the projects that help you make money.
Good luck!
Your absolutely right. Although at times the projects you might want to contribute too can be so intimidating :/
Yeah that's true. I started looking at projects that needed small things done like documentation, cleanup of typos in code, etc. and then eventually contributed more serious stuff when the time was right.
And I don't take pull requests too personally, if I submit something and it's rejected I usually try to find out why and then learn from it. If it gets accepted I thank the project manager and high five my cat :)
Really nice !!!! I guess I will try and start like you did :). I guess sometimes the fear of rejection makes it harder to just go for it, and it ain't a win if the cat doesn't get a "hi five" lol