johnnyb9

In my iPhone I have "do not disturb" setup and it only allows people in my address book through.

"We find a pass-through effect on tuition of changes in subsidized loan maximums of about 60 cents on the dollar, and smaller but positive effects for unsubsidized federal loans."

The incentives seem perfectly aligned... the advertiser doubtlessly doesn't care about whether it's a scrupulous ad or not. Paint.NET authors make money, and Google makes money.

The author suggests using virtual, but if your intent is not to allow child classes to override the implementation, this is certainly not "pure".

Visual Studio & ReSharper makes the code generation (Refactor > Extract Interface) and maintenance upkeep trivial anyway.

Fast forward to the in person meeting, they go through my solution and nitpick random things like "why use NuGet packages" or "why no test cases" (I had written them but they got mysteriously removed from the solution).

Finally the CTO speaks up and asked why I didn't write a GUI, as many other candidates had (mind you this was an application that accepted inputs and ran a calculation). I responded, "it's less effort to write a console application and the assignment said it was acceptable". CTO then snarkily asks me "do you always do the minimum"? I should have snarkily responded "only when I'm asked to code for free".

Thankfully did not get an offer...

Which is better?

foreach (var employee in staff) {

}

or

foreach (var employee in employees) {

}

The worst SQL for my eyes is the stuff that has multiple columns, etc. on the same line. Makes diffing stuff 2x as hard and you can't parse as much information. Though maybe I'm just used to that at this point.

Highly recommend the read