skysight-inc/HackerNews huggingface dataset:
When she sold off printing and spun out Agilent, what were the results? If they did better on their own then with HP, then that was a smart move, even if "HP" as a company was diminished. If she sold them for cash and invested that poorly, then that was not a smart move.
I think the methodology of Koutnik's argument is defensible, but not necessarily reflective of the actual decision most people go through to work that 40th-80th marginal hour.

As others have noted, equity helps with recruiting...especially when the employer provides a handy "illustrative" table of how much that 0.5% slice will be worth, fully vested, at a variety of valuations. Once people sign the dotted line and are full-time employees, however, I think the following is a more accurate depiction of how people think through the "work over weekend" decision:

- Will refusal get me fired or decrease my opportunities to work on things that are important to this company?

- If so, how bad are those outcomes? If you haven't even hit your vesting cliff, leaving feels like it would be pretty bad -- both for the loss of shares and for how it'll look on your CV -- not gonna be fun fielding questions about why you left Wuzz.ly after only seven months when you're interviewing for either a new job or funding for your own venture.

In addition to the gravitational effects on one's psyche of anticipating financial loss and unpleasant future conversations, there's something else at play: many young engineers (not all, but many) have never experienced anything approximating real, painful failure -- and are terrified of it. They've glided from top of their high school class to StanCalMIT Mellon, have been wooed by multiple employers at several points in their still-young lives, and have inferred from that experience that if a job doesn't work out, they've done something wrong. This aversion to "staining the white tuxedo", as Conan O'Brien once put it, ultimately holds back their potential.
It depends and usually it's a good idea to check with the manufacturer.
THERE'S STILL TIME
Thank you. Pretty shoddy on Wired's part.

We've updated the title. We can update it again if there's a better one.
The point Adrian was trying to drive home is that for any quantifiable skill we can measure we find that there is a bell-curve across candidates. The over-whelming majority of people are average in every human endeavor that we can accurately measure in this way. The theory goes that software development is not different.

If we assume that the bell-curve is likely to exist then it's probable that only a handful of people exist in this current generation who are at the far-end of the curve. If the success or failure of an organization involved in developing software is dependent on the talent of its people alone then I'd rather speculate on futures.

If there is such a thing as the Mozart-of-programming you can't expect to hire a whole team of Mozarts. Any policy to only hire the best available programmers is upholding a culture of egotism and hubris. It's just not probable.

I've only seen this belief propagated by people who are more concerned with being better than everyone else. It's convenient that their finger only seems to point outwards. I don't like working with people whose sole talent is the ability to recognize the lack thereof in everyone else but themselves.
Every implementation needs a differentiating factor. AWS is its flexibility and ridiculous amount of built-in functionality - message queues, databases, DNS, storage, map reduce, etc. Azure moving from one-click deploy to the cloud to one-click deploy to your own cloud is amazing. It's the primary appeal of OpenStack for me.

The real question will be what will this take? If I have to put Windows Server 20xx on my hardware to run the fabric, I'm out.
A cycle from say 70% to 80% doesn't wear it out much at all.

The problem with leaving it at 100% is that just sitting at full charge wears it out, it's better to just keep it within 40%-80% than to leave it fully charged.
As I sit and look at the replies already coming in, may I just add an enormous [citation needed] to the entire discussion? A question brought on by too many conflicting anecdotes can not be resolved by throwing another unsourced anecdote on the pile.

(Incidentally, I'm at least a bit curious myself as to the answer, and have my own pile of conflicting anecdotes I've read.)
This is a subject that is pretty close to my heart, and which I think extends beyond demeanor. I witness on a near-daily basis conversations turning into heated arguments simply because the protagonists fail to see beyond their own perspectives and convey their own inadequately. Quite often, it seems, the points brought forward by the "opposing" party are largely ignored, the arguments are no longer about who/what is right, but about who wins. You therefore end up with conversations where the two parties are in fact talking about the same thing, but are so caught up in their own narrative that instict (System 1) takes over. Alternatively, people may be talking about completely different things and fail to realize they're doing so, effectively and unknowningly arguing in a vacuum, where loudness and displays of anger are more often than not the deciding factors. In both instances, this often results in disgruntled people and feelings being blown out of proportion. One only needs to look at political debates to see what I'm referring to.

On a lighter note, and hopefully providing more positive (anecdotal) examples than the article provides, signalling can be a very powerful tool too, even when mixed. It seems I have one of those faces that instills trust; quite regularly, completely random people will smile at me, say hello or even engage in conversation. Similarly, I'll be, say, on a bus and transport inspectors will get on and check everybody's tickets, except mine. They will look at me, smile at me, and completely ignore whether I do have a ticket. This sort of thing happens to me so regularly that I'm not even sure what to make of it, though it is definitely nice.
These three, but for me I'd put cash on equal footing with the other two. I personally value my freedom over cash once I'm making enough to feed my family's needs.
Normally I would support libertarian attitude, but in that case it seems like a pretty reasonable Governor was elected by people, precisely because these people wanted these particular strokes of the pen, instating reasonable control over access to common resource. Democracy at work.

