skysight-inc/HackerNews huggingface dataset:
I just turned 36, and I am in a contemplative self battle with this very question for my own career. As far as internal career development goes for my current employment, I have "succeeded". I have had a slew of successful projects and have been slowly but surely moving up the chain. It's difficult because in a large firm (20k global employees), moving up means coding less and attending more meetings. This is starting to drive me mad. I know that I can only go so far as an engineer in a large firm, but I don't want to just coalesce into the larger bloat that churns out hours and hours of meetings and powerpoint. On this path, in 5 years, I will be a director of some department and my distance from the code will be far. One way I am coping is by continuing this management ascension and writing code on the side - but when I have kids in the next couple years I probably wont have much time for that. It is a difficult decision to be sure.
"When we started doing a lot of interviews"

Bingo! Only megacorps and people who hire noobs recruit that way. Beyond a couple years its all ... "That guy I worked with who was an expert with statistics (by their standards)" or "That guy with the awesome github repos" or "That guy I contracted with once..."

And looking at his graph, I'm guessing his job description is skewed toward noobs. Something about the company, or the job descript, or working conditions or ...
If you're on a feature branch, you can probably commit often, and push often (effectively backing up your work), then, the isolated unit of work is done on a single commit (non-FF) when merging with the main branch (this is the one you search for when you want to revert something or find the culprit for something).

This allows having "best of both worlds", I think.

EDIT: Take a look at the feature branches on the git flow model: http://nvie.com/posts/a-successful-git-branching-model/
This was by far the most amazing lecture yet. Practical, actionable, and concise. Major kudos to Kevin Hale; this has helped me so much.
Y U NO write this for other editors?
If the concern is the computer failing, you should do backups. And it's probably simpler to use automated backups than using git push as a backup mechanism.
Why is tech being singled out?

Because tech is wealthy, visible, and weak. This makes tech an easy source of symbolic and financial victories for those who wish to wage a culture war.

The real question is why tech rolls over rather than fight back. (There are a few noble exceptions, e.g. Uber, Tesla and AirBnB, but they usually only fight back within their narrow battlezones rather than in general.)
They go where you went Oren - they end up running their own company or running a group of devs or a product inside of a larger company.
As of mid-2013 they had five fab customers [1]: Achronix, Tabula, Netronome, Microsemi, and Altera.

[1] http://www.oregonlive.com/silicon-forest/index.ssf/2013/07/i...
Well, you're not gonna target the drones. You'll want to destroy the enemy's ability to control those drones, or their ability to build and maintain them.

Or, more realistically/cynically, you want to PRETEND that's what you're doing, when you're actually targeting major population centers in order to terrorize the enemy into surrendering (as used in WW2 by the USA against Japan, Japan against China, Germany and Britain against each other, etc...)

And simply disengaging when you decide you've had enough is a luxury that the USA and USSR have enjoyed in their proxy wars. Americans haven't had to defend their homeland in over 200 years now, and it seems a very skewed view of the horrors of war resulted from that. If war is nothing but a drain on resources to you, you're not so much fighting as you are trying to mug someone who can't really fight back.
https://en.wikipedia.org/wiki/Fellow
The Dyson humidifier cleans your air with ultraviolet light
Negative online reviews can lead to threats of legal action
> Rather read works by people who are creating for the sake of art, and not money.

So basically the independently wealthy.
I guess professional programmers has this sort of thing already sorted out, but it happens all to often to reach the point where my new feature is working as it should (appears to be stable), and I keep working on yet another addition on the same branch. When I commit, I feel like I should have committed at least 2 or 3 times by now.

