soulcutter

Sounds like tidelift

> Isn't the scope of curl/libcurl a bit too big?

No.

I do give some props for productivity and sharing a solution with the community (rather than just bitching about other peoples' solutions).

This looks pretty well-put-together to get a project started quickly, though my personal preferences might have been sass/foundation. To me those are small nitpicks in the scheme of things, and you're never going to be able to please everyone with your choices for defaults :D

The checkmark tables get under my skin a bit since they're mostly a specific set of dependencies (which of course your framework 'aces') rather than a comparison of actual features (in fairness, asset pipeline/DI I'd consider features).

Anyway, this is neat and looks worth some exposure. Keep on hacking!

Over 10 years later, and this is still relevant. It's scary how entrenched 'good enough' solutions become.

I have a fairly strong aversion to the way they implemented enum for ActiveRecord - choosing to back it with ints and also leaking that implementation detail through using the ordering of the enums as the int is a bad choice. Also the method name collision issues that go along with that are just silly - it would be so much easier to just prefix the methods with the column name, e.g. #status_new?

There's some other interesting stuff in there, though, and this is a good writeup of some interesting features.

I feel getting the right kind of feedback, or the right kind of information is the trick. How much value do you get from the various quantitative approaches you took? What just felt like navel-gazing?

Team-building, pride in your surroundings, and creating a culture all pay off huge in productivity. I see it as an investment, not a waste.

Best rspec rap, at least

I write code slower than my typing speed anyway. This sort of typing efficiency obsession leads people to use dvorak or crazy non-standard keyboards. No thanks, not worth caring about.