Attitude "...If I’m an overlying landowner, I have the right to pump as much water as I can..." leads only to the tragedy of the commons and ensuing disaster...
Ask them about their vacation policy, and specifically ask your interviewer when was the last time they took a vacation 1 week or longer.

Ask if they're remote friendly.

Ask what their sick policy is.

Ask what their company does to make the world a better place. It's fine if they don't have an answer, some entities exist just to make money without any other "mission", it's just good to know.
Production of water inefficient crops would shift to states with water, Cali famers would shift to more efficient crops.

The US is a big country, there's no need to grow almonds in the desert.
Only saw your comment today, thanks so much for this, I really overlooked this part from the docs.
Explore / Exploit – Life Is a Bandit Problem
Patent US6007232 – Calculating the average of two integer numbers
I think Microsoft has realized that their 'our way or the highway' approach only works for as long as the highway doesn't offer anything you need.

The fact that Azure can be used solely to deploy Linux VMs, for example, is appealing, and I've heard a lot of good things about it from iOS/Android developers who've used it.
I love fries with mayonnaise !
Some of those costs can be minimized by installing fiber while other utilities and maintenance operations are being performed. Some cities have adopted a "dig once" policy for this, saying every time there is a dig then fiber must also be installed if it is not already in that location.

I would also be surprised if a city like New York didn't already have a fair amount of dark fiber available.
United States Naval Academy Cyber Security Course
The importance of talent is often overstated, but it's not a myth.

The years I spent trying to do software development were like beating my head against the wall. Everyone seemed to be much better than me, and it led me to give up after a few years of starting and stopping. If I couldn't even manage to make a simple application, what was the point when so many people made one every day?

So I gave up and focused on other interests, like writing and art. Writing has served me well, but doesn't interest me enough to get much written. I'm just bad at visual art, no matter how much I practice and study. Fractal art is about all I can do[1].

Then I picked up a MIDI keyboard, a DAW (first LMMS, then Studio One) and had fun making music immediately. Haven't been able to stop since. Now I'm rediscovering my interest in A/V engineering. As you can imagine, knowing a little programming helps a lot with both of these things, and that's how I found an interest in writing code.

Most of the code I wrote even before finding a need is solid, efficient, and secure. But that's because I'm so bad at it that I have to be careful. If I don't write clean, efficient code, I won't be able to understand it well enough to fix it when something goes wrong.

I think we would be better off encouraging people to try many different hobbies rather than pushing them into something they have no affinity for. Then, when something clicks, show them how programming can make it better.

[1] http://www.designbyhumans.com/shop/mkronline/
Its best to consult with your laptop/charger/battery manual.

If anything goes wrong, new battery costs like $20. Feel sorry for battery prices for Macbook users, but then their charger is smart enough to help battery survive longer.
Ah, good to know. So Nim does static analysis on conditionals where Rust would use an explicit pattern match to get at the contained value.

Might be a good example for http://nim-lang.org/manual.html#not-nil-annotation
If you can amortize the battery cost over the miles driven, electric cars ought to be cheaper than gas cars. Less maintenance (no spark plugs or oil changes), less consumables, and the purchase price is about the same (see my first phrase).

If Better Place had worked out, it would have let people shift the battery ownership elsewhere. But it didn't.
Is there a way to modify the max charge level on apple laptop products?
I just pull the battery out for extended plugged in sessions. Get it to 98%, pull out battery. No need to waste charge cycles.
Group 1 will never be programmers, group 2 is where I fell the first time I tried it. Group 3 probably have some training and group 4 probably have some programming related experience, or maybe they are superheroes. At any rate, anyone in groups 2-4 can become excellent programmers if they apply themselves and get the help they need. They can be plotted on a programmer competency bell-curve. Group 1 are the people who will never learn to code because they refuse to try. They probably make up the first hump of the perceived bi-modal competency graph. But they were never really in the running at all.

I can think of at least 2 people in my 30-person cohort in college who did not know how to code, and would fall in the first hump of a bi-modal competency graph, despite having passed 2 years of programming courses.

So my theory is that the second hump is a normal bell curve, and the first hump is people who won't try.
Lean Testing
This is my favorite technology superstition, some citation would help many people sleep easier it seems.
Poor analogy follows:
Programming ability is like chess ability. The skill lay on a regular distribution, but the game that 1900 players play (top 5%) is much different than the mean (~1400).
Full-time | Phoenix, Arizona

GiftcardZen.com - we buy and sell numbers. Funded. 20 people. We're the fastest-growing company in Arizona.

