skysight-inc/HackerNews huggingface dataset:
I don't think that's true.

If you have a feature branch with a number of changes in the same place, rebasing on to a branch that also changes in the same spot means you need to fix all of the related commits during the rebase. If it's a big feature that could end up being a huge task.

I may be wrong about that as I'm no git guru.
None of the jobs I've had over the last few years have made it mandatory to have a LinkedIn account. I don't see how that would make sense and why employers would require you to have it.
Do Polish employers require you to have a GoldenLine account? I have both, just to see if it leads to any solid opportunities. It hasn't yet.
It would be great if journalists could stop conflating the dark web with the deep web (formerly also known as the dark web) and stir frying statistics between the two (omg! 80% of the web is the dark web and 80% of the dark web is child pornography!).
Hang it near the screenshot of Edward Snowden getting political asylum in Russia.
Beautiful. I would download if it was for Ubuntu, which I thought it was.
For some strange reason, some people conflate the two terms - deep web and dark web - even when they have essentially nothing in common.

Maybe that's where the "Dark Web is bigger than the regular internet" meme comes from.
A good starting point for this article is the movie "Good Hair" by Chris Rock. But rest assured, there is already a lot consolidation that already happened for Temple Hair in India. The raw material for this is, faith of Hindus (Hindu Women to be specific - since they have the long hair), that giving away hair as a form of surrender to God. Any guess, how long that will last?

edit: changed movie name [Bad Hair]
suddenly someone injected www.leekspin.com while I'm viewing the map.
Nothing about these terms is "accurate". By that definition, Facebook is in the deep web.

...And in the dark web -- they now have a Tor-friendly Onion address!
Loituma - Ievan Polkka
I found this out the hard way - when I first was in the interview process with Google, it took almost 3 weeks before I had a technical phone screen scheduled. I ended up canceling it because I took another offer. Later on, when I started the process and had the initial phone screen, I mentioned that I was interviewing with the likes of Facebook, Amazon, and more, I was immediately told that there was an opening for a technical phone screen the next week.

I think they base part of their scheduling on how many similar companies are trying to hire you.
Just a general thank-you to the OP for bringing this up, and for all participants. I've resisted creating a LinkedIn account on principle(s) despite the invitations.

I'm sure there's some selection bias from the title, but the comments help address the nagging fear that I'm shooting myself in the foot.
Believe it or not, Russia today is very free country with very good life for an average Joe, comparing to the UK. And ReactOS story is just another proof of that.
I totally agree with you, I don't get it either. My only explanation is that as a programmer you are trained to write clean and understandable code. I also try to apply this to my commit messages (with varying results). But rewriting history to make everything look clean and simple is the wrong this to do. The messier your history is the more likely you'll need to retrace your steps (and CI results) at some point. It is mostly people coming from SVN and only running CI on the trunk branch that favor the rewriting approach. It might be hard to let go.
> The original plan was to use the fifth day for non-billable work such as searching clients, meeting with people, doing mandatory paperwork, writing blog posts, doing something that would later generate passive income etc.

That's work.
Taking a Fence Down
This is only partially true. You are 'strongly encouraged' to enforce your patent violations, for after a period of years (6) they basically become unenforceable. This is to prevent things like 'patent bombs'.

In practice it doesn't always work this way ( see patent trolls ) but it can be a BIG issue for people looking to enforce their patents.

Here's an interesting example:

http://www.ipwatchdog.com/2010/05/26/estoppel-time-bomb/id=1...
Thanks! I want to say I love you but I will only say that I wanted to say it :P
Glad that Affinity Designer / Photo is coming into the fray to steal more Adobe share. Because it will make all the software better. If only it were cross platform, not just mac for now.
I disagree with you that the history doesn't look pretty.

Have you not found the ability to investigate/audit bugs hindered by non-linear histories?
Yep: being able to tell the difference between feeling, perception and will is essential to my life.

And acceptance: that is crucial as well. This is the fact: "I feel bad. OK, now what was I about to do with my classes today?" (This is a very simplified figure obviously).
Tamr, gets $25.1M in new funding as its CTO wins Turing Award
This is super, will fork it into a private chat with bunch of my friends.
I't s a viable concept. In school we built a functional pipelined-MIPS processor in verilog: https://github.com/eggie5/SDSU-COMPE475-SPRING13
The Climate Wars’ Damage to Science
slightly OT, but I wonder if anyone has an answer for this.

We use feature branches and rebase before merging to master (mostly for the reason stated above - keep things clean and treating the branch as a single logical unit, not caring about higher-resolution history within the branch).

However, some times, especially since we typically merge on Github from a PR, it's easy to forget to rebase, or notice that there are more commits. So our history is mostly clean, but occasionally contain some "messy" commits.

I know we can reset master, but it feels a bit too risky compared to living with a bit of noise when mistakes happen.

