skysight-inc/HackerNews huggingface dataset:
I have 10 years' experience in building and maintaining web applications using ASP.NET, C#, SQL Server, and Javascript.

Location: India

Remote: Yes

Willing to relocate: Yes

Technologies: ASP.NET, ASP.NET MVC, C#, VB.NET, Web API, WCF, Javascript, jQuery, Ember.js, Backbone.js, SQL Server, Mongo DB.

Résumé/CV: Available on request.

Email: dubeyankur@gmail.com
I think the hype right now is overblown.
I'M Not MARRIED TO THE IDEA
I know I'm going against the normal view of things here, but as I near 50, I don't see any difficulty with people my age finding work. The group I work with would kill to find someone good with 30-40 years of experience. They are just really hard to find -- either they are already happy where they are, are a consultant, are a manager/executive, or they aren't very good.

The problem is this: If you have more than 20 years of experience and want to continue being a employee programmer you only have a few choices. You can advertise yourself as a senior programmer and try to command a senior salary. Or you can advertise yourself as a more junior programmer and ask for a low salary. If you have the ability to do the senior position, then there is not problem. If you do not... who the heck is going to hire someone with 20 years of experience who is still performing like a junior? Even if they are cheap, there is value to the employer of imagining that the employee will develop over time. Someone who flatlined 15 years ago is not someone you want on your team.

The moral of the story is: if you want to be a programmer for your whole career you need to stay on the front edge of the industry. You have to work your butt off day in and day out to not only stay current but always improve yourself. There will never be a day where you "make it". You will have to justify that senior position that you are going to occupy and show that you are better than the up and coming young wolves behind you. If you are not prepared to do that, then you are better off not being a programmer.
I find people usually use it to mean the point where they could modify the code and expect it to probably work. I might not really understand all the details, but I know it well enough to become part of it. Which really fits the origional definition far more than understand.
Awesome, yep we are very aware of this. Will be updating the copy and making it more clear going forward. Thanks for the encouragement!
haha. I find these laws quite amusing.

In India, there "could" be a lot of ridiculous laws, but people generally violate all these laws. I think with such a huge population, a law that is quite unpopular is never followed.
And it would be such a better site.
I'm not promoting or saying I agree with it(which I don't) I'm saying it is a reality for a lot of older developers.

I suspect it is that people think they are less flexible and less willing to work unsociable hours though.
NxtGen raises $13.5M to fund expansion plan
I'm actually kind of amused by that. All the stubborn casino owner had to do was pay the guys off and hope the cops finally caught up to them. But pride and "acting on principle" ended up costing him an extra $15M.
Agreed. I recall people went from not knowing who was the CEO to cheering for him.
You can ask for anything and you should, if you are worth it.
It is localized, the work force is aging and the population is not growing at a rate to replace those aging out. For the most part I have seen the ration of young faces to old ones lessen. It seems my generation 40 is really the generation that grew up coding and therefore the age bounds are being pushed with us. I know in certain markets that is not true, but in others it is.
The thing is not everyone is capable of being a senior developer or in a leadership role regardless of how much they know. I'd go so far as to say most aren't.
hmm, had a t61p -- only lenovo blessed ssd would be allowed to work in this model, ditto for wifi cards.

screen is washed out and dim (lenovo consistently deteriorated screen quality),

also screen was positioned slightly asymmetrically, yet keyboard was dead center -- design/usability at its finest.

battery life was 2 hours (new) -- guessing due to nvidia chip, which ironically died shortly after warranty period (common problem, google it)

So,... no thanks
That was Usenet. How many people even remember when there was real discussion and community on Usenet?
Argument in favour of short variable names;

1. They're quicker to type.

Arguments against them;

1. You can tell what they mean by reading them.
2. Other people can tell what they mean by reading them.
3. Tab completion is a thing.

It's a no brainer.
Forecasting future is obviously impossible, but we could approach your question in a structured way.

