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.

Working as expected.

https://www.theregister.com/2024/06/09/rto_quit_study/

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.

An ESPP is directing earned cash into stock. You buy the stock at time of payment.

This is directing equity into RSUs or ISOs at the open of the window. You will be subject to price fluctuations over the window, which you wouldn't be with an ESPP.

It is bad. I dislike most "smart" things though, so take my agreement with a grain of salt.

If there is a culture of valuing writing, wikis work. The tool can only improve or detract from what is already there.

That is every project when the team is dysfunctional. Your language won't save you.

1Password started and currently has a self-hosted option. They are actively migrating to a SAAS model to justify monthly subscriptions instead of licenses.

The master/replica setup is interesting because we did something similar at Shopify, but I don't believe this is conventional for redis cluster. Can you expand on that a bit? eg: Looks like master/replica are together on a host, wouldn't you want them spread out?

You are including proxies for clients and server? How do they compare to envoy? eg: Are you doing anything clever to handle failovers transparently for clients?

Is the metadata storage just using redis?

TAO uses MySQL doesn't it? Would that make it more of a service built on top of MySQL, rather than a unique graph database?

Environments are generally handled via deployment configuration.

What did you switch too?

The clinic was morally wrong. Lying to their customers for surgeries they did not need is malpractice. This does not need to be solved by the federal/state government. The professional body should handle it.

It is worth pointing out that Ontario solar generation is only 1% of the power supply mix.

https://ieso.ca/en/Learn/Ontario-Supply-Mix/Ontario-Energy-C...

Too many are... Some are built upon a novel ideas though. Can we build web apps like desktop apps? Can we use one language on the frontend and the backend? Can we write everything in java?

Rails was built upon the novel idea of, "Can we build a CRUD app framework developers enjoy using?". As there is no silver bullet, this comes with tradeoffs many do not want. Performance is not a first class citizen. Code is prescriptive. A lot of rails apps are just gluing together gems.

I will say though, if you are building a CRUD app. There is no other option that will get you to done faster than rails.

That's too bad. I worked at a dotnet shop when I learned rails (on my own) and it was night and day for me. ASP.NET is a poor framework that was tries to take the windows decktop app experience and port it to web. Turns out that is a bad idea...

Which frameworks do you recommend today?

It's hard not to become jaded when every framework turns out to be just another team's personal preferences. I would say the statement is generally true about frameworks, but not true about rails. Perhaps the author did not spend enough time with rails.

All of the low inflation items are also goods that can be manufactured overseas.

There are bugs. After 60+ hours of gameplay, I can say Cyberpunk is significantly worse than the Witcher 3 was at launch.

The thing is, on PC, the bugs are mostly visual annoyances or obvious lack of polish. Menu's not updating, UI glitches in cut scense, etc... I've had the game crash on me exactly once.

The core game has a great story. The side quests are unique and interesting. Characters have depth. Combat is surprisingly good. Cyberpunk has all the things I need to enjoy it and I did enjoy it.