Anyone knows of some way to prevent / alert / notify or otherwise help us avoid this rather common mistake before it happens?
The problem with having too many eternal branches is that they quickly become unmergeable. The nice thing about feature branches is that it's the author's responsibility to make it mergeable. But if you having a bunch of eternal branches none of which are "owned" by one person, when it comes time to merge them and there's dozens of merge conflicts there's not one person that can set down and know what the correct fix is for all of them.
Trying talking to people.

That's what is being done right here, right now.

I find that pretty much every woman in the tech industry who I've spoken to has at least one example of how they feel they've been discriminated against at some point.

Then sharing some concrete examples should be easy!
Node.js config loader with built in Environments
Writing considered harmful posts is considered harmful - I hate these so much.
Indeed you need to do them again. But you also have to rerun them after a merge anyway. The problem is that you can no longer see which commits that you merged where green before the merge. For example is very useful if the merge itself breaks the tests (uncommon but it can happen).
Patriarchy and Toilets in India
Node.js MySQL fixture loader
You're looking for https://en.wikipedia.org/wiki/Loituma_Girl
Don't forget that Gary Webb broke the story about the CIA running the drugs to Rick Ross and other inner city areas, and ended up committing suicide (or according to some being suicided.)

The British and Dutch started it with the opium wars and now America took a page from their book and does it too. This is the real issue behind the war on drugs. They create a black market and then own that market, makes for tons of money that's unaccountable to congress (eg perfect for black budget ops).

Opium production in Afghanistan was almost nil before we invaded, and now Afghan heroin is getting shipped straight to America and business is booming! Similar things happened in Vietnam, Cambodia, and Laos.
Why half of the license is CAPSLOCKED? Is it really necessary?
Segmenting a full name in JavaScript
you know, some of us DO hangout around lake geneva (or any other pretty place), have most of weekends done like there's no tomorrow (mountains, adventures, traveling etc. practically every weekend) and still manage to invest into whatever they prefer (right now selling flat in Prague, and considering one in Chamonix). That's my sweet spot in life right now. We'll see how long life will keep me in it, before throwing into something wild, as usual :)

It's not irresponsible to spend money on traveling and adventures. You get back much more than nice time there and couple of photos and souvenirs - you are exposed to new environment, people, culture etc. and you'll grow inside in a subtle, yet steady way. On the other hand, usual "buying stuff you don't need to impress people you don't care about" is useless, and won't even bring any long term happiness.
I tend to agree. One exception I think is rebase on a feature branch. If you rebase a feature branch onto master before merging it into master, I think you can get a cleaner history while achieving the linear history the OP wants -- and in this isolated case, I think you aren't losing any useful context by making it seem the feature commits were all done right before merge into master.

Maybe. I'm not actually sure, to be honest what's a good idea with git history, this included. Feedback welcome.
If it takes a month to get their shit together to hire you, how long would it take you to get anything else routine done at that company? You need a new machine for your first day at work and they put in a request and you'd probably finally get a machine a month later. That sounds like a nightmare place to work.
Yeah I have had several problems working with .svg in illustrator, the biggest one being wacky arbatray resizing of the document bounds when I try to open and edit an .svg. I was forced to export off a master .ai file rather than re-edit native .svg, a pain in the arse!

The workaround I use is opening the .svg in a text editor and editing the properties manually, you can clear out a bunch of adobe auto generated garbage and get the file nice and small.
As long as you're not gay.
I'm a bit confused, why are you merging things into develop if they're not ready?

If Feature B isn't ready, it should stay in its own branch until it is.

Develop is for code that the developers say is ready. You might have bugs, poor merge resolution, etc, but any fixes made should be quick and should pave the path toward code that can be merged into master. If the problems are major, revert develop.

Master, on the other hand, should always be stable and rock solid. You can then have production servers that always pull master automatically, and staging servers that always pull develop automatically.

I've worked on multiple teams this way it works out quite well.
Most of the houses that are really high-risk are at the top end of the market. Don't buy those. Buy mid-market houses, those values are much more stable. And never pay much more than the average house in that neighborhood is selling for, and don't over-improve. The last thing you want to own is the most expensive house on the block, as you'll never be able to sell it.
lol that's so random :-)
True. You do have to fix all the true conflicts. But you have to do it only once. If you merge your master, you have to resolve conflicts every time you merge from the master. git rerere could be potentially useful here.

Even more importantly rebase allows you to resolve conflict at individual commit level. During conflict, you can see the exact commit that is causing it, making it much easier to resolve it.