Looking for:

Developers: RoR, Heroku (see Stack below), Communications Lead, Data-driven Marketer, iOS & Android developers, Go-getter / Intern & Account Managers.

Our stack: We use Ruby on Rails backed by a Postgres database running on Heroku. Because we're constantly outgrowing our systems, we are moving to a service-oriented architecture, both by moving process to service objects within our existing app, and creating microservices which run in separate applications.

All positions are full-time, in our gorgeous new downtown office where developers have both windows/light/views and also doors that close. ;)

How to apply: hiring@
The data, at least in the Milwaukee prosecutor's office, does account for a lot of that. In fact, it apparently accounts for really obscure state like "two or more prior convictions", "arrested under 16", and "ever suspended or expelled from school". So all of that would have been part of the study. But I think what's important to understand is that different people are going to have different advocates. And that will not be part of the study.

Maybe a lot of the white kids had better lawyers, as opposed to the black kids who had overworked public defenders ??? Also... we shouldn't minimize the impact that parents can have on the process. Maybe a lot of the white parents were very involved and maybe even talking to the prosecutors ??? So then the prosecutor says "well... this kid only had a joint... I'll just let his or her mother/father take care of it." The mothers may not be that active as advocates in the case of the black kids.

What advocates were acting on behalf of a kid... we don't know. And it's just the sort of thing that would, typically, not be recorded - and, at the same time, have an enormous impact on outcomes.
Interesting. Do you know if there are any positions in the UK or any other part of Europe?
Plenty of interest. Containerization is still a new paradigm and a lot of us are just getting started with it. I'd love to read your experiences.
It looks good, and don't want to shoot down the UI, but here are some suggestions:

In regard to pictures 4 and 5, Roku tried the fully horizontal menu for a while, but wasn't great. It's too limiting. Think about using a vertical left and a grid right like they do. It fits more and given the right control, works pretty well to navigate, even if it isn't the prettiest.

And, if you only do one thing, remember the rule of simplification and reduce the number of visual elements required to convey the same information. Examples...

In picture 6, you shouldn't need icons strawn about the window left, right, and bottom. All kinds of space wasted for no apparent reason.

In picture 7, just say no to the advertisement looking things in the top bar and the useless title and description at top. If you must get their attention, make them go through a screen to have full attention on your singular announcement. Don't make noise.

In picture 8, having the blue under each black and white icon is a little distracting, and the text and icons have features too small to read or recognize easily.
"I could never drive an electric car because <insert my unique situation and criteria>."

Wait 20 years and then get back to us. In the meantime those for who an electric car makes sense will drive them. For those it doesn't won't.

This isn't politics or sports but a lot of the reasoning on here reminds me of those types of discussions.
Not to be discouraging, but if you don't get many comments or votes, it might be because this has been submitted multiple times over the past couple of weeks:

https://news.ycombinator.com/item?id=9487060 2 hours ago, no comments

https://news.ycombinator.com/item?id=9486301 3 hours ago, no comments

https://news.ycombinator.com/item?id=9485348 7 hours ago, no comments

https://news.ycombinator.com/item?id=9485266 8 hours ago, no comments

https://news.ycombinator.com/item?id=9485237 8 hours ago, 136 comments

https://news.ycombinator.com/item?id=9419035 12 days ago, 125 comments
Ah, so I can only use 60% of my battery before I have to find a plug? Bummer.
You could remove the battery when its charged and stay on the cord. Because battery life is heat-related. And leaving a charged battery in the laptop when you have a cord is chewing up lifetime without benefit.
You should have talked to Google, instead of numerous people.

http://batteryuniversity.com/learn/article/how_to_prolong_li...

Summary:

Similar to a mechanical device that wears out faster with heavy use, so also does the depth of discharge (DoD) determine the cycle count. The shorter the discharge (low DoD), the longer the battery will last. If at all possible, avoid full discharges and charge the battery more often between uses. Partial discharge on Li-ion is fine. There is no memory and the battery does not need periodic full discharge cycles to prolong life.

To answer your question: No.

Side note: Don't blindly trust the manufacturer. Of course Apple wants you to wear out your laptop as fast as possible, once it's past the warranty. They're a business.

Side note 2: Laptops do NOT charge your battery to 100%. Your battery indicator is fake. 100% on your battery indicator is more like 90% in reality. The charger automatically cuts off before it reaches the true 100%, so all of the comments in this thread about 100% being bad are wrong, because no modern laptops will truly let you reach 100%.
> For proper maintenance of a lithium-based battery, it’s important to keep the electrons in it moving occasionally. Apple does not recommend leaving your portable plugged in all the time. An ideal use would be a commuter who uses her notebook on the train, then plugs it in at the office to charge. This keeps the battery juices flowing. If on the other hand, you use a desktop computer at work, and save a notebook for infrequent travel, Apple recommends charging and discharging its battery at least once per month.

