@KimMaida@UHC Sorry Kim, that's terrible. Also had horrible experiences in the past and have seen no indication they have changed. So bad that if job hunting and I found out a company used @UHC as their health care insurance provider, it would make me pause.
@DanielGlejzner In general though, regardless of format, if done right, tests can be super valuable if they test just the logic of the unit in question (component, service, etc) and not Angular or injected code. Those should be tested in their own unit tests.
@DanielGlejzner A lot of Angular tests are kinda a mashup of unit/e2e tests because of how the default is to instantiate and run the component. And both types of tests can be valuable but not sure the combination of the two is great without a lot of care, easy to end up with non-useful tests.
@tomasz_ducin Doesn't mean that is the recommended way, obviously it isn't today. And it ignores what can be a useful feature & may require manual instantiation.
I've made that choice in apps not to use DI, mostly for utilities or similar. So I know it works, even if it can complicate tests.
@tomasz_ducin Your first line is true in the sense that today, you can absolutely write Angular without using DI. So it isn't "needed". There is nothing besides convention and utility stopping folks from directly importing and using functions, classes, objects.
@brandontroberts@angular Again, not having done a deep dive, probably a function call that accepts the id as an argument, returns the rxResource result for use. But without careful thought, could end up duplicating the resource api (i.e. in more complex situations), which isn't super helpful.
@mikepainchaud @bomberger40774@alexander_amend@Tbyrnes2 If the QB was standing still, would the ball have landed behind him? Yes. Therefore, he did toss it "backwards". The ball ALSO travelled forwards in relation to the yard markers on the field (re: physics). Both things can be true, because they are in relation to different things.
@Tbyrnes2 @mikepainchaud @bomberger40774@alexander_amend Hence the details to work out. What happens if the player laterals it and is tackled immediately stopping their forward momentum but not the ball's? Didn't say it would be easy. Heck, there's sensors in/on everything, but the NFL loves the controversies, get's people talking.
@Tbyrnes2 @mikepainchaud @bomberger40774@alexander_amend That's a gross misrepresentation of what I actually said. If the ball travels sideways or backward in relation to the player throwing it and the player catching it does not catch it ahead of the player throwing it, that should be a legal lateral IMO. Probably details to work out.
@mikepainchaud @bomberger40774@alexander_amend@Tbyrnes2 The QB actually did toss the ball backwards, but, due to physics, it travelled forward. No one is seriously disputing that it was legal given today's rules. Hence, the underlying question being asked is whether it should. We disagree on the answer to that and that's just fine.
@mikepainchaud @bomberger40774@alexander_amend@Tbyrnes2 The question is whether it should be judged as forward in relation to the player throwing it or purely based on where it is on the field. As the rules stand today, it is illegal. Those arguing the counter point think the game would be better if it was based on relative motion.
@pavelsvitek_ Yes, bring back function declarations! Not to mention they allow code to be written so a person reading it doesn't need to scroll past all the various helper functions because they can be defined below the main code for the file in question (due to hoisting).
@MattAnderson_8 They should absolutely listen. But I hope they need an offer that blows them away before considering moving him. Preferably IMO picks plus players (preferably cap friendly). Probably unlikely.
That said, my preference is that they hang tight and move to JJ in a couple years.
@IceSolst Yup, and FWIW, that was an eye-opening experience for me and from then on I have made sure to do pre-interview prep, especially if I find out it's someone's first time on that side of the "table".
@IceSolst What're your thoughts on devs considering moving over to security? Or at least gaining exposure to the field? From what I know so far, I think I tend to prefer red team but probably slightly more exposure to blue team stuff to date.