skysight-inc/HackerNews huggingface dataset:
My experience with Japanese people (I used to work in a Japanese company and attended a lot of meetings in Japanese) listening to someone else in meetings is a lot of "Aaaa, sou sou sou sou. Sou desu. Wakarimashita. Hai. Wakarimashita. Mmmm. Mmm Mmm. Sou desu." I eventually did some of it myself. Seems like a lot of aizuchi to me :P
The Importance of Specific University Courses
My understanding, via limited testing, (might be wrong) of CloudFront's content behavior is that new things show up pretty quickly (hour?). Changed things would be subject to the expiration time limit. So, edits of old posts won't go live until the original objects expire - unless you invalidate the cache for them.
Unless you were Director / VP / C-level or above, I wouldn't expect to see anything.
While I am a staunch advocate of UBI as a solution to a massive swath of present and emerging problems around the world, I also do not see the experiments around it leading to its mass adoption in at least the span of decades.

Things have to get much worse (and they will) and we will need some active social unrest (on the scale of Occupy Wall Street or Black Lives Matter, except informed about UBI and fighting for it in a unified message) before the wealthy will acknowledge that if they want to stay wealthy, they need a society to be wealthy within, and we won't have one if people are destitute and starving by the millions because traditional capitalist expectations of work and compensation break down in the face of growing automation.
Apple shipped the first mainstream products with USB.

" Apple Inc.'s iMac was the first mainstream product with USB and the iMac's success popularized USB itself.[15]" - https://en.wikipedia.org/wiki/USB

I built my own PCs at the time. it took about 5 years before USB gained wide adoption. Today the smaller, reversible, faster, USB C standard is on the verge of becoming a standard. I feel like it's the late 90s all over again. Apple first and the PC industry taking its good old time. Why is it so difficult to ship a couple new ports, along with that legacy USB?
Yeah, they've got a cookbook out. http://www.amazon.com/gp/product/149262571X
Google is in the 'early stages' of expanding internet access in Cuba
Difficulty is relative. If you don't study modern C idioms your C code will be crap. Same goes for Rust.

Honestly using higher-level languages is the same mentality as taking a pill to magically lose weight. It's quick, but detrimental (to programmers ability) in long term.

Programming becomes easy but in the long term most people forget how algorithms and data structures work, in addition to cache mechanisms and other optimizations.

Until hardware changes drastically there's no sense rewriting everything (unless of course it's just for fun). It's better use of time to study Math and lower-level concepts instead.

That being said, most businesses will take the quick pill instead.
No, watch this documentary:

http://www.pbs.org/video/2320041315/
I sent an email to Uber about this. Other companies like facebook, xbox have a way to create test accounts.
I don't know if the study's author has a link to her compiled data but I was curious to see if the data was easily available officially...and it turns out there's a convenient (convenient, if you know how to scrape and parse PDF tables) list here:

http://www.fws.gov/Endangered/esa-library/index.html
Walmart has no problems with them. What you're essentially saying (I think) is that generic online retailers cannot handle the amount of returns they need to to stay in business so they need to get rid of customers to stay profitable. Seems spot on to me.
This blog post was 3x longer than it should have been.
The SO survey results explain the situation clearly enough, which already makes it obvious that everybody's perception about JavaScript being used in almost every aspect of programming and by most of the devs, mostly because it was implemented first on browsers, which are now some sort of ultimate medium for applications.

But anyways. This seems to be just a repost of the SO survey to what appears to be a victory to JS lovers.
I agree, I don't think it would be super effective to say "Please don't pirate", like an after school special or something.

What I think they should have done was used it as a marketing opportunity and given the pirates another opportunity to buy they game and get more value after they have already been playing it and know they like it. (Get more value by removing the severe pirating problem within the game so that they can progress farther)
Chronic pain, fibromyalgia, chronic uticaria, essential tremors.