— https://web.archive.org/web/20110521104819/http://www.apple.... via http://apple.stackexchange.com/a/12280

This could also be useful, but doesn't answer the question directly: http://www.apple.com/batteries/maximizing-performance/
You can know the stack but then write raw code with nested if statements and for loops to just implement the current requirements to the letter. As soon as a small change is introduced to the requirements, you're screwed.
You can control the battery % at which a device will begin and stop charging - so there's no need for this. Idk what all this misinformation is about.
> If you leave it plugged in, you aren't losing cycles

Too bad that some batteries wear out even faster this way because of the heat.
GrooveShark shut down
When you say, "If you run the numbers", what you mean is, "If you do the calculation for the operation that we know how to do then..."

And I agree. We do not know how to perform an operation that extracts net energy from the zero point energy. We have no idea how to go about it. And we have good reason to suspect that this is impossible.

We just have no proof of it.

For an analogy to a past situation like this, it is like the situation for many decades when it was known that Maxwell's demon could break the laws of entropy, but we were pretty sure it couldn't be built. And there was a century long back and forth on the topic before that was demonstrated.
FCC’s Tom Wheeler Talks Net Neutrality, Congress and Serving the Next President
I just used Papa at the office today. Remembered it from a while ago, it really turned out to be effortless. Excellent work.

(While I'm at it, may I suggest to provide CDN URLs on the website? IMO it would make the otherwise awesome page perfect.)

Thank you again.
20% is the standard for lithium batteries, but sooner is always better.
> Our brains work in so weird ways.

I think, to be specific, it's more cultural influence.
yeah, that is actually what I was saying. I just provided an alternative way of looking at it where you pipeline the dependent operations instead of running them at the same time.

eg:
instead of:

foreach actor(find collisions -> find response -> do movement)

do:

foreach actor(find collisions) ->
foreach actor(find response) ->
foreach actor(do movement)

That way you may modify the primary data structure directly in the 'do movement' response without any conceptual 'data races'. It really just off loads the information lost from 'mutability' to the secondary data structures of collision lists and the like.
The problem isn't necessarily that specific issue, because now that it's known, practical measures can be taken to compensate for the risk.

The problem is that the existence of that one issue demonstrates a serious failure in the tools and development processes and quality checks used to create the control software. There could therefore be other issues in the code that haven't been found yet that could cause similarly catastrophic failures.

Failing to reliably identify this kind of arithmetic error is a huge deal when you're working with high-reliability software. It simply shouldn't happen, and there should have been several different stages in the development process that would have prevented it.

So, the development team should have the book thrown at them until someone figures out exactly how it did happen, closes every related tool and process loophole so it can never happen again, and audits all potentially affected code to make sure the same combination of loopholes hasn't allowed any similar mistakes into production elsewhere in the system.
> The present invention relates to calculating the average of two integer numbers, and more particularly to single instruction cycle calculation of the average of two signed or unsigned integer numbers with a correctly rounded result and without errors due to overflowing of intermediate results.

From what I see this is proper patent. There is disclosure, the claim is specific and seems that there is inventive step. Am I missing anything?
How Facebook Is Profiting from the Digital Divide
Ratatouille with rye bread toast
Agreed. Though the OSX build needs a lot of love.
> If they went organic grass feed beef one day they would need the entire 20 years of the entire US organic beef production to fill their first year needs.

Perhaps they should phase it in then? It's not like A/B testing and exploratory markets are not a well known practice.

In fact, that'd be the best way to trial it, and build up the supply chain - prove it works and helps build anticipation if the offering is really well received.

Furthermore, if it was an option, perhaps that would allow them to further phase it in.

Change doesn't need to be done all at once. True, it's not like random small chain restaurant deciding to do any of the above, given McD's franchise model and volume, but it's by no means as daunting a task as you describe.
Good advice. The only caveat being this only works for certain laptop models
A Home for All the Lonely Apple Watch Heartbeats
Tesla e should know this.
>It would be great if I could trade equity with other engineers to slightly lower the risk of the "all in one company" issue.

That's a fantastic idea. It wouldn't really be possible to trade equity without the companies permission, but you could probably trade percentages of future earnings from that equity.
You could remove the battery

Oh, if only that were true...
Ultimate Performance the Boss 351 Mustang Way
Lenovo at one time (they still might, I'm not sure) included a piece of software that allowed the user to optimize charging for battery life. Basically, it would stop the battery from reaching 100% of a charge.

Great idea, except that if you forgot to turn this feature off and had to leave, you might leave the house with just 60% battery life.
No, you can use as much as you want. But Li-ion cells will age faster if you deplete them completely, so it's not the best way to keep your battery healthy.
Uniqueness Validation Race Condition in Ruby on Rails Applications