skysight-inc/HackerNews huggingface dataset:
It's a bit indulgent but if I knew the guy wasn't going to perk up I'd just bring it forward.

"I'm getting some hostile vibes. Have I upset you or am I mistaken?"

It'll either give the guy a reality check or speed things along. No sense in us wasting our time.
and 'equals?'
>Isn't a more experienced person going to cost more?

Sure. But everyone's looking for senior developers. And salary tends to top out for senior devs, so it's not like salary scales linearly with age.
People Under 50 Prefer Texting to All Other Communication
> Three companies, three different responses on Hacker News, and three ultimate outcomes. [speaking of Codecademy, Meteor and Homejoy]

The only one on this list with an 'ultimate outcome' is Homejoy. Codecademy has no business model that I know of, and Meteor isn't even close to profitable.

Quora is also used as a 'success' case and they also don't have a business model.

I find this post does a pretty poor job providing any sort of supporting evidence for it's claims.
Is she a badass engineer or is she a sage? I don't mean it to be offensive but I've worked with oldtymers that wanted to coach more than actually do. They have tremendous knowledge and experience but if they're advisors or extra managers, they aren't building; some companies need and can afford that and value it, a lot of startup type places see that as an extra cost.

Our industry has these polar ethos that are pretty deep: one group sees old product that has stood the test of time as an indicator of quality. Like "UNIX has been around over 40 years, it clearly did some things right." The other, and it's insanely popular right now, thinks that anything that is too old clearly has some damage and its no longer good technology, like the neovim crowd, "vim doesn't even use the newest C standards features.." Some times you have to believe that you're doing something different and everybody did it wrong before and that's while you'll succeed this time, that's how you take the risk and ignore the downsides. being old can be a detriment to that belief.
"Any inventions, innovations, or ideas, conceived solely by the employee or jointly with others, relating to any current or future business of the company, at any time during the term of employment, are considered property of the company."

That was part of the employment agreement I had to sign when I worked at a large electronics/telecom company a number of years ago. So anything that could have been put on a public facing site (including technical articles) was not allowed. Of course, you could get a waver for individual projects but that had to be granted by I believe a VP level employee. Oh, and if you were to seek out that permission, unless you were already a superstar performer, you'd hear thing like "How do you have time for these side projects when you are behind on xyz project".
iOS disables custom keyboards for password fields, which is a great idea in most scenarios. This is what prevents Agilebits building a 1Password keyboard extension.
8 Myths Technologists Believe That Sink Businesses
I remember people even being pissed because Meteor raised more money than other projects. Doesn't matter that their marketing strategy and roadmap are near to perfect allowing them to maximize their market share while other (possible) better projects can't. A typical case of confirmation bias.
If you're willing to stand outside in the street for, oh, any time between 8AM and noon? Package delivery is notoriously annoying already. Drones that require in-person acceptance outside your building are not helping. Its a problem that needs solving, before drones can deliver anything.
Even More Brainfuck Optimisations
DraftKings Continues to Operate in Nevada
I suggest Philip Hazel's technical memoir (http://people.ds.cam.ac.uk/ph10/CIHK.pdf), which goes through his career.
> It all came from an ASK HN i did a while back where I asked "What problem in your industry is a potential startup"

Oh, that was your thread. Then thanks again, for posting that. I remember it because I found it somehow only few days ago, and bookmarked after reading through. The anwser there were not what I expected, and they revealed a whole world of problems that are not obvious but very important and in need of solving. They reminded me of this old edw519's classic:

https://news.ycombinator.com/item?id=1724198

