skysight-inc/HackerNews huggingface dataset:
I don't think you're be fair at all. Young people don't work more because they suck, they work more for a variety of reasons including: they aren't yet jaded or burned out, they don't know how to pace themselves, they have fewer family obligations, they are more excitable.

Second, no one has 20 years of relevant experience. Maybe computer science fundamentals have stayed about the same, but it was 1993 20 years ago, and what we do now looks nothing like what those of us who were around then were doing. Further, all those years of experience could have, and often do, entrench very bad habits. I've seen some atrocious code from people switching from older workhorse languages to more modern ones, it's not pretty.

Finally, /the data suggests/ homogeneity is valuable in early startups. You're not wrong about needing a team with different strengths, but you also need a team that really understands each other intuitively and agrees on fundamental values and principles. There's too much friction otherwise.
>>The Economics of Depression are called "Keynesian" - the set of tools, observations and policy proposals that are shown to work when in such a crisis. They are again fashionable with young stars in economics creating new Keynesian-expired models. All of the criticism of this "Depression economics" is usually valid during normal times, but this is an extraordinary event.

There is an entire (respected) school of economics that disagrees that Keynesian economics works. I'm not here to argue which side is right, since I am not an economist, but to simply state the Keynesian economics are the "Economics of Depression" and then dismiss the Austrians as a "joke" is ridiculous.

>>The talking heads and politicians never like stimulus - its use implies a different mode of the economy, its much easier to just continue talking as before. Debt isn't an issue, because stimulus from defence spending right before WWII was done with much bigger debt-to-GDP, inhereted from WWI in most countries that did it.

From what I have seen, this is pretty much the opposite of true. The Democratic Party in the US has been extremely pro-stimulus basically since Obama's election (your point about state level cuts negating its efficacy may be true, but that doesn't mean there isn't a large group of politicians that are pro-stimulus). Most of the talking heads I have seem pretty pro stimulus, and they definitely are anti-austerity.
Interesting in light of this discussion: https://news.ycombinator.com/item?id=6504331

But to trust that something like this to make a permanent copy of stuff I'm linking to, I'd need to know a bit more about them. Else this is effectively like using a link shortener -- a single point of failure.
Why does my personal (or intranet) webapp needs an internet connection to work?
Also, America is the only country that taxes overseas income. So the only other country where the tax status of the Nobel prize would be in doubt is Norway.
The issue isn't fact vs fiction, but that you're being extremely insensitive and using what's considered a derogatory term.
Bitcoin does have the ability to store this kind of information in the actual blockchain, but blockchain.info decided it was not worth the bloat.

http://bitcoin.stackexchange.com/questions/7864/is-a-public-...
So, at last count of criticisms our industry is ageist, sexist, able-ist and racist. Did I miss anything?
There is definitely a difference between writing nitpick reviews and writing negative reviews of a place based on legitimate issues. If you leave negative reviews complaining about finding a hair on the carpet then yeah good hosts probably aren't going to want someone who is that much of a nitpick.

But if you leave a review complaining about real issues like no towels, dirty sheets or bathroom then that's not going to hurt your chances with good hosts. Believe me I've left a bad review based on an Airbnb place being dirty, and I've left a neutrally toned review that complained about some minor issues like a slightly dangerous ladder leading up to the loft bed at once place I stayed at, and I don't have any issues getting great Airbnb places.
Unfortunately, the list of companies with the oldest workers -- IBM, Oracle, Dell, HP, among them -- would evoke eyerolls from most young hip tech workers today. What's Apple's median age?

Of all the big young tech companies, I would think that Google would be the one to benefit most from older, experienced employees (besides the group of all-stars it already has, such as Norvig)...Google's business encroaches on a lot of other domains, and domain knowledge is something that (usually) gets better with age. Perhaps in 5 to 10 years, there will be a bigger group of 40+ yr old professionals with enough tech experience/savvy to be more obvious assets to tech startups.
It's depressing how little money it takes to buy a politician. I would completely believe $40k. The AG isn't doing anything illegal, he has prosecutorial discretion. As we have more and more laws, more and more power is vested in him.
I know personally, I intend to create a company after I get experience from industry. I am a 21 year old college student, so that means ill be somewhere between 28-35 when I start a company. At which point I will probably higher younger for cheaper. Perhaps that is part of the reason those companies have such younger workers. Most Programmers either do consulting, start their own business, burnout, or change career paths by 30 based on the 20 or so I talked to.

I could be totally off, but from what I know and have seen this seems to be the trends.
What are you talking about? Kernel developers don't care about visual design - they write kernel code!
"A simple way of avoiding the above issue is to have a "personal" computer with personal accounts and activity, and a "work" computer, with work accounts and activity. Never use the work computer at home, and never use the home computer in the same place you use the work one. There's no way to confuse identities or traffic patterns."

