skysight-inc/HackerNews huggingface dataset:
If you are talking about the part on unit test, yes that was a bit extended. I guess he was just trying to cover up his silly mistake (nothing wrong, only human!). Also I think the audience mostly consisted of student researchers who are probably not used to the idea of writing unit tests.
Maybe they can't write it in a personal way because as long as they treat it as a technical process, they don't feel responsible.

Even CEOs need to feel like a cog in a machine sometimes...
I made this FWIW
http://jsfiddle.net/nXth5/

It gets the domain of the website you need a password for, he login you want to use, a pin that can be website dependent. It outputs a deterministic password that's 12 character long and contains at least one uppercase, one lowercase, one number, and one symbol (since some websites require you to have that)

(And no, there are no benefits in using a KDF if you think for a second about the constraints and the threat model)
That is some real dedication the the Java way.
Choosing among various projects to pursue at a large company requires understanding of market trends, financial projections and assumptions behind them, as well as various human resource management issues. Clearly, a very smart person could pick that up on their own - but you can also study from a body of knowledge of how to do this effectively. In some ways, picking up CS is much easier on your own than knowledge you get from getting an MBA
It goes to "The Open Source In-Memory Prediction Engine for Big Data Science"
This works great unless you're rebasing and the commit hash you reference falls out of use. In PR comments that I expect to rebase again before release but for which I don't expect changes earlier in the file I'm referencing, I often live on the edge and link to the mutable diff. In the context of PR comments, you can edit them after the fact, so neither choice is necessarily game over - you can fix the line number or the commit hash you point to after the fact.
> A lot of people have a tendency to over-value their work and roles.

I think most people are shitty at it on either side. You can be great at your work and role and still get the axe. Management doesn't often take that into consideration.
The generated password is also site-unique and thus leaves you more resilient against sites losing their password databases or being outright malicious, but the rekeying problem in the grandparent post is a major (essentially fatal) downside.
Does yours detect which part of the full-text is an author name, which is journal and which is publication date (mind the reference section present in practically every paper)? Does it index the notes you made on them?
Here ya go: https://github.com/avelino/awesome-go

Please don't forget to contribute if you see a package you like missing from the readme file.
That's the usual purpose of a password manager. Freeing you from having to remember long and/or complex passwords so you can effortlessly have stronger passwords and more convenience (also different passwords for different services without having to remember them all).

Keep in mind that this is something for personal use to retrieve passwords used somewhere, not for storing passwords for users within a service (at least your confusion sounds like you might be confusing those two things).
> Tons of middle management there, just sitting for years and causing obstructive damage.

how do you know it's middle management?

> Getting rid of dead wood

That's such a despicable way to talk about human beings,but not surprising here,unfortunatly.
ClipUp – Idea. Gather. Organize
Can Brain Training Be Used in Schools
This struck me: the layoffs are motivated by two outcomes, one of which is "work simplification".

