Grinding is for making cheap meat editable. It doesn’t mean it is good.

Different pacing is important on a team. Some rush ahead making a lot of mistakes. Some sit back and work on a thoughtful solution.

This is one thing Ted Nelson was hung up on. It’s tough to solve.

Funny, I always interpreted the gray branches in that diagram to mean short lived branches.

I just have dev and master with all my projects. Everything else is short lived. And short lived branches are rebased and squashed. Also, all devs work with forks to keep upstream pristine.

And there are those dogmatic about trunk development. I think if you follow the rule of thumb of don’t let dev and master get too out of sync you don’t need to do trunk.

I hate doing video on calls. But I might be more willing with a stylish red beanie. My appearance is my biggest concern and a stylish hat is a good idea.

TIL no one knows why it is called a Picardy Third.

> too much magic and implied behaviour

I think you may be confusing RoR with just Ruby.

Rails is its own beast.

I didn't confuse anything. I specifically mentioned Rails before listing those drawbacks you quoted.

I thought this was going to be the Elm email client in a JavaScript app. I'm getting old.

Elm (lang) looks interesting though.

Mac version has that setting too.

Here is a write up stating why Chrome doesn't do this by default:

http://arstechnica.com/business/2012/02/google-strips-chrome...

This is why as a dev I never want anything more than read permission with the production environment.

Their actions may be similar. What is drastically different than 100 years ago is what we know about global warming and pollution in general.