Every week my great aunt looks for some news about essential tremors. Extremely common, affects walk, hands, throat, sometimes head movements. All there is to treat is deep brain stimulation, or treat the symptoms with stuff like beta blockers. Giant hammers but no looking into the underlying causes. We know so little.
Unfortunately, Twitter's user facing technology has been declining in quality. It's too bad because I like twitter a lot. I can report the following issues:

1) many links to deep inside twitter (eg: user's feed or a particular tweet) will actually bring me to my twitter home page.

2) android app destroys the battery. This is true of many social media apps, but unlike facebook, twitter's mobile web app is barely usable. It keeps insisting that I get the native app and it's extremely clunky and slow. Also, many features aren't there, particularly twitter search.

Back when they were more open with their api and there were alternative clients it was a better experience.

I know none of this has anything to do with their lack of a business model. Also, I don't want to discount their contributions with bootstrap and the big data stuff they've done. Hopefully they won't end up like Yahoo.
Seriously? You can't imagine why people might want to take advantage of modern technology while simultaneously wanting privacy protections?

Your argument reminds me of this Onion video: https://www.youtube.com/watch?v=lMChO0qNbkY
>Since the times when you need "just scripting" are about 0.00001% of real-world cases

I would argue the opposite is true.

Most of the time an analyst builds regression trees in the mktg department for a retailer. Or similar situations like this.
"Profits are independent of investment decisions, at least if a company is not engaged in accounting fraud."

Right or wrong, for good or worse, this author is being deliberately obtuse on this matter.

Amazon generates profits and re-uses them before they're on the books as profits. It's a tactical decision, and the letter of the accounting law doesn't contravene their strategic decision.

If you don't like it, don't buy their stock. They've been at this game for a very long time.. so, it's no surprise.
Isn't it the other way around? One can downvote a post and then reply to it, but can't downvote replies to one's own post?
Sorry for the next-day response, went to bed shortly after posting that.

Long story short, this paper received a lot of press attention when it was published to the ACPD last summer for discussion: http://dotearth.blogs.nytimes.com/2015/07/23/whiplash-warnin...

Which led to a fair number of climate scientists upset about what they saw as the press reporting on preliminary results. It's linked in that article but the key point is that Hansen has spent the last ~10 years calling out what he sees as a reticent attitude among climate scientists towards (what he feels is justified) alarmism: http://iopscience.iop.org/1748-9326/2/2/024002/fulltext/
After 12 years of primary and secondary school, one would think they'd have gotten some, wouldn't one?
As I said, I don't want to learn how to use 5+ tools. I want to be able to install one thing, have everything work out of the box, and learn how to use their uniform and standard way of doing things.
oh, i know -- i got spoiled working at matasano where we'd usually get the first crack.
try! macro results in code that looks pretty similar to exceptions: https://doc.rust-lang.org/std/macro.try!.html
You're right this would be solved if we had babies in nursing homes and waited until someone was 80 to teach them calculus!
It is a rewrite of gnu coreutils because cureutils sucks. It is a good reason !

I guess it doesn't intend to be a 1:1 rewrite of coreutils then ? The public available function to users will be rewrote.
I completely agree. I spent lots of time, especially after the Paris attacks, reading about Daesh, and the origins of their beliefs. The Atlantic article you mention is a fantastic primer on this very complex and hard-to-digest topic.

Many people seem to view doing this kind of reading and learning as some kind of gesture that is sympathetic to those who commit such acts. I will never understand how wanting to be educated on the history of a group automatically means you are siding with them ideologically...but I am from the midwest and left quite a few beliefs I will never understand.
When the Scrum Master Becomes the Impediment
> I mean if you have to write that match construct around every function call

Not quite.

1. you're supposed to handle errors around function calls which can fail, which is a strict subset of "every function call"

2. rust has a number of higher-order constructs to facilitate that handling[0][1][2], not just raw `match` statements or expressions.

