10 million earning 4% is 400k per year. That's a good bay area salary.

Couldn't "The Wisdom of Crowds" help with this?

Maybe if they started ranking the answers on a 1-10 range, allowing people to specify graduations of correctness/wrongness, then the crowd would work?

https://en.wikipedia.org/wiki/The_Wisdom_of_Crowds

Speaking as someone who just sold a house in the Bay Area (Dec!), house prices here are very much "buying the payment".

The valuation of the property goes up and down directly with the interest rate.

The ROI of the house (we bought in 2016) was ~8% on the down payment over the past 10 years, excluding maintenance and interest charges. As an investment, property is not a very good one.

To get that 8% on the down payment, I spent 4% on the remainder. It really doesn't net positive after the mortgage interest (with a 20% down payment). It's about "forced savings" and having control over your environment.

As an aside, since people are stuck in houses (mortgage rates and prop-13), there is a definite lack of starter homes. Everyone adds the second bathroom, meaning there aren't any single bathroom homes to be found. That increases the market floor.

If improving a portion of the codebase makes it better, but inconsistent...

migrate the rest of the codebase!

Then everyone benefits from the discovery.

If that's difficult, write or find tooling to make that possible.

It's in the "if it hurts, do it more often" school of software dev.

https://martinfowler.com/bliki/FrequencyReducesDifficulty.ht...

This isn't really about software quality, it's about the entire organization.

Consistency enables velocity. If there is consistency, devs can start to make assumptions. "Auth is here, database is there, this is how we handle ABC". Possible problems show up in reviews by being different to expectation. "Hey, where's XYZ?", "Why are you querying the database in the constructor?"

Onboarding between teams becomes a lot easier, ramp up time is smaller.

Without consistency, you end up with lots of small pockets of behavior that cause downstream problems for the org as a whole.

Every team needs extra staff to handle load peaks, resulting in a lot of idle devs.

Senior devs can't properly guess where the problematic parts of fixes or features would be. They don't need to know the details, just where things will be _difficult_.

Every feature requires coordination between the teams, with queuing and prioritizing until local staff become available.

Finally, consistency allows classes of bugs to be fixed once. Fix it once and migrate everyone to the new style.

It's also important to understand the makeup of the existing team, and headcount the team has.

If the team is already full of lvl5's/6's, there's not going to be enough senior eng work for a new one, particularly when headcount is being reduced.

Probably the programming env, like SIM toolkit.

There is a lot of fraud with UPI, specifically social engineering to obtain UPI OTP codes.

Since the card and the account haven't been previously associated, that's probably a risk model saying a human needs to verify the account before activation.

Indian cards also (I believe) have a mandatory 24 notice period prior to money being pulled - giving fraudsters a 24 hour starting gun to spend like crazy. That makes merchants that provide variable cost service on credit products twitchy.

https://support.stripe.com/questions/background-on-indian-go...

Not really, it's like asking which C compiler was best back in the 90s.

You had Watcom, Intel, GCC, Borland, Microsoft, etc.

They all had different optimizations and different target markets.

Best to make your tooling model agnostic. I understand that tuned prompts are model _version_ specific, so you will need this anyways.