The problem with this approach is that you need to never use the wrong computer for the wrong thing. You can help yourself somewhat by setting up different window colors / desktop backgrounds / etc, but what happens when you go visit your great aunt for thanksgiving and forget to pack both laptops? What happens when your work laptop breaks, and you desperately need to update the site to deal with some issue?

A more reliable approach would be to have one computer with two accounts (or if you like technically sophisticated approaches, use a mandatory ACL system), one for work one for personal things. Set up each account with noticeably different colors / themes, so that you are less likely to accidentally use the wrong account for the wrong thing. If you forget/damage your laptop, you have less of a temptation to use the wrong computer.

I am sure that Truecrypt fans will point out that hidden volumes work equally well, though the extra effort required is something of a stumbling block in my opinion (and I am not a big fan of hidden volumes to begin with).
Java as a language is not that great, but the alternatives are usually even worse:

- Python: slow, dynamic typing

- Scala: slow compilation, very complex syntax, worse tooling,

- C#: MS-centric (but other than that C# is superior to Java)
They work on completely different concepts:

Jekyll requires you to generate your site. Dropplets generates pages on each request.

Jekyll runs on your machine, and is written in Ruby. Dropplets runs on your server, and is written in PHP.

Jekyll's posts require very minimal metadata, and use a key/value pairing system with YAML. Dropplets' posts require a ton of metadata, and the same metadata for every post, and in a specific order, and you can't add arbitrary metadata.

----

I don't think Dropplets has categories, but I may be mistaken.
ES6 generators and iteration in spidermonkey
Things like this should be required when posting links in Stack Overflow and the like.
The Web at 20: What's in store over the next two decades?
There's a learn more button...
Clojure's Java interoperability is better than Scala's. For example, Java collections are automatically treated as Clojure collections with no wrapping required, any Iterable is a seq etc.
Young people work for less money because they are inexperienced. The older worker has to provide the same value for their higher pay via experience. And this is where the problem comes into play: the potential employer might not see the older worker as being worth it, especially if it doesn't appear that they can do more than the younger worker. They might also see potential (room for growth) in the younger candidate that they can't see in older ones. And this is all quite reasonable....also remember that most companies are pyramids, with lots of openings in the bottom and much fewer as you go up....

So you as the tech employee must be aware that your life is short if you don't continuously grow your skills so you don't become an unjustifiable expense later in life. Not only that, but you have to become an expert in marketing these skills.
Hey creator here, we realize there is a bit of a trust issue, thats why we have the paid plans. Our costs are low enough that, even if you were our only paying customer left we would be able to keep the service running just for you.
I think one of the reasons Jon manages to pull it off so well is how basic it is. He has a 100% custom sidebar (very basic), but other than that he is using native menu controls and standard dialogs. Obviously the editor pane is the big custom component.
This is a saturated field, as others said. But there's room for a competitor here. I would focus on the main social networks integration: Facebook, Twitter, and maybe maybe Pinterest. Everything else, including Mailchimp is overengineering.

Also I left a comment just now on your site. I wonder if it's possible to get all the Twitter oauth tokens when people enter through Twitter?
It is powered by PHP. They probably feel ashamed as they don't say it anywhere on the webpage ;-) Seems nice tough!
Not exactly. There aren't pages, and posts are written in your text editor, and the files are "dropped" into the admin section.
Twitter is hiding two years of financial data
The other problem is learning as you go. It seems like some of his mistakes were in the very early days of the site, and they were uncorrectable due to Google caches and such.
CEO of Pebble on how he'll survive Apple's iWatch
Great closing line: "Avoid ageism. It isn’t rocket science. Even when it is."
Building Websites for Charity: Marathon Fundraising
That's true of any flat-file system... But, I agree.
The concept and simplicity make me think of Ghost's (http://ghost.org/features/): free, open source, near-minimalist, and self-hosted.

The seemingly only advantage is that Dropplets doesn't require a database, and its landing page is amazingly beautiful, clear, and to the point (though Ghost's "features" page is slick as well).

On a more technical note, click events seem to be propagated up the player on the landing page, closing it when toggling HD for example.
It's not quite as capable as the original, but I've put together a Sublime-like editor running as a Chrome app, because I thought it was ridiculous to have to run Vim in a chroot just to do some editing. I'd love to get feedback from any developers working on Chrome OS: https://chrome.google.com/webstore/detail/caret/fljalecfjcio...
I'm getting on the old side of the average, approaching 40. But in my experience I've never seen a startup founder tell me that I or anyone else was too old. Mainly because the industry really is a meritocracy and it's about what a person can do now, usually. Fortunately for me most juniors don't know all my tricks just yet.