See: http://jeffkreeftmeijer.com/2010/the-magical-and-not-harmful...
The Airport Test (How to Ace That Interview)
Totally, hence we see startups from the U of Calgary and the Missouri School of Science & Technology. Thankfully we're in a world where amazing founder can come from anywhere.
Microsoft doesn't really own the drivers. Microsoft just provides its DDK, then the hardware vendors who wish to include their drivers along with Windows are forced to provide the sources for the drivers in cause to Microsoft. Otherwise the drivers are usually made and provided directly, independently from Microsoft, by the hardware vendors themselves. Its safe to assume that the condition for using these drivers is something that has to make the hardware vendors happy (which is whatever sells their hardware).
> It is mostly people coming from SVN and only running CI on the trunk branch that favor the rewriting approach. It might be hard to let go.

You're being ridiculously prejudiced and jumping to conclusions AND throwing out judgements on things that by your own admission ("I don't get it either.") you do not understand.

Please realize that the correct response in such a case is not to double down, but to engage in a dialogue so you may reach understanding of which factors you're unaware of or they're unaware of, that create the difference in stance. (And no, you can't expect the other side to initiate the dialogue. The way you are talking you present an image of someone singularly uninterested in dialogue, even if that may be unintentional.)
My comment got a few upvotes, so perhaps there is more interest in this topic than I originally thought. I wrote an ebook "Job Tips For Geeks: The Job Search" a couple years ago that included a few tips on working with recruiters, but that wasn't the focus. I'll give it some thought, thanks for the insight.
Yeah the numbers don't seem to be quite correct. According to Wikipedia there are between 90 and 105 million native German speakers.
I really think we're dealing with some very complicated biochemistry here. I have never seen a single psych drug, the PI sheet for which did not begin, "The exact mechanism of action is unknown" (or words to that effect). And that includes very old drugs like Lithium.

Obviously, these drugs can provide relief for people suffering from various kinds of mental disorders. Most of them target serotonin, norepinephrine, dopamine, and a laundry list of receptors. Yet it still amazes me that no one can seem to draw a clear line between these chemical interventions and relief from symptoms.

Given all that, every piece evidence becomes potentially significant. But it also means a long, long slog through inferential statistics, patient self-reports, placebo effects, and targeted studies like this one that may fail to account for a thousand other factors.

I'm not a biochemist, but I think I would find this work both fascinating and very frustrating.
This has serious XSS holes which need fixing! Here is a PR that should do the job (not tested): https://github.com/idoco/map-chat/pull/1
No, it's not easy, it's a barely usable hack. Coding anything on a type system level is like coding in Brainfuck or Unlambda, while with macros I can use whatever fancy DSLs I already have implemented for nice, declarative compiler construction.

Can you stop in the middle of your translation from BNF to low level code and dump a bunch of nice .dot files plus a tex documentation for the grammar? No. Your type system cannot do it, and you certainly do not want to do it in runtime, it's something to be done exclusively in compile time.
The word "wet" is a technical term. If you spray a water repellent like Scotchgard on your clothes, they will become hydrophobic, and water won't cling to the cloth, nor penetrate its surface. In other words, hydrophobic materials are hard to wet. Waxy surfaces are also hard to wet. See "wetting" on wikipedia (not to be confused with nocturnal enuresis ;-).

Wetting is a verb. Maybe the title should have read "Daddy? Why does water wet?" That might have resolved the confusion, at the risk of angering grammatical pedants.
Yes, unfortunately that's the case.

There are a handful of commands described on http://www.quicklisp.org/ but there is no end-to-end, comprehensive user or developer manual.
I think the majority of people on our team don't like rebasing because it makes spelunking harder in some cases. But there are certainly people that preferred having some commits rebased so it was easier to revert them (reverting a merge is possible but harder). Although I'm not an active developer myself I think my dislike of rebasing everything is shared.
A coworker at my last job did something like that - he had been there several years, and asked to work only 4 days a week for 80% pay. I don't think he's ended up getting as much out of it as he hoped, though.
http://learnopengl.com/ is also excellent
The solution is for the official Google (et al) text to include a message about the real reason the code was sent, making it clear that the hacker's first text was malicious.
You need to have a lawyer involved from the beginning. It will ease a lot of pain. You need a good contract that will cover all bases.

In terms of bugs, make sure that the project is developed with tests. Most outsourcing places don't test anything. At all. Include it and make sure that whoever ends up managing this has a build server like jenkins where the tests can run on every commit. The PM should be able to read code and see if the tests are actually meant to do anything. I've seen projects were the tests were just code asserting types.
I'm not sure that's exactly an overblown characterization of SOPA. If you thought DMCA abuse was bad, SOPA would have ramped it up to insane levels.
Barbitrage
Here is how mustache.js[0] does it:

var entityMap = {
"&": "&amp;",
"<": "&lt;",
">": "&gt;",
'"': '&quot;',
"'": '&#39;',
"/": '&#x2F;'
};

function escapeHtml(string) {
return String(string).replace(/[&<>"'\/]/g, function (s) {
return entityMap[s];
});
}

also document.createTextNode will tell the browser not to render the children as html, whereas appending a dom element and innerHTML will.[1] I'm just assuming that behavior is correct in all browsers though.

[0]https://github.com/janl/mustache.js/blob/master/mustache.js#...

[1]https://jsfiddle.net/1dsygwoj/
Show HN: Blue Remote – Treat Your PC as a TV
Erm... your definition of "free" and "good" ought to be fairly unusual to believe that statement. I think the likelihood of a UK journalist to be murdered by the UK government is 10000x smaller than the analogous probability in Russia. As to "very good life" - while quality is subjective, the quantity of life the average Joe is expected to have (aka life expectancy) is certainly less than it is in the UK.

And to reply to a sister comment - you don't have to be gay to run into various trouble you wouldn't expect to run into in the West, though being one will likely make matters worse.
The problem is that things go from being talked about as a statistical correlation with a probability of error, to being a "link", to being the thing people base their diets and other philosophies on. The anti-vaccine movement resulted in a lot of people touting science as the reason you should trust vaccines, conveniently ignoring the fact that it appears to have started from a phony scientific study. The fact that the phrase "a new study ... has found exactly the opposite" can be published by serious researchers is exactly why we shouldn't be going around proposing that people be legally forced to inject themselves with things because they're considered scientifically illiterate. As Scott Adams said in his piece on the subject, "Science isn’t about being right every time, or even most of the time. It is about being more right over time and fixing what it got wrong." [1] That should be kept in mind by people who are publishing, reporting on, and reading these studies.

[1] http://blog.dilbert.com/post/109880240641/sciences-biggest-f...
Sure, but I guess I'd never reply unless I specifically had just requested a pass reset or something similar.

I get that this social engineering trick is like most others and preys on people who don't think about what they're typing or replying to, but isn't that the case with a lot of similar tactics?

If a malicious actor can trick someone into giving out a PIN or a password by impersonating their email host or bank or whatever, their work is relatively easy.
People who love rebasing and linear history tend to see feature branches, even if pushed to a public repository, as private to their creator and maintainer and fair game for any sort of rebase. In fact, we do consider rebasing of feature branches mandatory.
And then do you need the 'develop' branch at all? If not, you're describing something similar to what OP is.
XARA, deconstructed: An in-depth look at OS X and iOS cross-app resource attacks
I think the post was more about syntax, not standard library. Functions and methods are reasonable easy to lookup, syntax much less so.

Also try googling for some unknown syntax.
The Best of What's New in Swift
That's what I meant, it's O(n^2) for the words per paragraph I thought, not the entire document.
I call it BS. Women are mostly emotion based creatures. They are simply interested in other areas than men. They love the experience and the emotion from things..hence why they want to be translators, teachers and they study other kind of stuff we consider mostly useless.

It's like saying NBA is occupied mostly by tall people and that's troubling because short people are in disadvantage. We should try to stimulate the short people so they start playing basketball competitively.

Bullshit.
> Now try doing that in a loop that you want to break out of.

Fair point, although this can be worked around. Though it begs the question of why you need block scoping anyway. If you have a function large enough to need it, you should probably break it down into smaller functions, and compose them.

> It canonicalizes one of the popular ways of doing classes

But there are other popular ways, and this way new users will have the underlying details hidden from them, meaning they'll encounter problems later. It's also potentially misleading.

> { ... } in JS has never meant set literals.

Yes, but it's never been { a, b } - there's always been a colon. Python also uses {} for dictionaries, but with colons. Having { a } magically use the variable's name as a key name, and also use the variable's value, is unintuitive. { a, b } in another language would be an array (C, C++) or a set literal (Python, mathematics). Nobody would expect it to do what it does here in ES6.

> [] has also always been used to index objects and arrays, so using it when generating the object with keys and values follows as an extension of that.

I suppose that makes some sense, but we don't use [] for string keys in literals.

> Arrow functions capture lexical this, which method properties do not.

Oh, right, good point.
You aren't going deep enough. What are the roots of those problems?

Did the manager have a bias against women because they feel women are worse workers? What caused that bias and how can it be fixed (sadly, in some cases it can only be fixed in the younger generations... or maybe this is a bias I have against older individuals... and why would I have that).

Did the manager have a bias against women because a previous project was massively delayed when a woman took maternity leave and the temp replacement took so much onboarding work that they might have been better being a person down? How about changing culture so a later delivery cue to someone taking medical leave is 100% as acceptable as an earlier delivery (including the same end of year bonuses).

Did the manager have a bias against women because some of their male employees fear an instance similar to Donglegate and as such would be far less open to forming the same sort of comradeship that enables the team to run smoothly? What caused the employees to feel this way?

Did the manager have a bias against women because they are male and they fear for their own professional safety when conducting private one on one meetings with the opposite set? Why do they fear such and can that fear be removed.