I’m really good at searching Google. I’m a “prompt engineer” too

Did it work? How do you know that? A consumer of your package sends a int when your package expects a string.

What now?

Use whatever is most enjoyable to you. You’ll be most productive working in a framework you like as opposed to one people online convinced you was “right”.

Take an hour or two with each. Use whatever is clicking best with you.

All these options are perfectly sound.

This is the stupidest use of this stupid meme with this stupid piece of shit that I’ve ever seen

lol, is that what you took away from that? He burnt himself out, took it out on his employees, and his audience.

In what way is he looking like a victim here?

Not defending LMG’s mistakes, but GN’s opinion that you should not ask for comment doesn’t hold water.

GN definitely has an agenda here. He made several comments that made it quite clear he’s resentful of LTT’s success.

While I don’t think anything he reported is false, it’s all wrapped in a narrative that relies on implications. He certainly makes a whole lot of hay about a few small mistakes and heavily implies LTT is in the pockets of their sponsors and a conspiracy theory that LTT is only successful because of some connections and preferred treatment by YouTube.

He’s very much trying to establish a narrative that LMG is wildly corrupt and undeserving of their success. However, a lot of it comes across as sour grapes.

It’s clear Linus has come to the conclusion he’s in way over his head. A small channel to a full blown media/tech company is a whole different ball game.

Coming up to the new CEO announcement, you could tell Linus was burning out. He seemed tired, quick to anger, and just generally in a bad mood.

That shit rolls down hill. Pushing for more videos on a tight schedule and burning everyone else out with him has led to the sloppiness.

As for Madison, I believe her. The company clearly has managers who have no business managing and simply got those positions via having tenure as the company grew.

Culture rots when there is no accountability, and when you have a burned out, grouchy CEO trying to do too much, too fast.

So what will matter now is what they do about it. Linus hiring a CEO is a good first step. I feel LMG has always been remarkably transparent and they aren’t pretending Madison’s story didn’t happen.

So if there is accountability for what happened to Madison (as in the people who totally did not do their jobs should be likely fired) and if proper training and processes are in place to make sure it doesn’t happen again, then at the end of the day, they’re doing what they can when shitty stuff like this happens.

Ideally it never happens. But if it does, do what you can to make sure it doesn’t happen again.

Say what you want about the LMS folks, they’ve always been open. Linus’ heart is almost always in the right place. He wants to build an ethical and transparent company. He is a huge tech nerd and that’s what makes LTT so entertaining.

If it continues to degrade, yeah, I’m going to pass on further supporting them. But until they prove they can’t or won’t act in good faith, I believe them

BUILD SOMETHING.

Learning concepts without the ability to apply them are essentially useless.

Get your hands dirty and build something that would be valuable to you and solve a problem for yourself.

Don’t get hung up on doing it “right”. Focus on making it work. Don’t worry about how it’ll work for a million users. Right now your focus is on making it work for one user.

As you go you’ll hit walls. Research how to get past them and keep going. Again, you’re going to make mistakes. DO NOT GET HUNG UP ON THIS.

Making mistakes is part of the journey. Even the best software engineers in the world rarely get things right their first try. It’s part of the process.

I was a big fan of Vue 2. Vue 3 is a completely different library if you choose to adopt the composition API (which is where everything is headed). If everyone is going to have to learn a totally new composition pattern, might as well look at what else is out there.

Kinda similar to the big overhaul between Angular 1 and 2

Vue 3’s Composition API and composables are more similar to React functional components and hooks than it is to Vue 2 and its Options API. That’s not to say that React Hooks and Vue Composables are apples-to-apples. They still have different approaches to reactivity and so on, but the programming model is more familiar between the two.

Coming to Vue 3 from 2 was a bit of whiplash. However I’ve been working with it for a few days now and have come to appreciate how much more flexible and powerful it is to have access to Vue’s reactive primitives anywhere - you don’t have to write all your business logic in the scope of a Vue instance.

That said, it comes with a much higher learning curve. Vue 2 gave you guardrails, an easily understood component class structure, etc. That’s what I liked about it as it scaled well to large teams. Whereas React scaled to a large team quickly turns into a complete mess. Ask 10 different React engineers and you’ll get 10 surprisingly different approaches to how to implement components and architect applications.