richman777

Agree, not really sure what the alternative would be?

EntityFramework? In my 5 or 6 years with .NET I've had more problems with EntityFramework than not. Most of the time it's overkill or just not optimized for the queries I could write myself. I'm a huge fan of Dapper.Net. Looks like there's initial support for core as well.

That's essentially exactly what it is. Our team got a demo from them trying to determine the best tool for our use-case and we simply couldn't justify it over google docs for how we do things, especially since we were already setup on the google apps platform for our domain.

But that's the point. You weren't a "good" employee if you're judging on one metric: experience with their infrastructure.

You were clearly good enough to get hired but all things considered you were the correct person the let go.

The distinction, and you seem to understand, is that it wasn't a personal thing. People say stuff like "let go of good people". What does being a good person have anything to do with running a business?

Not saying any of this is right or wrong but more musing over what drives business decisions and how people will often mix personal feelings into non-personal decisions.

I'll just add that your viewpoint is just the opposite side of the coin. I'm not as price conscious as I am convenience conscious.

It's not worth my time and anxiety levels having to deal with the side-effects of the budget choice which you listed out.

I also get a pretty nice corporate discount from my work which makes the big boys a no brainer. Although I still used the main car rental places before and the process was super smooth. Literally need a car and sign up for it in 10 minutes. Show up and get the car in ~5 minutes. At airports with kiosks you scan your license and go straight to get the car.

I have to agree with you. The OP said they clearly violated the notification statute for banking record. Except that statute clearly states a subpoena issued by a valid agency (here a lawyer involved in a case) was a valid reason.

They presented just as poor of an argument against the article as they claim the article itself did.

It's concerning to me that they can be charged out of concern for identity fraud and not actual identity fraud.

I'm not a lawyer in any manner but how is that not prior restraint?

I'm assuming this is the international terminal? I fly ATL->SFO every 3 weeks or so and SFO domestic is the fastest airport ever. I'll leave downtown SF at 1 and get to airport, drop my bag off and be at gate in ~30 minutes.

ATL on the other hand....even with TSA pre I can take a full hour.

Honestly for me the main difference are the IDEs. I started with Eclipse and the jump to IntelliJ was huge/great. But using Visual Studio was always a better experience.

Your point about the difference between the languages is definitely true re: Java 6. Java stagnated for a few years there while C# was improving with things I'd actually use. Java 8 is definitely an improvement and ultimately I think it would boil down to ease of use and familiarity when comparing them.

One thing I don't miss about java is server configuration. At the same time, I'm definitely relying on IIS doing things behind the scenes I probably don't know about.

I just want to chime in with a simpler answer. That's not really how Internet ads work. Ad deals between companies are fairly large and complex, at least the kind that are going to support a site like imgur.

Content is king and imgurs content is random and most likely junk. There's no consistency you could sell to a partner where'd they be willing to pay enough to allow something like DaringFireball does to work. The only way they're making enough is to put the junk we're dealing with now.

This is similar to my experience, but there have been situations that are similar to what the article posted. Usually however, those are weeded out by the time the deployment to production comes around.

In that case, the QA team is already testing off the feature branch and when they're done testing, you probably don't need a cleanup branch as you've tested the case where you're going to not use it.

It seems that the method posted in the article would be very useful for when you have a strict release cycle with versioning/features in place and you know with pretty good certainty when you are either going to sunset an old feature or require all users to be on the new feature. In that regard, I could see this working very well.

My mom has ALS and has an eye tracker. The camera is infrared and shows up based on any light in the room.

From looking at the tracking software it seems to calculate contrast between the retina and the surrounding eye to track what it is looking at.

Others have mentioned this but they've really migrated away from an IIS-only approach. .NET 2015 has really tried to emphasize that you don't need IIS. Take a look at some of the .NET core documentation. They're officially supporting Linux and OSX when it's released (tentatively Q1 2016...so far away) but it will "just work" out of the box.

http://blogs.msdn.com/b/dotnet/archive/2014/12/04/introducin...

Honestly I've found getting up and running with Mono and Kestrel really simple with the latest beta. I ran from Visual Studio without really doing anything and then switched to OSX and it worked perfectly. You still need to rely on some mono classes as of now for things that haven't been open sourced (Xml streams....) but even the mono implementations worked just fine.