Automation eliminates jobs, I've said this for a while.
If anyone's interested in anedoctes from a library dev point of view, I've my framework listed there (it's called Mithril), and microjs is not a big source of traffic despite microjs being around for a while.

Microjs displays popularity from the release repo, which in my case is low compared to the development repo ( https://github.com/lhorie/mithril.js ), so even the little information that is displayed in the microjs site is not super useful for someone trying to figure out what libraries are worth looking into.

Myself, I primarily use it as a starting point resource for looking at how someone might have tackled a small-ish domain, to minimize getting tripped by caveats I might not be familiar with.
I have a hard time swallowing police department rhetoric in these situations. The officer has a gun, and the unfortunate power to make "extra-legal" killings with it. They're safe. If they irresponsibly use that gun in an unsafe manner, like all the drunken NYPD officers who shoot people[0], then it absolutely is our or someone's responsibility to take matters into our own hands and monitor ourselves until we see that accountability. Relying on internal affairs/review commissions to provide that is a broken model.

Also, I know folks doing this locally, and have watched officers request that filmers stand at a safe distance. It's interesting to me how often "safe distance" corresponds with a) somewhere with a shitty view far away and b) a position where the filmer is significantly further away than a number of pedestrians or gawkers whose "safety" presumably isn't in dispute. I have good friends who were arrested for nothing more than filming, and they were often given confusing and contradictory orders by an officer who obviously felt he had the immediate situation well enough in hand to direct most of his attention ordering the filmer around. It happened almost 2 years ago, no charges were filed, and if this was a legitimate concern then I'd really like to see some obstruction charges brought in the several local cases I've seen of citizens arrested for filming.

I do agree that some of these groups' strategies are a bit busted. I'm familiar with the Peaceful Streets Project here in Austin, and sometimes the ragey/personal rhetoric got a bit overpowering. Then again, cops kill people, often under suspicious circumstances, and get away with it. Perhaps it is time for a bit of rage, and to make it personal.

0. http://www.huffingtonpost.com/2014/05/01/brendan-conin-nypd-...
Thought of this a while ago and it probably already exists... but I hadn't seen the one with a pin code yet to verify that your passphrase is correct. That's a nice addition!
I meant "square foot". It's a gardening thing in the USA. If you want more, rent more; 1ft^2 is the basic unit.

Good point on "chemical warfare" - and this arrangement can solve it. Unless you request a particular arrangement of adjacent square feet, the GaaS (Gardening as a Service) provider can arrange arrangement with other people's plots to improve on inter-species interactions, and do so in ways that individual gardeners can't because they don't have the scale nor variety.

Sure, rent-a-plant would work too. I prefer the "square foot" approach. My idea started when the lead post reminded me of those odd real estate semi-scams that sold "one square inch" of some otherwise desirable area, complete with legal deed; then I realized that "square foot gardening" is a thing, and ran with it, and now hopefully calbear81 will really take it somewhere.
Udacity now have Android courses in partnership with Google : https://plus.google.com/+AndroidDevelopers/posts/jmSk2az9715
The original paper being discussed:

http://arxiv.org/abs/1312.6082
Compared to the original, this sounds much better, and looks grammatically correct!
You could easily increase security by adding another rule that only you know to the seed.

For example, if I am generating a password for nthj@example.com, I could have a rule that I always append the first four letters of the domain name to my seed.

In this case, I would actually generate a password for nthj@example.com+exam.

In this scenario, my master password may be compromised, but the hacker would still have a lot of difficulty using the master passphrase to access any of my accounts.

This, of course, only works if no one else knows your rule, and you could get far more clever with the seeding rule than I was just now before my first cup of coffee.
A friend of mine who has been CFO of a couple of Fortune 500 companies once told me that layoffs always drive a stock price up, and that it's also one of the single biggest proofs that Wall Street analysts have no idea how to run a real business.

He explained that any company who could shed a massive amount of its workforce within a year, or all at once, is a red flag for massive internal problems. At the time we had this discussion, he was the CFO of a company that had over 30,000 employees globally.

His thinking was that the same principals that small companies use (not hiring too quickly, etc.) should be scaled up regardless of the company size. You either need people or you don't. You don't hire too fast simply because you are experiencing rapid revenue growth, because revenues do not grow unabated. You hire as slowly as you can, so that when recessions hit or market forces change, you don't suddenly have 3 or 4 times the staff you need. His thinking (which I agree with) is that since those people worked extra hard to cover the work when times were booming, you don't turn around and lay them off just because things slow for a couple of years.

Those people worked hard for the company because they are good employees; he saw it as more important to have good employees on hand when things ramped up again rather than just cut them loose and hope he could get more good employees later.

Since that discussion, he's gone on to two more companies, leading one through an IPO as the CEO. All of his companies have operated like gangbusters - he comes in, revenues go through the roof, debt gets paid down and he's NEVER LAID ANYONE OFF. In the meantime, in his work history, he's been through 3 IPOS (two as CFO, one as CEO) and I don't know how much he made personally on each I do know that he cleared $41 million in a single day on one of them.

This is in complete opposition to what I've heard from several other CEOs, who tell me 'labor is your most controllable expense'. Yet, none of their companies (some also on the NYSE or NASDAQ) have performed anywhere near what my friend's has.

I think he's right. Wall Street is full of guys who have no actual experience running a business. They see layoffs as 'cleaning house' and 'cutting expenses' but the reality is that while that can be true, it more often is a harbinger that the company is not well run.
You can't ignore physical damage, but you can most certainly ignore attempts at emotional damage. Your emotions belong entirely to you. Nobody can change them on your behalf.
Google Software update 5.0 benefits developers to transit to wearable devices
The History of Civilization
e.g. see www.supergenpass.com (who use an identicon as a visual hash of your passphrase for verification, rather than a 4-digit code, so might be easier to recognise)

I'm personally a big fan, at least for low-importance logins. As other commenters have mentioned, there are definitely security trade-offs that need to be considered.
> O'Brien's boot metaphor was purest hubris

It's quite possible Orwell agreed with you there. One thing not everyone notices is that the Newspeak appendix to 1984 is written in the past tense.
So, how do you tell a workforce of X people that 18000 jobs are going to be cut?
There are lots of companies with more than 127,104 employees that manage just fine. Boing across the street for instance. The reason for the cuts is two fold. First, Microsoft acquired Nokia and they're going to let go of all of most of the non-engineering staff, as well as a lot of the management. Second, Microsoft just restructured itself. It used to run like a conglomerate with VP essentially running their individual business like a fifedom ala the organizational chart comic (http://www.kaushik.net/avinash/wp-content/uploads/2012/08/or...). Over the last 3 years there's been a series of high profile executives let go with the intent of increasing cooperation between the divisions, then last year the company restructured going from 9(?) divisions down to 4. As a result there's a lot of redundant people and teams. This house cleaning is in part a result of that.
You doubled down on your sexism with ageism.
Oh expect. I've got a crappy little script I wrote when I was a sysadmin at Ticketmaster used to change a lot of our out of band management card passwords:

http://www.digitalprognosis.com/opensource/scripts/change_pa...

It might be useful to someone else.
Female Yahoo Exec Accused of Sexual Harassment Files for Defamation
The door id is not just the user id it also contains the site name. For example "username@site.com".
Most likely he did not write that email himself, that's what assistants are there for.
Subject: Important Company-wide Announcement

Dear Employees,

For our business to continue running, we must reduce the number of staff. This is an unfortunate but also inevitable reality.

[insert details of layoff here]

[insert honest platitudes]

Senior management wishes all of you the best of luck, and has every confidence that you will be even more successful at your next job.
So finally we found a use for google glass.
Is this going to bloat the Software Engineer market? Do we know what percentage are developers?
A C++ Embedded Webserver
A Descriptive List of Free Online Ruby Tutorials
The problem is that the 'door' is your password now - you have to remember all the different doors, or use a password manager to store them for you... But then why not just keep the actual passwords in the manager?
Layoffs almost always improve stock price (literally the first thing "strategy" consultants do when brought in to help "fix" a company is look at an org chart and start hacking bits off). Whether layoffs are actually a good move in the long run doesn't become apparent until much later. (Did you destroy your ability to keep doing business to get a nice bottom line in the short term? Corporate raiders specialize in buying companies with borrowed money, firing a bunch of people, pumping the bottom line, and then selling them before the fact that they're now crippled becomes apparent.)

I had a guy under me laid off, and I resigned on the spot -- because his being laid off meant the company was giving up on a core capability that was the main reason I wanted to be at the company. A friend of mine was working at a large software company that laid off "dead wood" (according to management) including key engineers, which literally led to all the other experienced engineers on his team leaving.
Filecoin | Democratized Cloud Storage
They're different concepts, obviously (hence the different names for them), but they correlate strongly.
Even though I get tired of all the "rules" the entrepreneurial community sets out, half of which contradict the other half, I can completely relate to "slow and steady is bullshit" idea.

I started a company when I was 23 and found product-market fit almost immediately. But, being young, naive and completely unexposed to "real" entrepreneurship, I tried to grow the company organically, customer by customer, market by market (in my case, TV markets) rather than raise money. I woke up every day, hit my cold call targets, and spent the rest of the time coding, dealing with other IT issues, recruiting, managing employees, bookkeeping, etc.

While I was busy gathering rinky-dink customers in one corner of the country, my competitors raised money, expanded nationwide, and completely ate my lunch.

While this may be of the "well, that sounds like a personal problem" variety, I believe the following holds true when a new "gold mine" (i.e. as yet unrecognized market opportunity) is discovered by one or more companies:

"Even if you're growing, if you're not growing like crazy, you're falling behind, comparatively."

For example, let's say there's a company competing with Uber that's growing by 2x per year. In a vacuum, that's great, right? But not in reality. Uber is growing at like 100x per year and will eventually destroy that company.

So yes, I completely agree with OP, a least in terms of startups.
This map is certainly very interesting, but it suffers as a visualization. The topographical map is nice, due to its simplicity and well-chosen color scale, but the main geological map certainly has some problems.

The biggest problem is that they are choosing two represent two different dimensions of data(age/time period and terrain type), but are using seemingly random variations of hue to show these variations. Additionally, with so many distinct hues, it is nearly impossible to tell the difference between some areas on the map (for example, Hesperian basin unit and Hesperian polar look very similar).

A more effective way to visualize this data would be to apply a separate hue to the 8 categories of terrain unit, since these are categorical data points. Then, visualize the geological age on a brightness scale, since this is more of a quantitative measurement (obviously the current map also show the particular time period, we'll just ignore that for now). I think this would provide a much clearer view of the data, though you would lose a small bit of granularity.
The views were beautiful but the scene transitions in the video got irritating. I stopped watching after a while.
You can add a standard string to all passwords, for example "Ab1#", so that it satisfies like 99% of sites. You do get in situations where you have to know remember some more information, but this can mostly be written down.
> Sorry, nothing "hateful" intended. Saying "for Dummies" in a book title is now famous. It's supposed to be to have sympathy for someone struggling to understand and, thus, feeling like a "dummy"

But emphasizing the audience - boys - is less common (but the audience would I guess be implied, anyway. But I don't imagine literal boys would pick up a for-dummies book on the opposite sex).

It's also become in vogue to regard boys as psychologically and emotionally stunted, compared to girls. The title just seemed to hint toward that trend.

> Sorry, nothing "hateful" intended. Saying "for Dummies" in a book title is now famous. It's supposed to be to have sympathy for someone struggling to understand and, thus, feeling like a "dummy"

And yet, women and men seem equally mystified by each other. Women and their higher social/emotional intelligence doesn't seem to fair better than their knuckle-dragging partners. There are plenty of men who cling to unhealthy relationship, plenty of women who do the same, and many of them seem equally irrational in their insistence of clinging to it.

No, I'm not someone who is of the opinion that men and women are on average equal, and that any perceived difference is all about "selection bias" or whatever. But some universally "accepted" differences, I find questionable. Like women being emotional and men being rational - though women may be more emotional, men are just as much slaves to their emotions as women. And women's higher social/emotional intelligence doesn't seem to help them in their relations towards men. I guess it's like the misunderstood geniuses - too smart for their contemporaries (partners)?
We used Expect recently to automate iOS runtime hacking (ssh to jailbroken iOS device, run cycript to inject code, profit). One of those old Unix tools (built on tcl) that's very handy for automation.
Google enforces HTML5 use on YouTube for Firefox 33 and newer
Google tests Loon in the Brazilian northeast
Why would you assume that a link is good for more than 1 day ?
Nice.

I have a somewhat similar tool but it doesn't do much besides check for password expiry and do password changes.

It uses pexpect but also multiprocessing and multiprocessing.Queue. I built most of it before we started using Ansible at work, but it is still useful in those places where Ansible is clumsy.
Because while that's the top-line for the 18,000 people affected (12,500 today), he'd desperately like that not to be the only thing the other 100,000 people who are staying hear. He wants the rest of the people to first hear: "We're changing for the better, and while these layoffs are a bad thing, it's necessary pain we have to go through to be better in the long run." That means wrapping the bad news with as much context and transparency as you can, every time you talk about it.
Carbonite: A slightly better pip freeze
"And while I'm lecturing you, I'll be sure to make it derogatory." Nothing like calling someone an 'ignorant hipster' for buying a product.

This article seems like it was written for people who already hate that other people like almond milk, and they just want more ammunition so they can lecture their friends about it.

My wife and I use almond milk for a few reasons; we can't drink dairy (I can't digest milk fats, she's lactose intolerant), soy milk is highly processed and the rapid growth in soy products is already a source of environmental concern, and rice milk is vile. So we get rice milk. We use less than a cup a day on average, and there are entire weeks we use less than a cup, rather than 'drowning our cereal' as the author points out many people do.

And then there's this gem at the bottom:

As for me, when I want something delicious to moisten my granola or add substance to a smoothie, I go for organic kefir, a fermented milk product that's packed with protein, calcium, and beneficial microbes. Added bonus: According to the label, it's lactose-free—apparently, the kefir microbes transform the lactose during the fermentation process.

This is the most hipster paragraph I've read in months. Personally, I can't wait until three years from now when someone is writing an article on Mother Jones about how 'organic' kefir is actually awful for you and the planet and you should be drinking this other thing instead'. For example, they could start with how terrible the dairy industry is, like the author outlines in his fourth paragraph.

Like another commenter posted, if there's something you like, there's someone out there just waiting for an opportunity to lecture you on it.
You can't pull autorotation with fixed pitch blades, at least not in any meaningful manner. Light quads can fall pretty slowly with pinwheeling motors but that's not actually autorotation. The way a helicopter is able to autorotate is to pull negative pitch, which spins the rotors using the fall energy of the copter, then shortly before crashing pulling back to positive pitch and using the still spinning blades to slow down to a controlled landing.

For motor failure ETH Zurich has some research out there about recovering to normal(ish) flight after a prop loss. The quad goes into a pretty rapid spin but it's still controllable, link below to an outside the lab test.

https://www.youtube.com/watch?v=ek0FrCaogcs
The Nokia layoffs are only the first half. One of the last things Steve Ballmer did was restructure the company.

http://www.microsoft.com/en-us/news/press/2013/jul13/07-11on...

This created a lot of redundant people and groups.
Do you do that explicitly or is at a compiler optimization?
This is great! thanks for sharing.
Not really. Slow and steady would be splitting the entire learning material over a longer period. This would be learning everything as fast as possible (cramming), then taking a couple weeks break, then cramming again. It is indeed much more effective.

(the general case is much less explored, and the article provides no evidence either way, unfortunately)
> None of these passwords are ever stored. The pass-phrase is not a master password to some stored list of passwords.

True... but what makes this method superior to simply having a master password to an (encrypted) stored list of passwords? What makes it more secure than that ordinary way of doing things?

It seems to be less convenient in some ways (there are more things you have to remember), although perhaps more convenient in others (there is no password database to keep sync'd accross multiple computers or to lose).

But I don't think it's actually any more secure?