Happens too often so I setup up this plugin from 20 to 10 and see how it goes! But thanks, the idea is really handy.
/dev/burnout :(
can this be turned off ?
And yet they still do ~$100 billion in business per year. About 12.5 times the amount Facebook does, a company that can claim something like 1 out of every 6 people on the planet as a user.

They also employ 431,000 people, or about 61 times the number of people Facebook keeps alive in the global economy.
I found the Forbes article unconvincing, especially this bit:

> applying the same strictures to Standard Oil would have left that company alone rather than breaking it up. And that’s a conclusion that I’m entirely happy with too.

So it would have been fine far Standard Oil to take over the entire US economy as long as it reduced prices far consumers?
Blue17 – For the Best Mens and Womens Vintage Clothing
Same. iCloud has worked perfectly fine for me. My experience has been pretty close to the "It Just Works" that Apple strives for.
Show HN: Golgi: Google Maps for the brain and connectome
You should work for a tech company (i.e. those companies that solely focus on tech). Most usually have clear career paths for those who want to become senior individual contributors vs. managers, because that is actually very useful.
It looks like Hachette's PR department has stepped up a gear. This subject has been covered several times before and I think this comment [1] did a good job of explaining Hachette and Amazon's positions. To summarise:

When Hachette's contract with Amazon expired, Amazon (rightfully) stopped ordering advance inventory for stocking, but continued taking orders for available titles and transmitted those orders to Hachette as they arrived. From there, it's Hachette's responsibility to deliver the orders to an Amazon distribution center. Once the books arrive, Amazon packs & ships them to purchasing customers as normal.

That's why, when Hachette's contract expired, all of their books were listed as "Out of stock: ships in 1 to 6 weeks" - that's how long it takes Hachette to deliver stock. That's slow as hell.

Amazon didn't "boycott" or "drop" or "betray" authors or "discourage" readers from buying their books - it ceased offering retail inventory management services to a supplier whose contract had expired, and made a rational and defensible business decision when it became clear that the supplier was not negotiating in good faith to establish a new agreement.

[1] https://news.ycombinator.com/item?id=8151181#up_8151480
It prompts every 20 writes (i.e. saves), not lines modified.
Build & installation from scratch is far too complex. Relies on fortran libraries of numpy which I can't get built inside my corporate domain
This concept isn't strange at all, you're simply making the mistake of thinking that the pool of developers shrinks when it gets old, when the opposite is true.

"new" programmers, the ruby devs, the python aficionados and the PHP gods are becoming increasingly common.. we're at a golden age where it seems a large percentage of our generation is doing some kind of dev work- larger than any proportion of people in history.

it shouldn't be surprising that people with 20 years experience aren't common because not many people comparatively were vested in the industry 20 years ago.
Actually, a glorified save is exactly what a git commit is. I literally have a command that (haskell) compiles and commits everything if it compiled. I sort it out into sensible commits later.
First, assault & battery are misdemeanors. They are punishable by up to a year in prison, and maximum sentences are rare.

Second, violence is not acceptable as punishment, but it is acceptable (often necessary) in defense of self and others. If people are fighting, it's fine to break them up. That said, I doubt a larger adult needs to resort to blows to stop two kids fighting.

Third, there are plenty of punishments that don't involve hitting. It's common to restrict access to TV or games. If all else fails, there's the dreaded, "No phone for a week."
The Minimum Amount of Money to Become an Apple Developer
"Do we all _have_ to become managers?"

Who would we manage, if per the article their average future employee only has 2 yrs experience and I have about half a century of working life. So the average bottom layer of the pyramid programmer will end up reporting to roughly twenty five ex-programmer managers simultaneously.

Or rephrased, 24 out of 25 programmers "must" find work elsewhere every two years or so, to keep the numbers reasonable.

"tucked away in major corps"

That's where I am. Work to live, not live to work, great benefits, nice working environment, nice coworkers, but if I want a promotion pretty much ten people would have to quit or die of old age first. This "being pushed into management" stuff from coasties sounds really weird to non-coastie ears. Or having a "career" sounds weird, since I've had the same job for decades and have no realistic hope of title advancement, and I'm perfectly OK with that.
I can't see this as a problem. Let the market decide. Probably my treasured reading is your rubbish and just possibly, vice versa.
What's to stop them from selling it to each other? Could we see a completely stratified economy, with rich people selling each other the fruits of their automated factories' labour?
I think this story is a really good object lesson for the typical HN reader that there are mind-bogglingly huge businesses out there and they don't operate like startups.

IBM employees 61x the number of people as Facebook and makes almost 13x as much revenue.

If you can't figure out why IBM works and what it does, you need to keep studying how businesses work because you'll only ever understand small startups and be missing out on a big picture.

Even if all you ever want to work in are small startups, knowing how big businesses think can be really important to getting your company sold to one of them.
To get a programming job that can actually use 10+ years of experience, you need to develop strong interpersonal skills and (to put a darker shade on it) learn some CS 666: Software Politics. At that point, the main obstacle to moving into management (needing to bring your interpersonal skills up to, at least, the 25th percentile) is gone.

In other words, if you're good enough at interpersonal politics to keep improving as a developer past the 5-year mark (which requires working people well enough to get on the best projects) then you're also good enough to move into management.

Moving into management is also just plain easier than protecting a specialty against the anti-intellectualism of business-driven engineering. You're a top-flight developer making $140k with a well-formed specialty (let's say that it's machine learning in Haskell). Your options are: (a) compete for the two jobs that exist in the world, (b) give up your specialty and move to a hedge fund, or (c) move into management, which tends to be specialty-agnostic, and lucrative. If you've decided that you're a manager from here on out, all those damn Java shops become options again.

Startups were supposed to provide an alternative, but these days the VCs act like bosses and being a funded CEO is a middle management position.

For what it's worth, the genuinely interesting fields of programming tend not to have the same age-related attrition. Machine learning researchers, and even serious engineers like Jeff Dean, are just starting up when they're 40. However, the business-driven engineering that 95% of us have to contend with is mind-rotting. Spending a week debugging someone else's VibratorVisitorFactory method, or figuring out what the fuck some ORM is doing, just causes atrophy.

We have age-related attrition (of both kinds; our most talented leave, and our less talented or just less lucky are punted) because we're a badly organized industry. We have a talent for which there's nearly unlimited demand, and yet we refuse to organize around protecting its interests with a union or a professional guild.

Also, organizations that use a "dual track" only underline the problem. Take Google. It's 100 times harder to become a Principal Engineer (Director-equivalent) than to hop on to the management ladder and make Director. It's 10,000 times harder to become a Google Fellow (VP-equivalent) than to make VP. There may be a noble intention behind dual track organizations, but their actual effect is to show how stacked the deck is against lifelong individual contributors in a world that is still "manage or be managed".
> About this Mac

When the user selects 'About this Mac' from the Apple menu, Yosemite phones home and s_vi, a unique analytics identifier, is included in the request. (si_vi is used by Adobe/Omniture's analytics software).

Wow. I am waiting for "Team Apple" to invent a radical defense on this one. But regardless this is shameful on Apple's part.
Loved the game. There is one level where you have to push 4 buttons to open barriers. But 1 player if fast enough can push 3 of them and you get glitched through last one. So I was trying to get one cursor through, clicking every button 5 times, but I was just a bit too slow. Then he just came to my place and wiggled "hey move on its my turn to help". He was fast enough and I moved on...
If you want to use OS X, you need to play by Apple's runes. If you want to use some kind of Unix-like system, you don't need to play by Canonical's rules. There's a myriad of Linux distribution, not only Ubuntu, and then there are the BSDs too.
But that's missing the point. There's still plenty of places where it's hard to impossible to eat _healthily_ in the U.S. Yes, we've won the calorific scarcity battle, but regarding obesity as self-inflicted lacks nuance at best and victim blames the poor and disadvantaged at worst.

http://en.wikipedia.org/wiki/Food_desert#Barriers_and_propos...
I much prefer our ascii art doge when all tests pass. :)
> This makes me feel that the new focus on privacy from Apple is more for PR purpose than something they really care for.

It may well be something that some parts of the organisation care about, but clearly it is not something that the UX people designing the settings applets care about (assuming such people exist; for a company generally very good at UI and UX, Apple tends to have very confusing settings stuff).
no - I'm suggesting both situations are equally unpleasant for users and HN crowd tends to absolve Apple for any 'crimes' they commit - it's just funny

(I'm using both Ubuntu and Mac on a regular basis)
> It's common to restrict access to TV or games. If all else fails, there's the dreaded, "No phone for a week."

Except, of course, if you're limiting the TV anyways, and you don't allow kids to have (smart-)phones.

In general, I agree, there are other kinds of punishment, but they might sometimes not be effective. Then what?
You would need to move it (or the print) on the z-axis as well. And printer heads are usually quite big and heavy, I'm not sure if they can get small enough for this.
You forgot:

3) People with 10+ years experience generally don't go out looking for work and applying for interviews. By then you have enough connections that if you want to change job, you'll find it through old colleagues. Not by shopping around like younger devs. This applies to most all professional occupations, not just Software Engineering. If you look at people applying for positions in economics / law you'll see a similar graph.
> Compiler enforced static typing rejects many correct programs, which is a disadvantage.

In practice, however, it is only a theoretical disadvantage. The kind of "correct" programs that get rejected are not very useful.
Absolutely true. As a user, I have never had any problems using iCloud.
I don't think the remaining problems are self incflicted. That's kind of the whole point. If these problems are systematic they might be even harder to solve, and then we haven't gotten closer to the eventual goal (except for the mentioned stock price of course).
You can really have two "species" of commits:

One of them is the "published, shared" kind; for this one, I can agree with you, that they should be self-contained and complete, especially when there many devs on the project, and/or you'd like to be able to use bisect.

The second kind, and for me actually a very important one, is more of a "local backup, dirty hacking" one. Those shouldn't probably be published (unless a private/one-guy repo), but allow for easy hacking, developing, testing, experimenting. The "commit often, whatever you have, however broken or non-ideal" approach provides safe lightweight backup, and allows for easy switching between various paths/approaches. Now, after you design stabilizes, dust settles down, and you are completing the work, you can (and probably should) eventually either just squash everything into one final feature commit (the end result will be indistinguishable to what you'd deliver if not committing in the meantime), or remodel the intermediary commits to whatever ideal shape you like them to have retroactively (with "git rebase -i", including patch editing etc.) Knowing the benefits of this approach, I don't understand why anyone would want to reject it.

