fole

Not really. Both usages are common in spoken and written English.

MS Stack Advantages: - Backwards compatible for businesses where that matters (any B2B company tends to need this) - Tends to be easy to integrate with Windows security/domains/etc - C# is a fantastic language, and it's getting better with each release - Has a growing open source environment, check out everything StackExchange has released, and NancyFx for my two favorite examples - Mono means that eventually you'll be able to swap out your server with Linux if you're brave and persistent - Entity Framework and Linq to Sql do a good job of abstracting your database layer - If you're using SQL Server (a pretty good, but expensive, database server) using a MS Stack means you can easily (and fully) enjoy everything it has to offer

IIS is pretty well documented online. Generally I can just google a short english sentence with exactly what I want to do and get it running.

C# Learning resources: What language are you coming from? If Java then just start using PascaleCase instead of camelCase. Then get Jon Skeet's "C# in Depth." If your coming from something else there's half a dozen good intro books (pick any, based on how good you are at picking up new languages). Then still get "C# in Depth."

Entity Framework is pretty straightforward to use...the MSDN docs are great, and the wizard gives you a good intro. Otherwise I'm sure there are books out there. I find experimentation and googling effective.

I worked for an NLP research think tank for a while and we always created text files as intermediate steps to each part of our system. It was basically a cache of each step, and you could restart the system at whatever step did work.

Hard drive space is cheap. Use as much as you want.

Please rephrase: "Full time - LOCAL"

I know I could do it with a pretty straightforward script, but it's not as simple as a ctrl+f, and it requires me being on a machine w/ unix tools (i.e. not a PC or mobile device).

Dear employers, please stop mentioning 'remote' unless a) you're OK with r-emote employees, or b) your business is all about about disrupting "r-emote controls", innovating "r-emote assistance" or something like that.

If your posting doesn't include it we'll assume it's not allowed, and you're well within your rights to toss out any application that does request it. Look at it as the easiest filter you'll ever find for resumes. If you really feel need to stress that the job isn't for r-emote workers just say 'LOCAL ONLY' or something like that. Pretty please?

@_whoishiring could you add something to that effect to the monthly post?

Try not to use the word '*emote' unless it's pertinent to the job posting. Some of us are looking to work from home, jobs and using the phrase makes it tough to scan through the results.