skysight-inc/HackerNews huggingface dataset:
Source: I have a master's degree in mechanical engineering in hybrid vehicle powertrains, and a big part of my research was battery technology. I spent some time working with the folks at National Semiconductor learning this, so I have several primary sources.

Disclaimer: my knowledge of the field is from ca 2010.

1) Lots of deep discharge cycles do negatively affect battery life. Try not to jump between 0% and 100% too much.

2) Li-ion batteries do not love being at 100% SOC (state of charge). As batteries become more dense, the membranes become thinner. High SOC equates to high chemical potential, which will break down membranes faster. As such, avoid leaving your battery at 100%. This wasn't as much of a problem with older batteries with thicker membranes, but is becoming more and more an issue as we try to squeeze every ounce of density out of batteries.

3) Roughly 70% SOC is where a battery is happiest, but the whole range of ~30-80% is pretty happy for a li ion cell. Try to keep your battery at ~70% or so overnight, at 50% or so for long sleeps.

A good usage pattern: plug in and let charge to 90%, unplug and use for a couple of hours, plug back in at 50% or so, rinse and repeat.
I've always been told that the number of cycles was the most important factor in battery life (but not the only one). A cycle is one complete charge+discharge, with partial credit for partial discharges — so discharging to 50% counts as 0.5 cycles. [1]

This tells me that leaving your battery plugged in whenever possible is good, since it minimizes the number of cycles you're putting on the battery. If you unplug the battery once it's fully charged (and proceed to use it), you're just subtracting cycles from the battery's life.

On the other hand, apparently there's a cost to letting the battery sit at 100% charge for too long. I don't know how long "too long is", but Apple's battery site says this about long-term storage: "Do not fully charge or fully discharge your device’s battery — charge it to around 50%. If you store a device when its battery is fully discharged, the battery could fall into a deep discharge state, which renders it incapable of holding a charge. Conversely, if you store it fully charged for an extended period of time, the battery may lose some capacity, leading to shorter battery life." [2] Keep in mind this is specifically talking about long-term storage only.