I will say this though - I have to constantly step my game up to stay relevant. At 50 I will be expected to not only know programming very well, but the industry as a whole including analysis, planning, finances, management, etc.
On the other hand my father has been consistently using his Apple TV non-stop since last christmas. I didn't even have to instruct him on how to use it aside from a 5 minute intro course.

I've heard similar rave reviews from 3 people over 60 about how great the Apple TV is. None of which I would position as tech-savvy.
Tips for Those Who Want to Build Products on Their Own
When you hire cheap indian/pakistani programmer through some * lance *.com site - without knowing it, in many cases you'll be paying rock bottom rate for middleman who pays less than half of it to actual programmer.

Welcome to the cost "efficient" world of outsourcing!

http://toprate.org/FILES/programmers.jpg
One point to note is that a DMCA takedown targeted at Mummify.it will remove the content just as it would from the nytimes.com.

If I manually save that content to disk then any DMCA take down doesn't affect the content stored on my local hard disk.
It would legitimize the (uncontroversial) assertion that cars have worth.
and if Mummify goes down...

Would it be a better option if the "permanents" were shared across p2p/bittorrent and every unique item had at least 10 shares distributed across the globe, maybe a max of 20. When one share host goes down, it just picks up a replacement.
Let's centralise the interwebs!

It seems like a bad idea, but they do have a point. Maybe when referencing a link also make a small note to one of these archive sites?
But, Dropplets doesn't have a built in post editor, and requires that your posts contain lots of required metadata, and in a really arbitrary order.
I like working with Java too. I'm only pointing out the problems, which I see are pretty clear.

The only problem is from the perspective of using and developing a new skill, I would rather use a newer language which is better built for problems of our time than something 20 years back.

Java has had its day in the sun. Its primary purpose was to become an easy C++ for people who didn't get memory management and people who didn't want to get into tiny pedantic issues while trying to run their code on two different Unix'es. But these are by and large solved problems now. Over years a lot of legacy code has gathered around Java.

But if you want better employability especially if you want to work on new projects, new paradigms and new domains of problems you should likely chose newer set of languages. Not Java.

One hard lesson that I've learned over the years is to never have any hard religious feelings towards old aging tools. We must learn to move on, find new shores build new stuff there. The only projects you get with these older tools are legacy ones, and people are generally waiting just to phase them out.
I hope you are consistent and feel the same about the peace prize to Kissinger
Inflection points in technology open up opportunities for new competition once a mega company has won a space.

It's a fool's errand to try to beat Google at the game they've perfected and were built for. By the time you could very slowly wrest control of search from Google, the whole tech world will have changed and your point of competition will no longer matter. That's the foolishness of Bing, for example. It's great that companies still try to compete with them, but all they will accomplish is to keep making Google better (and that's a good thing for consumers); they won't 'beat' them however under any circumstances.

Google will be beat in search the same way Microsoft was in operating systems: a dramatic sea shift in technology (with Android now being by far the most important operating system going forward).
Marc Andreessen: The world is going to see an explosion of countries
The weight of words: designers should always work with copywriters
Over the years, I had several bad experiences with outsourcing to big companies in India. But recently I had a discussion with an Indian colleague. She used to work for a company for which my previous company outsourced to. She told me most of workers there are just out of school or the rest are bad programmers. Good programmers find quickly a job in better paid positions in other companies.

It seems the main issue is deciders in the west are happy to find cheap outsourcing companies in India. Their pick goes to the company with the lowest hourly rate. What they don't realize is that the good programmers move very fast in better paid position elsewhere... letting you work with the less qualified people.
"They're not stupid ... they're demotivated"

Maybe ... or their incentives aren't aligned with yours? We used several different Indian out-sourcing shops at various points and if there was the slightest ambiguity in a specification (and how do you write one without any ambiguities?), they would (purposely?) do what you'd least expect. As a contract programming shop, this led to the most billable hours.

We later purchased an a company that included an in-house division in Bangalore. These programmers were therefore employees of the same company that I was and therefore motivated by the same factors (successful projects meant more work ... unsuccessful projects meant looking for another job). In general, the in-house Indian programmers were competent other than slightly inflated grades (a lead JavaEE programmer with 2 years of experience?).

So from my experience, there are some brilliant Indian programmers, and some worthless ones, with the vast majority falling in the middle ... just like here.

P.S. I'm in the US, but I imagine that "here" is valid for many values.
As a Java fan I claim that Java is the best choice for lots of projects. What other language has:

- amazing tooling

- static typing

- great performance

- huge amount of libraries available

- multiplatformity