edit: Also, with many small, dirty commits, it's sometimes possible to fairly quickly do stuff like carving out some subfeature into a separate branch (with judicious use of rebases, cherrypicking and some occasional small edits). Or, remove/revert commits marked earlier as DEBUG. Seems useful to me, as a means to somewhat speed up such operations and decrease the possibility of manual error at the same time.
I remember a friend of mine complaining about getting his program to sync using iCloud, he said it was complicated but very solid.

He would commonly submit his application to the store and get critical feedback and very helpful comments on why it wouldn't work, what wouldn't work and in one case an architectural issue that could have caused duplication.

As a consumer, I've never had any applications fail to use iCloud effectively, everything I use that actually leverages iCloud (and not dropbox or $proprietary_syncing_method) just works wonderfully and predictibly.

the authors actual gripe seems to be from the developer who has not submitted a fully working version of his program.

I would ask him what specifically makes him think that it's the device causing the issue.. maybe add a contact through the webUI and see if it syncs, or modify data with another application that uses iCloud.

>Obviously I’m using more apps than just MindNode.

which apps, have they been updated recently? iCloud API's have changed in iOS8

Diagnostics is super simple stuff, don't blame everything before at least looking into the issue.
Data Science in Action: Unlocking the Power of Recommender Systems
I think that this is somewhat correct. Obviously, I don't have the evidence and haven't done the research he has done (over 800 footnotes - how many sources?!).

