https://github.com/bbatsov/rubocop FTW. Integrate it into your test suite and you can see your mistakes before you push up a change for your team to see.
We've tried putting style violations in the build and found there are enough edge cases that it isn't exactly the interaction we've wanted. Sometimes, we want the human to say "no, my pair and I broke the guideline on purpose and we're okay with it in this case." We don't want a broken build in those cases.
Totally agree with you about getting feedback earlier than opening a PR, though. Linters integrated into text editors are a great way to go.
Well, it's a comparison of different ruby versions, using Rails. That's pretty useful to people who use Rails, which is a lot of people.
Of course, it's not a real Rails app presumably, but just a sample/dummy one. So you may or may not see comparable speed-up with a real app. But it's probably suggestive of the upper limit of improvement you can get by switching ruby versions.
"Will I get a performance improvement from my Rails app by upgrading ruby" is a real question a lot of people will have. Micro-benchmarks of ruby wouldn't answer it as well as the OP does.
At your age, open source is the best way to learn.
That way other developer will be able to point out some of the mistakes. And point you out on the right way to do something.
Besides this is not something that any developer cant do in a couple of hours of work. So not releasing your code doesn't really have any impact.
But 15 years old and coding is impressive. I was rotting day and night playing Civ 3 at that age :) Wish i didn't :)
You mean... If you make yourself sound like a somewhat normal and interesting person people will want to live with you? I don't understand how this was a breakthrough for you.