?
That's a good point. I think one of the reasons Sublime works so well is because the interaction is minimal and unobtrusive. You don't realise how simple the controls are - as you said; standard dialogs etc.
I've been using JUCE for a couple of years for VST development. I've found it to be a very well put together library for audio work (diving straight into Steinberg's SDK is pretty daunting for someone new to audio like myself), and a lot just works out of the box.

There is strong leadership from Jules on the direction of the library which is generally a very good thing, though it does mean that sometimes there isn't much room to budge on controversial issues. Font rendering is one aspect that several have battled with for a while, I've struggled to get good crisp smaller fonts without resorting to using freetype. Jules argument seems to be that small fonts shouldn't be used period, therefore the library wont render them well (I think there are technical as well as philosophical reasons for this, particularly on OSX). While I agree they should generally be avoided, there are certain situations where this isn't the case (reproducing an exiting GUI for a client, fitting non-critical text in when screen real estate is at a premium etc).

Overall I would certainly recommend for anyone starting out in audio development, but be prepared to fiddle around with fonts; I'm not so familiar with the non-audio parts of the library.
#1 It is crazy and I see a toolbar on just about any average user computer. However, most people do not explicitly install them. They're being silently opted-in or gently coerced into it.

#2 and #3 Google is so influential that it's highly unlikely to happen on the current playfield. They either buy a potential competitor out or cripple their business. I can only see two opportunities for this: a) specialized niche search, b) search based on a new disruptive technology.
In terms om symmetric ciphers we know of two chinese ones: sms4 and zuc. The latter has also been accepted as standard by 3GPP (SAGE).

https://en.wikipedia.org/wiki/SMS4

https://en.wikipedia.org/wiki/Zuc_stream_cipher

Not sure why anybody would want to use them or the GOST standards unless required/forced to do so.
It's not an ageism problem, it's a loyalty and perception problem. Old people by their nature cling to institutions of loyalty and start-ups are definitely not known for staying around for +3 years.

Furthermore start-ups also implicitly prefer "just good enough" in order to get your company up and flying enough to quickly accrue investor interest, whereas stability forms the bottom-line of our elder engineers -- and stable systems require far more time than some investors are comfortable with.

Even worse, there is the management aspect. Older people have very different management styles, and throwing caution to the wind is definitely not among their managerial toolset. If your company has older people in positions of power then it definitely scares vast swaths of people away -- from eager investors looking to turn a quick buck and energetic young engineers looking to for autonomy to work without anyone second-guessing their decisions.

Finally, the saying "old is gold" applies quite well, however that gold needs regular polish to remain shining.
We can't completely blame the customer. The competition is quite high and it is easy for anyone not familiar with programming (most of the clients) to get attracted towards cheapest option.

Not to forget that such companies/people often market themselves as jack of all trades and it is hard for customer to see any real difference developers asking for $200/hour and $20/hour when $20 guy is promising everything!
Unfortunately, paying someone well does not necessarily mean you're going to end up quality either.
You can't customize 1000s of emails. Sure you can mail merge in their name, but putting their name in the first line is not customizing.

Customizing would be looking up information about their company, researching their competitors, talking to people who know them, figuring out what kind of food they like, and then crafting an email to them. That is not spam. That is hustle and marketing.
> They are also more likely to be dumber and lacking in versatility.

I think you mean 'naive' or 'inexperienced'. Stupidity ('dumb' isn't PC, but nobody seems to care anyway) is generally thought of as something inherent.
Can the Internet save energy?
#noEstimates Debunked
I wasn't able to find anything in there that is specifically about fracking.
Yes, it's a good thing however I don't think that it's going to be "reversing" any time soon.

As stated above, the intrinsic problems haven't been addressed at all.

Not sure what the population at retirement age is going to do. My parents are semi-retired e.g. laid (sic) off. My dad is 72 and still looking for work.

Icing on the cake: the stupendous amount of debt owed by college grads.
You might find something on http://staticgen.com/
Plus, there's not even a configuration/preferences screen. It's all text. So, no gui widgets needed.
One of my favorite tricks not often used: -XX:MaxTenuringThreshold=0

Higher throughput when you have lots of short lived objects.
It's not the boss who paid $20 / hour who is moaning here. It's the guy who he brought in afterwards to clean it up.
I'm a programmer from India. Here its more of quantity vs quality. We have a ton of programmers, but really small number of good ones. Most of us come into this field not for the love of programming, but for an "onsite opportunity".
The reality for older developer is that you are going to have to:

1) Move to management to continue advancing

2) Find one of the very few large to midsize companies that has a long-term developer career track comparable to their executive track

3) Start you own thing and exploit the fact that you are more productive than younger developers, and control the purse strings

Large and even mid-size and event ostensibly tech companies still, for the most part, view developers as an R&D cost center. They look at cheap development resources, either young kids or foreign, and think "For the price of 1 developer, I could have 10!"

Now they have 2^10 problems.