5 ms·
> you can also just use a couple hours every day, and some at the weekends, to create something from scratch on your own That's what I've been doing. :) I've p
by sown 11y ago
> you can also just use a couple hours every day, and some at the weekends, to create something from scratch on your own
That's what I've been doing. :) I've pitched a couple of patches but they usually get turned down. I'm wondering if I should take a break or just accept that I won't be a good engineer.
> Recently I've been writing a ruby grape-based api server and I thought I had a handle on it. Then I had the privilege of seeing a similar project for real and I wasn't even close. Theirs was so much better. Maybe I can get to that level but these guys are young, half my age, and they know 4x what I do.
- toxicFork 11y ago> That's what I've been doing. :) I've pitched a couple of patches but they usually get turned down. I'm wondering if I should take a break or just accept that I won't be a good engineer. Don't blame yourself, there may be many reasons for that, I would try to find out why they were turned down, and then look at some patches that weren't turned down. I know it's hard not to feel bad about being rejected, even if it's just a patch to a project, but at least you'll have the benefit of learning from it. > Then I had the privilege of seeing a similar project for real and I wasn't even close Sure, there will always be competition, but is the project made to be sold, or is it made to have more experience apart from fixing bugs? If it's the latter, I don't think there's any way to lose. Study the other project and see what they did better, then try to implement them yourself :) "they are younger and better", that doesn't matter. Just try to get yourself better, there's always someone who's better than someone else! Edit: formatted the response to be a bit more readable