That aside, for rust explicit error handling is considered a feature both at the language level (allows for less runtime requirements and much stronger guarantees — check out exception-safe C++ for what happens when low-level meets exceptions) and at the user level (by forcing a conscious and explicit decision, whether it's crashing the system, handling the error or passing the ball upwards)

> the code quickly gets bloated, doesn't it?

Does C code quickly get bloated? Because you're also supposed to check for error codes after each function call which can fail, and C doesn't provide much abstractive power to mitigate that.

[0] http://doc.rust-lang.org/std/result/enum.Result.html

[1] http://doc.rust-lang.org/core/macro.try!.html

[2] https://github.com/rust-lang/rfcs/pull/243
but that's a problem if so

It's not necessarily a problem. It actually cuts both ways.

The code is not going to benefit from updates, but the code is not also going to be harmed by updates. Think API or behavior changes. Additionally, if the use case for a dependency changes, sometimes the "new" solution doesn't match well.

Ex:

I work with jscript in ASP sometimes. A javascript library changed such that instead of doing iterative processing of nested items (pushing an item on to an array, then looping, popping off the item and processing it, then repeating), they changed to use node's nexttick with some logic like 'we want to move to nested function calls for processing, and doing that iteratively would blow the stack, so we'll just use nexttick so it won't have an increasing stack'. Well, jscript in ASP doesn't have nexttick or any equivalent timer. So while the original code itself worked flawlessly, the use case of the authors moved and we pulled that code in as an external dependency.

That's obviously an extreme case, but I can't really count the number of times that an API change in an NPM package for node has meant modifying code, without a change in functionality.

So yes, you get updates, and sometimes those are going to be security updates and real bug fixes. Other times though that update is going be adding new functionality (and possibly new attack vectors), or dropping support for your use case, etc.

Like many things in our field, it's wisest to look at the risks in all cases, evaluate them for the specific situation at hand, and then choose the appropriate one, rather than cargo-culting one 'best practice'.
I'm not entirely clear on your point. Are you suggesting that writing in C as opposed to Rust is somehow morally cleansing? Or are you suggesting that having higher level abstractions is somehow ruinous to ability?

The evidence is pretty clear that programming in C does not confer enough skill to prevent disastrous mistakes despite its near-hardware level of abstraction, so I'd really like to know what you're saying here.
Wow. I was surprised that comment came from a smart, accomplished guy. It's nonsense. What he's essentially saying that the existence of compiler bugs in Rust refutes using it as a C alternative. Let me try that: the existence of hundreds of compiler bugs in C compilers over past years means it can be relied on either. CompCert had a few at spec level so we throw it out, too.

Realistically, you rewrite the components piece by piece in the new language. You make sure each compiles right with testing and review. You report any problems to the compiler team, who fixes them. Eventually, you're whole app is in the safer language without a lot of work. You might even swap them where safer one becomes reference code with other one there for any platforms not supported yet or too buggy. A diversity benefit as Hipp mentions.

With all of this, the program becomes immune to most memory & concurrency issues while being easier to maintain. Its undefined behavior will probably be a fraction of C's in number and severity. That's a net win.

Note: I'd have told him Ada/SPARK instead of Rust given it's been stomping C in embedded safety for a long time w/ lots of tooling for verification activities already there. Counters his compiler maturity argument, too.
Not necessarily. They are trying to be "health conscience". Sugar-free diet! Fat-free diet! Both arguably good, healthier diets to have.

Then you get people who reason themselves into "Gluten-free!" must be a good thing! I blame the "____-free" moniker often being related to "healthier for you" diets. People will seek out "gluten-free" and there have been cases of restaurants serving "gluten-free" food that wasn't actually "gluten-free".

I've heard a number of cases from actual gluten sensitive individuals who have a love/hate relationship with this fad.

1) More gluten-free things to choose from! Yay!

