nahname

Curious why you think Mercurial was a better product. I used it over a decade ago (coming off SVN) and it seemed to use a lot of similar concepts.

I agree. Usually your best people have an easier time finding new jobs and are the first to go. That will also work against future hiring when you no longer have the talent to draw in great people.

Ottawa was tricky because the jurisdiction belongs to the OPS, which fumbled the entire situation from beginning to end. It wasn't entirely clear if that was intentional either. The RCMP (federal) was brought in to break up the protests, but there was a lot of stone walling from the conservative provincial government.

There is also a world of difference between an organized protest with a specific purpose drawing awareness to a cause and thousands of people using commercial vehicles to hold a city hostage with no purpose or agenda other than a bunch of angry people unleashing their rage on the cities populous.

It's Active Record that makes rails code re-use especially unique. I don't know of any other framework where you can 1) be certain of the ORM 2) add database tables from a third party library 3) the whole experience not being cobbled together.

Ruby is practically the pseudocode they teach in schools. Which is selected for it's intuitive and simple nature.

It's a great tool for those that want to build CRUD apps quickly and get 99% of the things right. That speed comes from code re-use (mostly gems). Once you get experienced in rails, you primarily glue things together. It's fast, but does not feel rewarding.

What if their decision making is just doing what everyone else is doing?

Latency is important to sales and it hasn't been an issue for Shopify. In my experience, you need people that understand how to scale things more than you need a scalable language.

Something like this only works if your leadership team believes in it. If they give and receive feedback through the same system, align incentives to keep it going. Then this kind of feedback will thrive.

Your biggest expense will be people. Rails is ancient at this point, but I regularly see people ship product with it in fractions of the time. You can also re-write parts in rust later, when you need to.

>Pick people, not projects.

I follow this as well and it makes life better.

Redis is a cache

Yes, this would be for one quarter. I also agree it is quite similar to an ESPP, especially for the majority of people. I doubt many would be willing to allocate 80-90% of their total comp to ISOs.