I do however think it could be more nuanced than what he says - it may just be that the bureaucracy changes course much more slowly than the presidency or congress or state governments change - so it takes much more time for those institutions to truly catch up with the public sentiment.

Of course, once the bureaucracy begins to actively fight changing with public sentiment is when the problems begin. Those institutions that do should probably be "reset", i.e. disbanded and reformed with a better founding base.
Bank of England payment system crashes
The main problem is the large (multi-megabytes) runtime that Rust currently is forced to load by default. This is disappearing.
Some insurance companies do this too, using UA as a variable in determining risk.
I would typically commit at the end of the day, even if it is into my private repository. So days, I think it as backup, but on other days, I use it to socialise the code.

I find that this forces me to take stock of the current state of implementation and put my mind in the right mind frame for the next stage.

When pushing it into the main repository, it will be a unit of work.
It's not a moral judgement, rather an observation of a common trait.
The new iCloud APIs are a lot less magic-oriented, and lower level, than the Core Data syncing thing, so hopefully we should see improvements.
The barrier to entry against the Kindle that is on my bedside cabinet and many others is virtually impossible to remove.

Amazon offer a painless way of adding books to the device. Buying a book takes seconds and it magically appears on the front page of the device waiting to be read. Its one reason why book piracy didn't go as insane as music piracy, the means of adding books was easier than the device
Are you completely blind to what I am saying?

