A lot of them are on job Visas and cannot easily leave.

And doesn’t this basically admit to the crime?

Why was this written like this? It makes no sense. I’ll git blame it and ask them what’s going on. Oh it’s me…

Isn’t new York flooded right now?

I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?

It will be questioned, but you have a good explanation. The tricky part is explaining it elegantly. Hiring managers kinda glance at resumes so you should add a sentence at the end explaining that you were let off due to internal company reasons. You should also try and get a letter from the company explaining that it wasn’t for performance reasons. Even better would be to get letters of recommendation from your coworkers and manager. Hopefully they’ll be extra nice to you due to your situation, but you need to be proactive about it.

Because it’s the country the company is based in.

Loyalty is a two way street and when it comes to jobs the company’s loyalty should come first.

By the end of the meeting you have 10 more questions and no answers and more meetings to discuss the new questions

Thanks! This is a super helpful answer!

Can you be more specific? I’d like to know what it’s missing.

In that case you will love typescript. I’m not sure what other imperative languages have both type inference and structural typing.

My opinion is you should use it when it’s useful, but not when it’s unnecessary. Their main use case is when you need to couple the functionality of functions to a shared state, and it’s particularly useful when you have multiple interdependent functions that need to be tied to multiple codependent states.

I find it relatively rare when I really need to use a class. Between first class functions and closures and modules and other features, I find JavaScript has a lot of tools to avoid needing classes. Classes add complexity so I only use them when the complexity they add is less than the complexity of the task they’re needed for.

You should check out “post modern JavaScript explained for mammoths”

Getting over it?

At the end I said at the volume of consumption we have. If everyone switched to wild game we’d instantly go from over population to over hunting and that’s not sustainable. You wouldn’t be able to support the volume with pasture raised without deforestation either. Raising your own animals also wouldn’t match the volume that people eat meat currently either. Even if we were more efficient with the meat we use I still think we’d be orders of magnitude off. I’m not totalitarian anti meat, I just don’t see any path to sustainability without huge decreases in consumption. The things you pointed out are great, but I think we can’t mislead people into thinking that will be enough for them to not have to change their eating habits.

Yes, it’s still a transpiler, I’m not saying it isn’t, but what I mean is that it doesn’t add any functionally specific to the typescript language. There’s a transpiler for TS that doesn’t even do any type checking at all and just does the type stripping and back porting. But of course, that’s not why people use typescript. All the features that are actually important to typescript could be done through a linter instead. If type annotations were added to JavaScript you could get most of typescript’s features with linting rules and just handle back porting in a more standard way.

It’s basically a book you can talk to. A book can contain incredibly knowledge, but it’s a preserve artifact of intelligence, not intelligence.

The common thing there is that they’re smaller animals. When you raise a large animal like a cow you need to sustain that extra size for the entire time they grow.

Does climate friendly meat actually exist? I don’t really understand how, at least not at the volume people eat meat today.