First of all, allow me to question your premise. Software engineering is a quite lucrative job in the US in general, and in Silicon Valley more specifically. But in many European countries command average salary (with variations due to seniority, obviously). In Eastern European countries, India and China it is for sure a well paid job but not nearly as lucrative as it is in the US.

Clarified this point, the drivers of such high salaries are resource scarcity and high demand.

On the demand side, there are few relevant uncertainties: basically whether the economy will sustain the growth of the software industry (or, there is no tech bubble) and, on a longer timeline, whether evolution in programming technique will outpace the growing demand for software or not.

On the supply side, the main question is whether there will be an immigration reform or not and how it will impact the tech sector. Furthermore, more people are training now in coding than before, both in universities and after university using bootcamps or similar institutions. So the critical uncertainty is whether the new trained people are enough and good enough.

My humble opinion, given all these uncertainties and their probable resolution in the long term, is that sooner or later, "software salaries" will have to adjust downward. The only question is when and how fast. Aka, it will be something in the immediate or int the far future and it will be a hard landing or a smooth erosion over time?
// bad
const item = new Object();

// good
const item = {};

Literally useless differentiation.
> If those systems are (or are linked to) modified AGPL software (no matter how small the modification), they owe the temps, vendors, and contractors access to the source code to those systems.

Which is exactly the point. Don't modify the source code or use a different product if you don't want to accept the license.
As in every number in that set is a subset of the larger set of x < y < z. Poor language choice it's not true, yes I was wrong. I am just curious as to how much laziness and not necessarily confirmation bias has to do with the result. If getting it wrong had some kind of penalty or getting it right had some kind of reward ( money etc. ..), how much better would people do then?
The "more new lawyers graduating each year than there are law jobs" factoid is both stale and irrelevant. Most of those new lawyers had admissions scores well below the 50th percentile and are graduating from third and fourth tier law schools. Who cares about them? I doubt many would have had bright futures in programming, either.

Relatively modest undergraduate performance can get you into a law school like Northwestern's, where 87% of the class of 2013 "found work and reported a salary", and at least 43% of the class had a starting salary of over $160k, a very respectable ending salary for a programmer, especially outside of SFBA (http://www.lstscorereports.com/schools/northwestern/sals/201...).
// bad
const items = new Array();

// good
const items = [];

They obviously spent a lot of time on this guide, lots of investor dollars, and it's of almost no use.
Yes. Worst case is not printing the year, even for items which are from a previous year. ISO 8601 is the international standard on how to write dates and times. Get used to it. XKCD: https://xkcd.com/1179/

Japan has a strange tradition of dates and times such as 7-3 2530. Tokyo TV schedules have values like that. "2530" means 0130 on the next day. Businesses that close after midnight may give their closing time as "2600". This comes from a strange combination of military time plus a historical tradition that days start at dawn. At least it's unambiguous.
My point was that 1,1,1 is 1^1,1^2,1^3 and actually fits the pattern :).
The job market in CS is cyclical, with a roughly 20 year cycle; we are now at the point where supply will start to catch up with demand; 'everybody' will study CS, and in 4-5 years we will have a glut of beginners and bad programmers.

But, having experienced the bust of 2001-2002, I expect that, even at the bust, it will not be that bad. Also, programming trains you to think mathematically and analytically, so it is easy to move to a slightly different function.
Technology churn. I have been sailing on the concepts of http://www.tcl.tk/doc/scripting.html for the last 10 years. It is true that not all IT employers or clients reason at that level of thinking. But then again, that is good thing (tm). It means that we do not need to waste time discussing and that we can all save time. To cut a long story short, I do not experience any technology churn at all.

age discrimination. In online recruitment, nobody asks anybody else's age. What for, anyway? Nobody ever asks me for a resume either. A github account is more than enough. I am also over 40 and I have never made more money than today. I certainly did not make more money when I was 35.

