That's a great quote!

I just use Remix and use React in it's simplest form. Working for me so far but it might not work for big complex apps

Or with Remix Run which is great

Is Svelte still overly dependent on Rich Harris? He's great but that reliance put me off Svelte.

He was recently hired by Vercel to work on it full time so I wouldn't be too concerned about the future of Svelte

I believe there are at least 3 full time core developers now.

Got a good example of business logic not being in a component? Looking to learn.

I created a blog and wrote a post as a longer version of a reply: https://dinosaurs-with-jetpacks.com/posts/react-problems.htm...

Is it that they are global state to react but not to the programmer or his/her code?

It's that they are not shared like globals.

> There are always [] half-finished fix-the-world ideas conflicting with each other,

I work in a code base like this. People's suggestion? Introduce React!

Sounds toxic-ish! Why pick on someone who isn't paying attention?

It doesn't have to be toxic. If the team gets along well, it's all a bit of fun.

"crush your daily standup" - I am not sure that will be appealing to audiences outside America (assuming the target is dev teams worthwhile).

If I knew the first few mins of a standup were going to be a round table like "what's your all time fav book?", I would just join late.

Same here, this kind of "go-getter, overachiever" tone of voice in marketing seems a bit odd to the European audience.

Before I saw this comment by the parent, my impression was that the action-packed verbs (such as crushing) indicate that the subject mater is challenging and involves hardship. This attitude seems to come from a very stress-prone perspective, which, again, is a bit alien over here.

Thanks for the feedback! Icebreakers are totally optional. Some teams do it and like it, others skip.

That's fair enough. I would imagine managers would like it though :)

The worst tech team you've ever seen and yet they are generating 20 million a year? I think you should give them the respect they deserve and understand the limitations they have been under.

My thoughts:

* Get the code in source control straight away

* Get the infrastructure stable and up to date if it's not

* Get CI pipelines set up. As part of this, make sure the code is running through a static analyser. This will give you a backlog of things to work on.

* Organize an external penetration test to be carried out

* Investigate updating and/or consolidating the software libraries used (Jquery etc)

* Choose a page/feature to update on its own. Bring it up to date.

At this point, you should be in a much better state and you will have learned a lot.

> The worst tech team you've ever seen and yet they are generating 20 million a year? I think you should give them the respect they deserve and understand the limitations they have been under.

If the right opportunity is there, you can make a lot of money on an awfully built product that barely keeps it together. That doesn’t mean that there aren’t a lot of risks involved with that and that things can’t go south in a hurry.

I’m obviously not familiar with this project, but it sounds like a lot of things many’d consider table stakes are missing, especially for such a large source of revenue. Perhaps I’m not imaginitive enough, but I can’t come up with any limitations they might’ve been under that would justify that. I think it’s fair to call that out, even if they happen to make money despite this.

There is definitely loads to fix and it does sound like the team was inexperienced but they were successful it seems.