While I agree with your initial numbers, you can get a decent apartment in White Plains around $1700 (or less if you find a deal, have lower standards, don't mind commuting, etc.).
Source: used to live/work there and just checked on craigslist.
Another typo: the link to the source is to "gethub.com/discourse". Funny thing is when I clicked it I assumed GitHub was having another outtage until I scanned the Url more closely.
In all seriousness, are suits still a thing for interviews? I don't remember the last time I heard of a company that was anything more than business casual dress (and lets be honest, many firms are much more casual than that).
In NY city and state, many judges are elected. However, they are limited to members of the NY bar (min. 10 years practicing in NY). Primarily wanted to point out that "professional" and election-based are not mutually exclusive.
Wow, nice memory; I remember that case, but his name didn't register in the slightest while reading the article.
As for the result, it's nice to see. I'm hoping for more transparency, but if the past year hasn't kicked the government into gear I'm not sure what will (short of the courts, I suppose).
Agreed, it was nothing more than a glorified tweet. While I generally agree with his points, some more depth and thought would have been much more preferable.
Related to these points, if you're using Bootstrap elsewhere and then have to work on a WP project, it's convenient being able to utilize the same classes, tricks, etc. that you've grown accustomed to utilizing.
Well, alcohol is a much more dangerous drug. As far as I know, there are no known fatalities from cannabis. It's also not physically addictive (unlike alcohol or nicotine).
If you use gitignore, the file(s) will only be local so they won't be accessible by other team members (or yourself on a different machine) and may not be backed up at all (depending on your strategy).
I can't speak directly to the differences with Unity, but comparing C# from .NET 2.0 to the latest you're missing: LINQ, dynamic data types, extension methods, optional and named method parameters, covariance and contravariance, async and await... and a whole bunch I'm probably forgetting. It's a lot more flexible now and lets you take advantage of dynamic/functional code. After coding in 4/4.5 for awhile, I certainly wouldn't want to go back to a 2.0 ecosystem.
Unfortunately in practice that's not always the case. People are often so set in their ways they'll still try to do direct ports of "the old ways" even if the new language/platform offer easier/more elegant solutions. It can be very frustrating.
Dynamic typing support helps in a pinch in C#, as you can avoid a lot of code in some cases where performance isn't paramount. I've personally used that in a few cases in the past.
Just to clarify, high end for last two ratios are 2560x1600 and 2560x1440. Both were available at least two years ago when I built my current machine, although after some quick research the 16:9 format had some available as early as 2007.
I was waiting for the punch line as well, and then scrolled up to see who the author was. His tagline says, "I defend laissez-faire capitalism, using Ayn Rand's Objectivism." So it's safe to say it's not satire.
Isn't this more of an issue with the current browser you're using? As in, once fully implemented in the browser you won't be prompted to enter it at all. Also, my understanding was that your session information isn't passed along (privacy feature), so it would have no clue you're logged in elsewhere.
Agreed that DMCA can also be used, but that only applies to US hosts/sites. His approach lets you handle other cases and also takes effect immediately.
I agree with a lot of your points; ego is a dangerous thing. However, I think it's important to differentiate between the two major types of rewrites (or claims as to why something should be rewritten): 1) The code is obviously subpar vs. 2) the programmer doesn't understand the code.
I've had to deal with code written by 3rd parties where I doubted the person was actually a programmer who wrote it; nonsensical or nonexistent naming conventions, large methods of dubious logic that were often never actually called (anymore?), and a general avoidance of best practices (and I don't mean advanced code; even simple things like code comments along the lines of "this is a for loop").
#2 is a different beast altogether and I think this more applies to your last paragraph. Is the source code too advanced for the programmer reading it, or is the code/architecture too obtuse? Unfortunately, I think it's often primarily programmer laziness more so than the design itself. I've been told by devs they don't understand a system and when asked what they don't understand, they simply shrug their shoulders. If you don't make an attempt to "get" the current system, in no way should you be allowed to rewrite it from scratch. You need to at least learn the mistakes of the current system.
Ultimately I think users are pragmatic; if DRM stays out of the way they won't care, and that's by-and-large how Steam is for most people. They also seem to focus on value-add items, such as being able to install (easily!) on multiple computers, operating systems, etc., whereas EA and other companies seem to provide more pain than pleasure. If a company appears to be trying to help people, they'll lovingly hand over their money. If a company seems to be only interested in their wallets, twitter and message boards will not be kind.
If you're primarily focused on older IE's, I think it's assumed you're dealing with a forced intranet environment (typically government/military/large corp) and/or need to focus on stability, not the latest and greatest. Part of me says "good riddance" as I never got the lock in to XP, but I get why devs might be annoyed with being stuck at 1.9 for the foreseeable future.
Sorry, to say there's 100% reason not to do anything is rather silly. By your own definition, what if your tooling lets you do codgen? Regardless, I've found code generation to be particularly useful in many scenarios and I would never dismiss it out of hand.
I don't envy your 2000 tables. Or hibernate, but if you have something that works for your team (and is testable) I'm not about to complain. As an architect, I will say that I do care about the storage model, but I'm obviously coming from a different place.