You see, I have always instinctively felt that I needed to stay away from certain corporate situations and practices. I have always found them absolutely imbecile, annoying, constraining, and ultimately useless. What you are complaining about are issues that only occur in a corporate cocktail of idiocies, of which the ones you have mentioned, are just two. If you have always evolved in that soup of stupidity, you should not be surprised that you now suddenly get hit by that kind of things. It was just an accident waiting to happen.
I guess people take their pointless internet comments way too seriously.
Regarding using single quotes for strings (https://github.com/airbnb/javascript#6.1), I found it interesting that it's one of the rare sections where there's no rationale offered.

I guess it's just a stylistic choice in the end, but when we set up our own internal/informal style guide, my teammate and I spent a little while trying to come up with a justification for single vs double quotes. We ended up choosing double quotes based on the fact that JSON already made that decision for us: it requires strings be double-quoted.

(Although again, it's far from an important matter, as long as you're consistent), anybody has interesting rationales to share in favor of single quotes?
> Originally, Powershell did NOT have execution policy.

Yes it did. It always had default execution policy to not allow scripts to execute. Not sure how it was set in the Monad days before PowerShell 1.0 was released, but for as long as it has been called PowerShell, execution policy has been part of it.

On top of that, the .ps1 file extension is associated with notepad - not the PowerShell interpreter. When you "invoke" a ps1 file (like double-clicking it or have some program like outlook take default action), Windows will open notepad unless you explicitly associates .ps1 with another program.
Reddit is actively driving away their core users. This is a disaster for any product, regardless of where the potential lies. Until they are no longer your core users, you still need them.

On the other hand, this does remind me of all the pleas and hate that Facebook got about their permissive privacy policies. As much bad publicity that resulted, Facebook is still the king of social media.

To quote a reddit comment chain:

> Fuck Pao. I'm leaving Reddit.

> > No you aren't.
does bitcoin is fluctuate much and how do they convert/sell it into real money its hard i think
No, like July 4th. Or July 5th. Or October 31st. The 4th of July is a notable exception, and the GP's point of how we "normally (verbally) say dates" stands.
I'd suggest directed acyclic graph comments, too, so that a comment can reply to more than one other comment. Potentially super nice, but I haven't seen anyone implement them yet.
While I agree it is disrespectful, clearly there are plenty of people who don't respect him. If that question causes you to melt down and get someone fired then you're not worthy of respect.
Well at least we know she was someone principle.

Also, terrible management? "You disagree with me? You're fired."
> For example, the Department of Defense and Department of Veterans Affairs spent $1.3 billion on a program to build an electronic health-records database and abruptly stopped the project in 2013 after it failed to progress as planned. More staggering? In the past 10 years, about 96 % of all government IT programs that cost over $10 million were deemed failures, meaning they didn't meet their budget, timeline, or user expectations.

If this startup (and ones like it) is successful in getting traction taking over some of these projects, there are going to be a lot of very unhappy IT companies that were riding the gravy train for decades.

> A lot of the work we did last year for retooling the Healthcare.gov application process was figuring out which questions were necessary to ask of everyone and which ones were only necessary for certain people. Instead of having one online form with dozens of entry fields on a single page, the new Healthcare.gov application process asks a few general questions—like income and household size—then directs you to more specific questions based on your replies.

Jesus. You'd like to think there'd be some minimum baseline of common sense required to design an application of this level of importance.

> The newfound optimism about the government's technical future is inspiring, but can a 10-person startup really make a difference?

Obviously. You'd almost have to be trying to screw it up as bad as the original team did, unless this story isn't an accurate portrayal.
Use const for all of your references; avoid using var.
If you must mutate references, use let instead of var.

In my 15 years of programming javascript I've never once seen this matter.
Can we see your github?
Yeah, if we are being honest here, we can all stop pretending to wonder why the AMA went bad. It went bad because people just don't like the guy.
The whole tone of this question smacks of "gold fever". I'm guessing you're thinking about entering the field, so I'm going to tell you what someone told me during the original dot-com bubble:

Only become a programmer if you truly enjoy it.

If you're getting into programming solely because you think it's "on fire", you're going to have a bad time. It is always possible at any given moment for various reasons that VCs could collectively pull back on tech, or some major employers could downsize, and flood the market with excess talent. No one can predict this shit. There was a time post-bubble when many programmers could hardly give away their skills let alone make big bucks. Not long later there was a time when it was a foregone conclusion that all software development was going to India. Now here we are talking like "is this money wagon going to go to infinity?" and I say stop. Just stop. Do it because it suits you. Do it because you like the work. Please don't do it for "the money" which may or may not deliver for you, ever.
FDA approves Theranos test for HSV-1
No Shoes on Hacker News
Marc Andreesen for example has a suboptimal head structure for baldness, however I'd venture to say straggles of the remaining hair would look worse.
Shaved head > BLding head IMO
You had it set to "last 24 hours". There are many stories mentioning shoes: https://hn.algolia.com/?query=shoes&sort=byPopularity&prefix...
At least in Ruby, you can only do string interpolation with strings in double quotes.
If you refer to this line: "over 80% of maintenance effort is used for non-corrective actions." it doesn't say that 80% of the software development effort goes to maintenance at all... it says that, of the X% maintenance effort, 80% is not used for bugs. Then it gives an example for the accuracy of this number, 21% of bugs, so 21%+80% ~= 100%

It doesn't attempt to explain what X is at all. It could be 10% or 90%, however in my experience, and according to other's point of view[1], 60-90% of time dedicated to writing code being maintenance time sounds legit

note: modifying = 5 * writing new code (20%). Understanding is another matter, but also important:
[1] http://blog.codinghorror.com/when-understanding-means-rewrit...
Yes. There was no prior mention of magnitude. I benefit vey greatly from my local grocer, s/he provides with quality goods at a reasonable price -- making an impact on me.

Now, how do you draw the line with 'significance'?
The comments here suggest people are missing the full significance of this problem. It's not just a cute number puzzle - it demonstrates a profound human weakness that has a deep impact in everything we do.

1. People that think having a gun in the house makes it safer will not try to design an experiment designed to demonstrate the opposite.

2. People who think organic food is better for you than regular food will not try to look for evidence that the two types of foods are equally healthy.

3. An Israeli who believes the area where he lives was uninhabited before 1948 is not going to think about what kind of evidence would contradict that belief.

I'm not saying the views above are incorrect. It's just that we are all guilty of falling in love with our beliefs when they should be mere acquaintances. Hence the quote, "People don't change their minds. They die, and are replaced by people with different opinions." [1]

[1] http://www.paulgraham.com/quo.html
Start here: http://www.paulgraham.com/corpdev.html
Interpupillary distance, the distance between the centre of the pupil in one eye to the other.
Plug and play predictive customer analytics platform for digital marketers
Reddit is really poorly managed. If Google bought it and gave it an overhaul I'm sure it would be welcome over the current administration. Plus, the "non-vocal users" simply don't care.

I would start with rewarding administrators with payment (akin to youtube, somewhat proportionally to views -- this creates a strong incentive towards fidelity), revamp post priority algorithms, and add some basic functionality that you need to install an add on (!), RES, to get (what other top 100 website needs this?).
JavaScript up to ES5 doesn't support string interpolation at all. ES6 introduces backticks `before${var}after` for that, but there's still no functional difference between single and double quotes.
If JSON requires the string to be double-quoted, then it's more convenient to use singe quotes, since your embedded JSON string (if you ever used it) won't need to have its quotes escaped.
My rationale for single quotes is also that JSON chose for you -- if you have JSON-formatted strings in your javascript and you use single quotes for your strings, you don't have to escape the double quotes.
How  to Become More Confident
Have you looked Selenium's Python integration? [1] If so, what issues prevent you from using it?

1. https://selenium-python.readthedocs.org/
That's because let and const where officially introduced in JavaScript this year, see the JavaScript standard ES6 (or ES2015).
I had a lot of fun on reddit (I was a verified "shitlord" on FatPeopleHate), but it never was monetizable. It's not a business and will never be, no matter how many users they get.
>> Why does this have to happen at the expense of public access?

I didn't understand from your answer why validation and restriction of public access need to go hand-in-hand. When I left academia, I was no longer able to read tax-payer funded research papers without paying an exorbitant fee per paper. Are you saying that lowering the fees is would lead to "losing a ton of money"? Do you mean the publisher would become unprofitable, or become less profitable?
>No, but I can.

I'm not sure thats fair. Yes you can, but I'm guessing you aren't the type of person to be caught running software 7 years after its EOL.

Or put it this way, Office 2003 was discontinued in 2007. Thats like running Debian 3.1 today (Sarge, 5 stable releases ago), and complaining about continued support. RHEL2.1 was EOL'd in 2008 (RHEL6 is the "old guard" now).

If you wouldn't expect continued support for Debian 3.1 or RHEL2.1 in 2015 there's, I don't see why its a problem for Microsoft or how it makes open source any better. Sure, yes you could patch Debian 3.1 yourself, but ultimately how fruitful is this effort, and how many people can be expected to to write kernel patches? Even if Microsoft said tomorrow Office 2003 was open source, how many individuals could you expect to have the know to patch their installations?
Remote Work: Why Virtual Work is better than offices
Digital marketers spend lot of time on analysing data rather initiating conversations with prospects and customers. We decided to build an system which will be a great assistant to digital marketers help them to be more productive.

Few clicks you would know which segment is best, where they will engage and start an engagement campaign.

We are looking for early adopters with whom we are looking to co-create the product.
Fixing it too well may be incompatible with some personal liberties and privacy. A big problem is that the Government has no really solid way to authenticate you online. If it did, you'd need to provide far less info when signing up for something. Some of the Scandinavian countries work that way.

Should the US? Should Government web sites work on the policy that you should never have to tell the Government something it already knows?
I tried the link provided but was unable to display the page, though as a citizen of the internet I can take a stab at the flavor of the insults.

Given her recent gender discrimination case against Kleiner Perkins and potential appeal, it would have made strategic sense to block anything sexist. I don't know if that's what was in the content of the replies - just guessing.

Also guessing it was pretty racist, and <checks underpants - yep, white penis> I can only imagine that shit got old more than a century ago.
Interesting. Is that common in your workflow to embed JSON as string literals in JavaScript? Never had to do that. I'd probably use ES6 backticks, so as to have multiline support and skip the need to escape both single and double quotes.
Given the bizarre nature of Jackson's comments in that AMA, I somewhat suspect that Victoria fucked up by writing down what Jackson was saying over the phone verbatim.

Doing that is usually a good way to make somebody seem rather illiterate. For example, people are much looser with the way they structure sentences and organize thoughts when speaking in an unprepared manner.

When you listen to audio of them talking, everything seems normal because we have different expectations for written English and spoken English. When you don't get to listen to the audio but only read a transcript, then you start to get problems because then you have written English that only meets a spoken English standard.
Top comment from that gizmodo article: "Reddit is legitimately full of the most self important toxic people ever. It’s also home to a huge variety of all manners of genius and hilarity."

I will miss it. As an Old Person™, reddit was the closest the modern Internet has come to replicating the heyday of Usenet in the 80s/90s. But because it's controlled by a single corporation instead of federating among all internet service providers, it succumbed to the corruption of the pursuit of captial. RIP.
Voat where all the worst parts of reddit threaten to go after being banned(before creating new accounts to continue using reddit).
Trying to grow a site to Reddits size on IIS? That won't end well.
Half of the top 10 subdreddits are now private