yabai_yatsu

So like in say 1000 years the world will still be the same?

It'll crash one day. The world will change. Statistically speaking when it does it will likely be for the worse too.

Yeah there should be debugging classes, googling classes, and how to orient yourself in a massive, existing codebase classes.

>Literally spending hours trying to figure out how to set things up through hours of Googling doesn't really help that, nor does it promote the "figuring it out" people think it does - its just stumbling upon the right set of commands that let me move past this particular hurdle.

That's basically all of software development for your entire career. Never not had a day or a week not like that.

I know a guy who owns a domain in my country equivalent to user.com or test.com or something like that. He frequently knows what new tech companies are about to launch because devs doing local testing sometimes put the email as blahblah@user.com and he gets all the onboarding emails.

He received one while we were working on a project together and opened it up to show me. I thought it's kinda hilarious that some dev is just chucking that in their sign up page but he actually gets a real email because of it.

They're winning on both sides now no matter which option you go for.

And cars.

>Probably in the form of some Romaji-like equivalent (ideograms are too high a bar) but we will start to adopt it.

CCP will make you adopt it as-is, or GTFO.

I find it interesting their approach to language compared to Japanese. Modern Japanese borrows so heavily from English, especially if you're doing technical work.

Chinese, at the governments request, hasn't done that. Instead new words are coined as needed. They're keen on protecting the language.

We have about 6 physical DB servers, each client has their own db/schema on one of those boxes. Several thousand clients each with 10s of users per client. It brings in $15m ARR.

So, it works.

We're wanting to move off that architecture to something more future proof, but it's not our biggest pain point at this point in time.

Depends on the industry / clients.

It's significantly better for us as a team to be able to focus on projects and improvements that benefit everyone. I've noticed the business starts to suffer when we focus on individual clients with narrow needs. Any one client only brings in 1/4000th of our revenue, so spending 1/4 of our development capacity on just something for them is a huge opportunity cost when we could be using it on something that benefits all our customers.

It was a different ballgame when I worked on on-prem software that cos millions and we only had 10 customers with a few customers sharing the same version.

I had fun adding https support to a decade old PHP app for managing a domain registry where the entire thing was in German :) I spoke neither German nor PHP.

note to self: stay the fuck away from the Polish social insurance administration domain.

What's a submarine ad?

Traditional enterprise software suffers from this problem. SaaS doesn't really. Having to deal with different versions of a codebase for different customers was hellish and I don't want to do it again.

Not really. Your queries don't have to contain tenant Id if as part of your tenant context they have a connection string to their tenant DB.

Good point. That initial period is hellish (and amazing) and it does taper off somewhat but settles on a new baseline of permanently elevated difficulty.

It doesn't get easier, it just gets a different kind of difficult.