2) More "gluten-free" things that can potentially kill them, causing them to have to be even more careful than they already were with what they choose to eat! Boo!
Engineering Culture at Lob: Six Ways to Move Fast and Not Break Things
It comes from the incentive structure of the recruiter and says less about the potential hire.

Recruiters are often paid a commission for every one of their successful hires and that commission is often split between an immediate payment and a payment (or payments) when the hire hits specific milestones (6mo, 1 yr, etc). Recruiters don't like trying to fit contractors into non-contract roles because they're worried about the contractor leaving before the recruiter's remaining commission is paid. If that happens, the recruiter puts in just as much work and gets paid less. They'd rather discard those resumes that they consider to be riskier and focus all their time on people with a history of staying at least 2 years in every one of their jobs.
> Difficulty is relative. If you don't study modern C idioms your C code will be crap. Same goes for Rust.

That's not a valid argument for why better tooling can't help alleviate some of the difficulty.

> Honestly using higher-level languages is the same mentality as taking a pill to magically lose weight. It's quick, but detrimental (to programmers ability) in long term.

If that were true, the most effective programmers would only code on assembly.

> Programming becomes easy but in the long term most people forget how algorithms and data structures work, in addition to cache mechanisms and other optimizations.

Why would higher level languages obviate knowledge of any of these things? If anything, I think it would help by reducing "noise" from incidental complexity; e.g. ownership in C vs Rust.
Giving workers bargaining power in wage and work condition negotiations is only a good thing, absolutely. It should be obviously unfair to the vast majority of people that you bring two people to the table when you apply for a job (in effect, at least) - a capitalist business owner seeking to profit and accumulate wealth through markets, and someone who doesn't want to starve or go homeless. Those kinds of negotiations are anything but fair.

UBI would see a dramatic shift in the valuation of jobs, in the ways employers can treat their employees, and in what work society values having done. I postulate often how I believe a lot of the tremendous flow of working into the advertising and service sectors has been due to the subconscious social desire to avoid the collapse of work, so we produce fictitious work with minimal or no net productive gains or utility to keep people busy. There are millions of white collar workers who wake up every day in fear of their job being replaced with software, and of truckers fearing the inevitable self-driving vehicle revolution on the horizon, because we are not starting on the path towards automation, we have been on it for decades, we have simply subliminally skewing our society to try to compensate for the implication that real productive labor has been moving out of the hands of human beings for a long time now.
As far as I know , most databases have their own proprietary way of dealing with schema upgrades and rollbacks, you will need to understand how its done in DB2 , Oracle, MySQL etc and then create a common pattern out of it.
http://www.onlineprogrammingbooks.com/download-pdf-foundatio...
I am in my mid-60s and I don't feel like I have suffered any age bias either at large companies like Google or small startups I have helped.

I sort of grew up with computers. My older brother and I got a mini version of a mechanical difference engine when I was a kid. When I was about 11 my Dad got me occasional use of a time sharing system, so that planted some desire in my brain for using computers. In high school I took a class at a local university.

It disturbs me to hear younger people talking pessimistically about their future careers. I advise them to keep learning and working on things that are useful and that they enjoy working on.

