fidodo

joined 2 years ago
[–] [email protected] 8 points 1 year ago (2 children)

And doesn't this basically admit to the crime?

[–] [email protected] 8 points 2 years ago (3 children)

Isn't new York flooded right now?

[–] [email protected] 24 points 2 years ago (1 children)

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.

[–] [email protected] 2 points 2 years ago

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

[–] [email protected] 11 points 2 years ago

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

[–] [email protected] 1 points 2 years ago

"we organized to all quit at the same time"

"Noooooo! Not like that! 😭😭😭"

[–] [email protected] 3 points 2 years ago (1 children)

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

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

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

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

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.

[–] [email protected] 4 points 2 years ago* (last edited 2 years ago)

You should check out "post modern JavaScript explained for mammoths"

[–] [email protected] 1 points 2 years ago

Getting over it?

[–] [email protected] 2 points 2 years ago

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.

 

I've looked into these three and they all seem very similar and seem to cover the same use cases. Does anyone have experience with them? I'm having a hard time making a decision or even figuring out the pros and cons of each of them.

view more: next ›