I was responding to someone who phrased their comment that suggested they had installed ubuntu a number of times; not exactly the behaviour of a naif. I also commented that since we were talking about time, the ubuntu version compared favourably against the Apple find-in-two-spots version. Also, if you want to talk about the general behaviour of tech naives, they don't reinstall their systems every year, not by a long shot. I've worked in tech support in some form or other most of my life, whether it's family, school, medical equipment, office support, whatever. Your idea that the general computer user changes their operating systems every year (or two) is pure nonsense. OSX is the best to come along in that regard, and that's because they do in-machine updates. There are still tons of people on XP, which was superseded eight years ago.

Hell, if you want to talk about the behaviour of tech naives, at least with the ubuntu issue, it's clear and obvious that something distasteful is going on. With the Apple issue, the naives aren't going to be even vaguely aware.

Sod the strawman you built up around me; in both my comments I was referring explicitly to an experienced user. But no, you frame me as dismissive of tech naifs... while painting the use-case of a person who is a power user. Perhaps Crowley has been whispering in your ear?
Is Google Gaming the Video Game Industry?
Marc Andreessen Leaving EBay Board as PayPal Separated
I thought this was about ethics in game journalism? I can't imagine why you'd still be talking about Zoe Quinn. After all, she wasn't involved in anything remotely resembling "journalistic corruption". [1]

I also think that taking the words of an ex at face value is something very different from "her own words".

[1] http://www.washingtonpost.com/news/the-intersect/wp/2014/10/...
Separate, unfortunately for your wallet... This one's a proper 3DS application, whereas Petit Computer is a DSi application that was carried over to the 3DS eShop.

That being said, I don't think the new version will run programs made in Petit Computer as is without a fair bit of tweaking, so you do have the benefit of being able to try out the Petit Computer programs already made. It's not a complete waste!
You have misunderstood me.

I know cabal - with and without sandbox. I said am amazed that sandboxes or nix tools are necessary in Haskell _at all_ while every other language which uses a package manager has one that works out of the box without any hassle and without any sandbox tricks.

> Nix and NixOS are two completely unrelated projects, that not even be recommendable in a development environment.

Other Haskell developers don't agree. They prefer nix even over cabal sandboxes. Quote: "Nix helps me avoid Cabal hell" and "Nix is much better than cabal sandbox".

https://ocharles.org.uk/blog/posts/2014-02-04-how-i-develop-...
I suspect this gets bumped up more for meme-compliance than novelty. I rather like the SublimeText plugin, gitgutters[1].

But it in any case, I'm a fan of VCS integration in my editor.

1. https://github.com/jisaacks/GitGutter