Edit: I did run into age bias, or at least I think it was: I had done a homework interview assignment and phone interviews for a back end job for Wikipedia and it seemed like they very much liked what I offered. Then, 1 minute into a video conference interview, I was brushed aside. So, I should have said that I have never had on the job age bias.
> There is some (unintentional I'm sure) age bias even in the response of "stay relevant" as if the implication is that older devs don't do that as a matter of course while younger ones do.

Maybe it's bias. But I know for myself that the older I get, the less time I have to spend on staying relevant. Mobile revolution? Never bothered to learn. Super fancy new JavaScript? Took me years to start looking into. Go? Ugh, don't wanna. Etc.

Ten years ago I was chomping at the bit to jump on any new technology that started showing signs of promise. Nowadays I focus on just solving people's business problems and printing money. Tech is a tool, not a goal.

This already makes my resume look a lot less shiny to keyword matching recruiters. The fact that I'm old/cynical enough to say "expected value of options is 0" makes me all but unemployable.
Have you actually done the math to show this works out in the long run?
Cadbury's chocolate now reminds me of the stuff I used to find in cheap advent calendars and low end pick 'n' mix.
They've done some decent optimizing in the last few releases. I'm finding it much more responsive than it used to be.
True. I taught myself C using vim + gcc under Linux. For those wondering what exactly you learn:

1. You learn the command line interface to your compiler, which is invaluable and something you'll have to learn at some point, even if you start off on an IDE.

2. Similarly you learn the command line interface to the compiler's support tools like make, linker, debugger, profiler, source code revision control, grep, strings and so on, and more importantly how the whole process of 'write-compile-execute-debug' cycle is done.
The Beasts That Keep the Beat
Frankly i see that kind of behavior spreading across the net in recent years.

I find myself thinking it started with Anonymous getting a bunch of press for similar antics. And over time other individuals and groups have adopted them to further their own goals.

Hell, some of it may well be organized as a kind of online cointelpro.
Always happy to see your username on threads discussing these matters!

I think you bring up an important point - your average 50 year old developer is much more likely to have spent the last 10 years at the same company, working with the same technology, maybe even with the same title, than the 35 year old developer.

Most of my experience has been .Net web application development in the northeast/mid-Atlantic. I think it'd be damn near impossible for me to get a job writing Ruby or Go for a startup at this point unless I made it a goal (it's definitely not) and spent considerable effort in my spare time working on projects. I'm only 29.

If you're a 52 year old developer who has spent 22 years writing RPG reports for AS/400s and you get laid off, you're either going to end up in doing the exact same job for another company, or you're going to be retiring.
My prediction for Basic Income is that even if it gets introduced a few years/decades later a lot of people will complain (rightfully or not) about all those parasites not doing anything while "job creators" have to pay for it. At least in the US it won't work long term looking at the current discussions about tax rates.
> 'I believe this'. So far he respects truth

What if he believes is objectively wrong?
> There is no intrinsic American cultural value to it

Of course not, Kraft Dinner is the national dish of Canada.
Make no mistake about it, this is clearly a marketing ploy by Kraft's ad agency. They are battling the minds of consumers who are (as of recent) continually seeing companies change ingredients and then be marketed to because it's "preservatives are bad...now with less preservatives!", with an undesirable side effect of "hmmm, but it tastes different". Coke Zero is a great example of this effect.

I'm not so sure Reddit's system is that similar. Reddit had a serious issue with search functionality not reaching the desired effect, and was easily circumvented by using Google search directly on reddit.

In reddit's case it was about completing a task and reaching a goal ("I now can search for something and it works"), for Kraft this is about perception and desire ("This tastes good!").
The Americans who’d benefit the most from online education don't know it exists
How to Get on the Social Map of Life Using SEO as Your Metaphor
It takes constant fighting to prompt saving a single species. Take a look at the https://en.wikipedia.org/wiki/Centrocercus for instance. They are endangered by husbandry and mineral mining which both have deep pockets. Most of the population isn't an issue. The Sage-grouse had a PBS special made out of it even. I think that makes a big difference to make a detailed documentary of the life cycle of endangered species.

Spreading the money out evenly would doom them all I bet.
I can definitely imagine that people might want to take advantage of modern technology while simultaneously wanting privacy protections.

I just can't imagine why they think that relying on a private company is the proper course of action.

I can also definitely imagine why thinking that public infrastructure or using free or open source software and hardware will lead to actions that will actually make a difference towards securing privacy protections.
Rust has macros, so boilerplate can be swept up pretty tidily. In the case of propagating up errors, there is the try! macro that encapsulates a match that returns early with the error
This is just part of the subterfuge; it's actually a different finger he doesn't use.