(Also check out http://static.v25media.com/edw519_mod.html if you haven't seen it before; edw519 has posted some incredibly insightful stuff over the years; one of the best programming reads I've ever seen.)
Looks decent. The approach taken is the right one: we do something very similar with the Squire rich text editor (https://github.com/neilj/Squire) which I wrote for FastMail's webmail. Basically the browser can't be trusted to do any formatting itself, which is a slightly depressing state of affairs, especially as there has been zero improvements in this area for the last 5 years. I guess it's not shiny enough for browser devs to focus on.

Looking through the code, a few things jumped out that should be looked at:

* Native TreeWalker implementations are buggy in some browsers. In the end we decided it was safer to just implement the bit we needed ourselves (see comment at top of https://github.com/neilj/Squire/blob/master/source/TreeWalke...).

* The HTML sanitisation using document.implementation doesn't account for DOM clobbering so is currently bypassable with the right malicious content. I recommend using https://github.com/cure53/DOMPurify for this rather than writing your own. It's tricky to get all the edge cases right, so better to use something that's been reviewed by several people (and in DOMPurify's case also undergone a formal security review). Again, we use this at FastMail as part of our webmail.
You're probably not familiar with Atwood's Law[0]:

> Any application that can be written in JavaScript, will eventually be written in JavaScript

[0]: http://blog.codinghorror.com/the-principle-of-least-power/
Earn cs go skins by playing 1vs1 arena
The 3 Laws for Building an Agile Marketing Team
Downloaded and saved to my "to read" folder, thanks!
Yes thats my experience with a lot of young people too. So the question is whether there is some way to channel the experience of hacknat's father (see his comment) and make it available in a way that make sense to younger generations?

Is it even possible to bridge or are we just left with the cold hard facts that these things only happens when they happens.
Technical debt is not an issue, just, of scaling code (presumably you mean to large numbers of connections or database sizes or something). It's really an issue of maintenance. The more technical debt you have on a project, the longer any round of maintenance will take. Even simple tools that are just slapped together quickly might be easier to rewrite than modify, but rewriting them each time results in a different sort of technical debt. Implementation X has features used by user A, implantation Y has features used by user B, so now both tools have to be maintained or you try for Implementation Z that tries to pull it all back together (but probably fails, because you're still not properly budgeting time and engineers).

Overengineering is still a problem, but underengineering is the one I run into more often.
7 Tips to Speed Up Your Terminal Workflow
React Native deployment with Fastlane
> In comparison, the average age in more traditional tech industries like data processing or web publishing was almost 10 years higher than Silicon Valley/Internet firms.

Maybe this could be explained by younger folks, not bound to a family's worth of obligations, moving to California in droves from places all over the world?

So maybe we should normalize the data based on the age distribution in silicon valley.
Big Data Insights – The Aadhaar Story
> Giving good jobs to everyone

Whether they're qualified or not, right? Because there are not enough jobs for everyone, and most people are not qualified for most jobs.
[course] Introduction to Functional Programming in OCaml
Unless you own a Tesla Model S.
You know that "languages that compile to JavaScript" (thanks for not using the word "transpiled", btw) include JavaScript? Babel, Traceur - does it ring a bell? Would you argue that their users are not a "part of JavaScript"? What about TypeScript (it's just an implementation of some ES6 features + a powerful linter)?

Coffee is just a set of syntactic improvements (well, it's debatable - let's say "syntactic changes") over JavaScript. JS is too weak a language to implement this syntactic sugar inside of it, so there is a need for an external tool. But if you take a look at any Lisp, you'll see that people are building syntactic abstraction inside a language and that it doesn't make their code "a different language compiled to (their kind of) Lisp".

This is not to say that everything compiled down to JS is still JS. But the difference is quite neatly explained in Mathias Felleisen great paper: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.51.4... All that Coffee does are local transformations, equivalent to what you could do with Lisp or Nim or Dylan macros.

[EDIT: removed the "soooo cute" opening sentence, as it was brought to my attention that it distracted readers]
To evaluate whether age can be used as a descriminator for those attitudes and behaviors, I suggest you substitute "woman" or "black" and see how that reads.

There are young people who will only use the tools they are comfortable with. Ageism is the mistaken belief that this is somehow associated with your most recent birthday, akin to astrology.
Big Banks to America’s Firms: We Don’t Want Your Cash
The ultimate goal is to get more students to apply to these top schools - especially lower-income students. In a vacuum, this is commendable; certainly our top schools should do a better job of educating students regardless of tuition. But while this initiative will likely raise application rates, will it increase acceptance, matriculation, and graduation rates for lower-income students?

Most 'metrics' applicants are measured by correlate highly with income. There are SAT prep classes, schools with more AP/IB classes, personal statement 'helpers', interview coaches, and so on. This initiative needs to be coupled with a better understanding of the challenges that lower-income students face.

There is, of course, no mention of financial aid packages by the coalition. Increasing the amount earmarked to financial aid, particularly to grants instead of loans, would be more effective.
> This sort of memory really has fuck all to do with how your computer actually computes

Really? Was that necessary?
Coffeescript is a compiler/transpiler and Babel does a much better job of doing it, Javascript has all the requirements you want in the "Next Big Language", dynamic languages will have pitfalls, implementing type coercion and lexer/parser optimization are the reason for some of the "wat" stuff in that video, if the speaker made a a popular language like javascript he would have a better understanding of why some of those pitfalls end up existing
"confrontational - poor culture fit"
An issue with 50+ is, everybody looks at your resume and says "Why do you want to work at our position?" Because, you've done so much at so many levels they assume you should be a VP or something, and no longer be developing.
Well these are ASN.1 facts I did not need to know and I would like to not subscribe to that mailing list, but regardless thank you for the explanation.
I had this same thought - as many times I comment and then realize that it could be "taken" several ways.

It also amuses me to no end that someone is collecting and analyzing data from HN based (in part) on my sometimes idiotic comments and silly debates with Internet strangers.
escape from the situation ASAP
I was a part of finding a secret in the SNES version of Sim City that had gone almost undiscovered for over 20 years after release. These things happen.
How Not to Fix Fannie and Freddie
Except that they call it experience for a reason. I know of 2 kinds of people: one who keep doing the same things over and over again and don't learn new skills; and the other who constantly improve over what they know currently. The latter builds up the kind of experience that is immensely helpful in many technologies, and deserve the higher salaries.

I suspect a lot of companies try to save money on the short term by hiring inexperienced developers and then have to deal with the long term pains of supporting that code.
Yes it was quite amazing to get all that great feedback. I tried it on both Reddit and Quora but it didn't go so well could be timing could be that it's lacking the incredible varied backgrounds that HN after all have.

And yes Ed519 always have some incredible insightful comments on of my favorite commenters.
Programming languages carry with them certain conventions. Straying too much from the established code style will make your code a pain to work with.

It's pretty hard to hit the right balance between adhering to the original language and matching your DSL to the problem domain. If you build a DSL that requires a day of studying code and documentation in order to make a minor change, you might be better off without it.
Sonic Pi uses code to compose a dance party
They're more likely to put in the suicidal levels of overtime that many companies want to see in their employees. This isn't to say that older employees (including myself, almost, I guess I'm middle-aged in this discussion) don't work hard. But we're more likely to clock out at 5 to go see a kid's recital or to commit to non-work related plans and actually follow through instead of being intimidated into staying until 7 or 9 or 11 at night. We've been there, done that, and now we want to do something other than forfeit our lives to work.
Hey look there's one in the wild.
Full Stack Enterprises (Who Needs Architects?)
C makes these sort of problems more common and occupy more time/energy/source code than they need to. The language doesn't try to help the programmer with even the most basic of these sort of resource management problems. Most modern languages offer tools to handle some subset of them (e.g. GC for memory in managed languages, or destructors for memory and more in C++/Rust), reducing the burden on the programmer for normal resource life cycles and hopefully making it easier to handle the abnormal cases better.

Sure, it's not generally possible for a language to perfectly manage every resource all the time, but this doesn't mean we should just give up and throw away computer assistance in cases when we can have it.

C is an important language, but there's no need to look at it through rose-coloured glasses.
Moore's 1965 paper was about transistor count doubling every 12 months rather than frequency but "Moore's Law" didn't come into use as a term until 1975, by which time Moore was giving shrinking feature sizes equal billing[1]. And Moore himself wrote a memo endorsing a more general use of the term "Moore's Law" for any chip performance metric that doubles regularly. I can't find a copy online but I have it in my old Computer Architecture lecture notes. And performance and scaling were identical as long as Dennard scaling[2] lasted.

[1]http://www.eng.auburn.edu/~agrawvd/COURSE/E7770_Spr07/READ/G...

[2]https://en.wikipedia.org/wiki/Dennard_scaling
Dogs are not cats. The dog cares about you and knows you usually leave then. They have a very good sense of time even thought they "live in the moment."
Exactly. While an interesting read in showing how people can be wrong about later hits, this study is meaningless unless the failures are included.
It is like looking at all the winners of the superb owl, finding some negative comments about them, and then saying "see, you shouldn't listen to anyone". What about all the teams that didn't win and had good comments? Or bad?
Ask HN: How does Ask.com manages to make money?
I mean, don't know anyone that willingly uses their product, still they're everywhere.
Software rewritten in Python often performs better than the original in Python, too.
A few comments here saying that salary is the elephant in the room, which is a valid point, but I think the biggest elephant is the insecurity which lurks in the heart of every entrepreneur.

Co-founder/C_O types in their early 20s are often intimidated by people 35 and older, especially when those people have a long record of working in tech and all the war stories to prove it. The thought of hiring such a person, even when they are superbly qualified for the job and amenable to the compensation package, makes young entrepreneurs a bit uncomfortable.

I think there are two specific fears that drive this feeling of discomfort. First is the fear that older employees might see right through the fact that they have no idea what they're doing and call them out on it.

Second is the fear that older people will destroy the culture through their relative lack of enthusiasm and exuberance. In young founders' minds, it's better to hire someone who's been drinking legally for all of 18 months and who can be counted on to nod earnestly when you talk about "our mission" at the all-hands.
The Customer Is the Real Benchmark, Not the Competition
The program includes online coaching through SAT prep etc. That is part of the website, and integral to the success of the effort.

There are already programs for low-income and 1st-generation college applicants. I don't see how its provably more effective to continue plugging that hole, vs this new initiative to bridge students from high school to ivy-league. They saw a gap, and they addressed it.

Its so easy to snipe at Ivy League schools, no matter what they do. Thus my other comment on this subject.
This is my biggest fear as I enter my 30s in a number of months. I've been programming professionally since I was 20 and for fun since 10 - I can't imagine having to do something else, it's what I was born to do. I'm still relatively young but I just got married and the long hours and complete commitment I used to wear as a badge of honor no longer seems appealing.

Am I going to be able to do this for the rest of my career? I honestly doubt it, but I have no idea what I would do instead. My father was a draftsman for years and made good money but the market for draftsmen completely dropped out and he spent the last fifteen years of his career unlocking doors at a school. I have such a strong desire to stay relevant but I can't spend nearly as much time studying as I used to even a year or two ago. Sigh.
I think what he is trying to say that it is possible to publish an app or service online and gain momentum completely by marketing it on the web. In such case, I do not see how your color/gender/sexuality/age/etc would matter. You could hide yourself behind a domain and nobody would ever care who runs or maintains the thing.
Apple's auto ambitions sideswipe electric motorcycle startup
Yeah the hidden problems I am talking about are less specific.

Some of them are problems like workers unions standing in the way of automation of some shipping procedure or that people never thought about it as a problem but rather the cost of doing business.

Technology definitely removes a lot of those barriers over time as you say. But there are still plenty of problems that aren't technological and perhaps those are the most interesting.
Tendering with Ubuntu
Where will the rich kids go? If the real product they're selling, is hanging out with rich kids, perhaps for the hope of future opportunities, spouses, whatever, then sending them all to state-U or whatever will just make the new "cool brand" the state-U.

It reads like advice to improve bars and restaurants. Now, the best most profitable bars and restaurants are the ones doing (fill in the blank) the best. To really gullible people, if every bar and restaurant on the planet did (fill in the blank) as well as (cool place) then every bar and restaurant would be as busy and successful as (cool place)... all of them at the same time, LOL. Obviously if air conditioning or electric lights or indoor plumbing were ubiquitous then a new selection criteria would spring up and the best places would have a different mythology about why they're the best and the rest will remain inferior.

Its an intentional confusion of macro and micro policy.

On a micro scale yes its very easy to fine tune some random poor kid to get into the cool kids-only club. On a large macro scale all that's going to do is change the selection criteria so the poor kids can't get in, or the cool place to get into is no longer "XYZ". Its kind of like real estate blockbusting.

Before major social shifts, you tend to see a lot of pump priming like this to get the population used to the idea of changing things in that area. Likely there is a lot of upheaval anticipated in higher ed or young adulthood and very soon the ticket to the cool kids club is no longer going to be going to Yale... or Stanford... I donno what its going to be, but if we're subject to endless social engineering blockbusting of the ivies, I guarantee whatever the future is, it won't be the ivies.

Perhaps all rich kids will have their parents fund startups instead of going to business school or whatever. Or seeing as professional tutors and grad students are now cheaper than tuition, personalized instruction will become the norm. You don't need a piece of paper to get a title of nobility or meal ticket if your dad is rich enough...
175 threads really don't use that much ram. I know userspace stacks are large by default but most apps don't use them and they are never materialized. So even if you're using 1MB of stack space for each one that's only 175MB. You can easily fit that on whatever is the smallest AWS instance.

I imagine that context switching between 175 OS threads all in the same process wouldn't really be that big of a deal.https://www.quora.com/How-does-thread-switching-differ-from-...

Additionally there are many legitimate cases for for a lot of threads like disk IO. If you find your self having to push a lot of bytes to/from a high iops drive like an SSD / NVM drive. Unless you're doing large sequential transfers that you can do in one large call, you will needs submit many concurrent request to saturate the drive (via threads). Disk IO is not network IO.
The balance mechanism will keep them from falling backward - but interpret a heavy backward arch as "reverse fast" and a forward jerk as "damn the torpedoes, all ahead full" and a sideways flop as "spin wildly". So it's less a problem of them falling out or falling over, as one of them dashing around like a panicking bull, ramming things and people at 20mph.
Model-View-Whatever
When you're talking about memory performance you always have to include the latency, the bandwidth, and the size of the memory pool. 64kb memory pools have scaled in latency and bandwidth at the same rate as processing power - now they're sitting deep in the heart of the chip as the L1 cache.
The best recipe for choosing the right Dev Team
Everyone slaving away is not anybody's idea of Utopia. Once upon a time, we thought robots would take the yoke from our shoulders and leave us all more creative and happy.

Automation is fast approaching something like that vision. But now any time we talk about universal income or other such programs, it turns instantly to make-work projects. How can we keep the slaves working? Because, if I work, everybody has to work.
I'm not certain who this article is targeting, but it reminds of an acquaintance who would ask me detailed technical questions, misunderstand all my answers, and then two days later misinform me of the things I told him as if he were teaching me.