Taken together, I interpret all this to mean that it's best to leave the laptop plugged in at 100% whenever possible, provided that you're occasionally taking it out and using it (so it's not "long-term storage").

That said, I'd love to see some quantitative benchmarks to confirm all this. ;)

References:

1: http://en.wikipedia.org/wiki/Charge_cycle

2: https://www.apple.com/batteries/maximizing-performance/
The title is slightly misleading but not entirely. Docker was, at first, a container technology. However, after it received its funding it has tried to convince the community and investors that it can be more and started to provide container orchestration tools, i.e Swarm, Machine and so on. Docker has received most of its momentum and attention because of the work they did around the container format. Docker build, run, stop, encapsulates most users experience of Docker.

Docker wants to be known as a platform providing container management tools and it needs to do this quickly because Mesosphere and Kubernetes provide this type of functionality at a more mature level, albeit using somewhat different philosophies. The container format part of Docker is ultimately replaceable.

Google (Ventures) backing Tectonic is significant because Tectonic will provide a commercial enterprise-ready distribution of Kubernetes supporting Rocket. Rocket doesn't need to reach feature-parity with Docker to be a notable replacement because Docker already does too much. All Rocket needs to do is provide the much needed enterprise features that Docker is lacking and integrate well with Mesosphere or Kubernetes. If this happens before Swarm and Machine mature, we could be wondering 6 months down the road what the hype around Docker was all about.

If Tectonic succeeds in the enterprise marketplace then Google will have stealthily marginalised Docker using community efforts through rkt and kubernetes and not had to fight them directly.
Obligatory (and analogous) XKCD: https://xkcd.com/927/
The Sony VAIO laptops also have this feature. Sad thing is there is no option for enabling this on Linux.
From memory transfer of copyright requires a written contract in the US; so be it your employment contract or a freelancers contract it needs to be written down. I have had contracts where I have successfully negotiated having that clause removed. Just because someone pays you to write code doesn't necessarily mean that at the end they own the copyright. Some jurisdictions however have implicit transfer of copyright in work for hire situations so consult a lawyer and make sure it is always written down.
There are a few of those, but also the default client behavior boosts the priority of old transactions so they will be processed eventually. I would guess that high-throughput miners responsible for the majority of hashing power would have other priorities though, so the "default" config might cover a minority of hashing power.

Edit: It's the age of the inputs to the transaction, not the age of the transaction itself that counts. But it's possible to just wait until the transaction inputs are old and then the transaction will go through.
You're being a little unclear on what is vs what should be, which are obviously different.
It's miraculous that pressure variations on your ear drum reproduce the impression of the orchestra; the speaker just builds on that.
A shot at retiring, eventually.
Your battery's life is all about charge/discharge cycles. Say your battery has roughly ~1000 such cycles. Once you've exhausted the cycles, your battery is typically running on bonus power. Whatever performance you get after this is extra and cannot be relied upon.

Thus, the longer you can preserve your cycles, the longer your battery will survive.

You can also read this thread: http://www.reddit.com/r/askscience/comments/1snzg1/is_it_act...
That means we need to be doing something to get more people into our industry.

Why? What's in it for me?

The EU has published similar numbers, 1.2 million in 2018—three years

I am a first-year CS student in Denmark and I hope you don't succeed in getting more people into the industry to fill those jobs before I graduate.

The lack of (talented) programmers is going to put young CS/CE grads in an advantageous position both in term of salary and job opportunities. I am happy employers are having a hard time finding people to fill those jobs. That makes life easier and safer for me.

The people screaming for more programmers here in Denmark are people in the government and Dansk Industri (lobby group representing bigger Danish corporations). The government cares about something they call "Denmark's global competitiveness" and the lobbyists in Dansk Industri want to flood the market so they can lower programmers' salaries. I don't care about the former line of buzzwords and the later is a hostile action taken against me as a programmer.

Don't get me wrong. I care about our industry. I will contribute to open source in the summer leave and I am involved in organizing some monthly meetups. But in the end of the day I also want a job.
The fact that Apple no longer has this statements on their website makes me think it's no longer true for their batteries (if it ever was).
Almost every residential and commercial building in NYC has fiber running in front of it: http://arstechnica.com/business/2014/06/09/verizon-will-miss...

That last few feet? Dependent on landlords.
> that just means it is rolled into the price of the car.

True. But if there were an option for all-you-can-eat fossil fuel, a lot of the market would probably consider it very seriously, especially if it were less than 5% of the cost of the car.
I believe so - thanks!
HappyApps streamlines application and system monitoring
Murder is not (supposed to be) explicitly sanctioned, only killing is. Murder as a word is supposed to designate specifically unsanctioned, immoral killing. We don't need another word for kill, we already have that word.

Don't let murder steal kill's job!
That's the summary you chose. Here's what else is said:

"It must be noted that a large proportion of the published work is descriptive and provides little quantitative data that we could assess independently. Many of the monitoring studies lacked sufficient detail with respect to study design and statistical analyses, making conclusive interpretation of results difficult."

"It is clear that greater clarity and improved methodologies are required in the assessment of the ecological impacts of desalination"
True. My contention is that learning happens in steps, it's not linear. This is especially true in programming. So rather than a smooth curve of talent, there are plateaus that people reach.

I would love to see data on this. Who knows, I might be wrong. (Wouldn't be the first time - even today)
Find out who builds the web
Spot on.

What's fantastic about this is the open wifi in low income neighborhoods. If you look at Pew stats: http://www.pewinternet.org/2015/04/01/us-smartphone-use-in-2...

Low income folks increasingly have smartphones (income <$30K: 50%) and smartphones are largely their only way to access the internet ("smartphone-dependent" - 13% of Americans in households with income <$30K rely on their phones for internet access, as opposed to 1% for those who make >$70K).

My team's research shows that low income folks largely use the internet largely the same way higher income folks do: banking, shopping, research, and yes, gaming. http://labs.robinhood.org/mobile-tech-impact-potential/

Anecdotally, the way many people access the internet on their smartphones is camping out at mcdonalds, starbucks, public libraries, etc. with open wifi. Imagine having to walk to the nearest Mcdonalds to do your online banking.

These wireless corridors will be transformative.
There seem to be 2 main ways people use laptops in my unscientific "asking of my friends" survey: Plugged in for long periods, or unplugged for long periods. It seems like the vendors should have solved for both of those.

From the previous answers to this item, it would seem that most vendors focused on long life unplugged (6 hours! 10 hours! So long, you'll forget where you last put the cord!) and "you'll have to buy a new battery... and they aren't cheap" if you stay plugged in.

While part of me finds that hard to believe, another part wonders if this is just a part of the wonderous circle of (battery) life. Luckily, the conspiracy part left the building, or he would have said that the evil vendors do this on purpose to keep a steady cash flow.

Sorry, didn't mean to evoke this earworm: https://www.youtube.com/watch?v=8zLx_JtcQVI
Yeah, I have this on my Yoga 2 Pro. The utility is called Energy Manager - and the setting is "Conservation mode".

https://forums.lenovo.com/t5/image/serverpage/image-id/34801...
I'm not sure what you're implying.. you can turn on most optimizations and still keep nil-checks on in Nim (either the whole project via --nilChecks:one, or select portions of code via {.push.}).

Unless you're claiming your example was still hiting UB, even with nil-checks on, and just happened to throw an exception by random chance, I'm not really sure how you figure UB is still happening here (since the exception will be thrown, preventing the deref). Nothing is preventing you from using nil-checks in production code.
Can anyone recommend a good book covering these topics and the history/migration of these groups at an entry/casual level?
1.5 Million position job gap? Really? I hate when people throw the us labor stats numbers around like that.

Uh, hu, I wish these statistics would be backed up in a more through manner. Like maybe forcing companies to disclose how many applicants they get for a position and why they were rejected.

I say this because, I recently interviewed for a position doing some pretty low level work, where apparently there were a 100+ applicants (or so the hiring manager said). But it was believable because the job was posted on linked-in, and linked in reported that 34 people applied for the job.

So, a lot of people applied for the job, were they qualified? Well, considering I know two people with skillsets that are compatible with the position, and both are unemployed and live within 5 miles of the position, I would really like to see this kind of data industry wide.

AKA, assign each candidate a number (only disclosed to the candidate), and then publicly post the number, and the reason for disqualification. Maybe if someone can figure out how, disclose the skills the candidate says they posses without directly correlating them to the candidates public profiles.

That would give us an idea of where the skills gaps are, or even if they are real. Rejecting a bunch of candidates because "they don't fit the culture", or they don't have 5 years experience with CMVC, or perforce or some other tool not directly related to the specific job requirements needs to be public information. Or for that matter, that someone thinks they will ask for more money than the position pays, without making them the offer.
"I wouldn't call it a bug, per se, but it's a known feature that we plan to improve even further!"
no the fast solver has solved the problem and is doing nothing ;)
Don't judge technology by what's there
complete space with an orthogonal basis ... without it digital music would be less of our worries (well, if "we" ever existed)
Submarine Pirates: Periscope Starts War with Hollywood
I'm pretty sure that the charging logic is built into the battery or other dedicated charging circuit hardware. Almost positive that while the OS can say "don't give power to the battery", it can't say "give power to the battery even though the battery says no". Not a great source, but this agrees: http://computer.howstuffworks.com/laptop-battery-overcharged...
I'll get downvotes for this, but my reason for sticking with python2 isn't library support, it's that I prefer python2's strings. Sure, it made unicode handling less painful in cases where encodings are always known and everything should be in unicode, but it makes things much harder for people working with bytes interfaces that want to treat all non-ascii bytes agnostically.
Presumably, any state that does annual safety inspections already has miles-driven info (whether or not it's actually centrally reported today). You'd still need to deal with ownership transfers, collections, etc. but that would be one mechanism to charge per mile without GPS tracking--which (optimistically) seems like a real political hot potato.
It's part a larger myth that probably needs to die also. See the book "Talent is Overrated" for a thorough and scientific evisceration of the idea.
> I have talked to numerous people and there is no set consensus on whether I should be unplugging my laptop charger when it is fully charged.

Hi Zatkin,

General advice: please study the materials hosted at the following great "Battery University" website: http://batteryuniversity.com/

The charge and discharge protocols which are best for battery life and capacity depend on the kind of battery.

Certain batteries benefit from being cycled, like NiMh and NiCad. It's not that important for lithium, IIRC.

Some batteries benefit from priming: treating the battery in a certain way when it is brand new, so it lasts longer and performs better over its lifetime.

(I could use a refresher myself; I'm going to study the materials on that website.)
Rust solutions would probably be the following: Some kind of runtime assistance (`Rc<T>`, `Arc<T>` et al), using indices as you mentioned (though with `list.get(index)` you'd still have to deal with the fact that it might not be valid, since `get` will return an `Option<T>`)[1] Another solution might be to allocate the textures in an arena that lives outside of the scope of your game logic, and have both the texture list and sprites contain borrows (Note I'm not sure about this, as I haven't done much with arenas yet).

Although I'm unsure where the `not nil` as discussed above comes into play here. What part in Nim would be `nil` here where Rust would have `Option<T>`? The difference between `Option<&Texture>` and `&Texture` is that you have to somehow deal with the possibility of no texture when handling the former.

[1] I should note that actual indexing behavior (`list[index]`) will assume you know there is one in there and panic if it isn't. This is one of the things I dislike and hope there will be an optional (no pun intended) lint post-1.0.
I suspect that the Federal Regulations also requires the planes not to fail at 248 days (or words to that effect). Specifications are not the thing specified.
Android Tool for Mac
They do have some advice on "long-term" storage here, which is roughly along those lines:

https://www.apple.com/batteries/maximizing-performance/

They don't say what "long-term" is, but monthly seems reasonable to me.
I read batteries wear off when plugged in in hot conditions, which is often the case for a running laptop. Can you confirm?
Yeah, that's a great starting spot for putting these crazy myths to bed.

A lot of a people seem confused about two concepts in the article: ideal storage and depth of discharge. These are two separate concerns. If you try to maintain the ideal storage charge while it's in-use (say 40%), you're going to end up wearing your battery by putting it through unnecessarily deep discharge cycles.

Unless you want to plug and unplug every few minutes, you should probably just leave it plugged in.
30% capacity loss is generally considered EOL for battery packs. (And that typically happens at 1000 complete charge-discharge cycles.) The Volt should have gone 1000 * 380 miles = 380K miles before hitting that.

On paper, I wanted a Leaf over a Volt, but the real world difference shows that differing battery technology still matters a lot. I dunno how Nissan built such a bad pack but there you go.
I've been wondering increasingly often over the past few years why we tolerate a phone network that allows for caller ID spoofing. I don't see how a system analogous to BCP38 would have any significant downsides, and there's a huge demand for anything that stems the rising tide of fraudulent robocalls.
For Thought provoking books/philosophy books etc I prefer physical books.

For Technical books I prefer digital books since I would love to try out examples almost immediately as they appear in the book.
I found that fully discharging and recharging such a battery 3-4 times will bring it back to (near) its original levels.

I've always had laptops plugged in all the time (desktop replacements) for months at end, with the battery acting as a UPS.

When first disconnecting the power adapter, the batteries always discharged much faster than they should. After a few cycles, they went back to normal.

I believe that leaving a laptop plugged in all the time is better for the battery than doing complete discharge-recharge cycles (5-100%).
Things have been changed in a world of SSDs and machines w/ much memory.
Actually, parsing a CSV in a single thread will never reach several hundred megabytes per second.
From what they're saying in the "Test" section of the Deploy documentation (http://www.manifoldjs.com/deploy), it seems that it just wraps your website in a WebView?

This is great from a developer perspective, but I'm not sure if the App Store review process would allow doing something like that.
All the websites I looked up came up as cast: unknown.
Indeed. From my understanding, while this is still technically true, they have replaced the need for users to do anything with chips in the batteries themselves which shut off recharging when they're near 100%.

That's why if you pay attention you'll often see your battery % go from 97%-100% and then back down to 97%. It is reporting as "charging" but in reality it goes idle to let the battery de-charge a little.
I believe that the current state of containers is just the beginning of the trend and containers development. IMO, containerization simplifies security, fast deployment cycles, dependency problems and improves some other things. There are problems, of course and things that are not solved in a containers world. The obvious thing is a persistent storage - we don't have a good solution to this that uses containers. There are "patterns" (like, for example: running specialized database container and sharing "volume" with the host), but it's just a hacky trick and not a solution. I really hope it'll be solved. Using AWS RDS (Amazon Database in the Cloud) and S3 is kind of a "workaround" (pretty good workaround, to be honest), but not everybody wants to use AWS.

I really like Ansible and I believed that Ansible could help with Docker deployments (http://www.ansible.com/docker), but at the moment I think that using Dockerfiles is faster and simpler. I'm still using Ansible for Vagrant provisioning, but don't need it for setting up production/ci anymore. Sure, Ansible/Chef/Puppet will be probably on the market and used by some big players, but I'd be very surprised if we won't see big shift into containers for most of the technology companies. Being faster, more productive and cost effectiveness (related: https://www.youtube.com/watch?v=xK0njkATf84) are good enough arguments imo.
Is that because they're unable to learn, or because they haven't been taught?
This assumes the battery percentage displayed is the SOC. This might be the case for laptops or small appliances where manufacturers are happy to trade long battery longevity for a small gain in time to empty, but the Model S for example has gap of a kWh+ and will simply not charge or discharge the battery fully, to avoid these cases where a very low of very high SOC damages the battery.
Bad analogy, then? (Also, polio workers are getting shot in Pakistan.)
>I would be very hesitant to rely on any metrics coming out of SE. Consider their great programming survey this year, they say the average age of a programmer is 29. The US Department of Labor says it's 49.

That doesn't mean they're both wrong. The two are just comparing different things. The SE programming survey included 157 countries, not just the US. It also doesn't only include full-time professional developers. 13.6% of respondents classified themselves as "Student". Only 66.3% of respondents listed themselves as "Employed full-time"
My experience has been that it depends on the laptop and how it handles the charging. Some will keep trickle charging at 99% so it keeps recharging the laptop frequently. That wears out the battery and usually in a couple years it won't hold much charge. Other laptops though wait longer until it falls to say 94% even when you leave it plugged in. This reduces the frequency of recharging and the battery lasts longer.
DCT, FFT, close enough I guess. No mention of Shannon or Nyquist?

Ugh, I see a trend starting here:

"This is the first in a new experimental series called Favored Equation. Each month, we’ll dive into a piece of math which makes your life easier in some way without you even realizing."

This is a spin on http://objectsobjectsobjects.com/ by The Atlantic:

"Object lessons: An ongoing series about the hidden lives of ordinary things."

I'm a fan of this type of writing. But when Sagan and Feynman did it -- hell when pornographers did it with OMNI Magazine -- it wasn't quite so rough around the edges.

I'm now a month into arguing with some ex-Gawker hack at The Atlantic over quotes like "New effects can change a guitarist’s playing ability completely" and a declaration that the transistor was invented in the 1960s. No corrections or retractions imminent.

No interest in battling the newer, younger, even-less-experienced Gawker editor too.