skysight-inc/HackerNews huggingface dataset:
Congrats guys! Very excited to see what the future holds with your powers combined.
My font package is not. I am curious as to why would that be. Can you give me a hand with that?

https://github.com/rbanffy/3270font
I think I agree with him at this point. Which is a bit sad. 12 years ago I went into academia because I wanted to do self-driven research, but then I realized academia isn't a good place to do research unless you are at the top of the hierarchy.

Then ~6 years ago I tried starting a startup, working for startups, but as Kay points out that's not a great place to do research either. Really, you need to be ruthlessly market- and production-focused.

So I guess my first two guesses for where I could do my own research were wrong. My new theory: The best place to do research is in your garage.

Let's see if I still feel the same way 6 years from now.
The Impostor Syndrome [video]
A Unified Theory of Randomness
While exciting news, with an interesting, counter-intuitive finding, that is a horrible (though accurate) title and worse article.

Here is the original story: http://bigstory.ap.org/article/f7e66079d9ba4b4985d7af350619a...

and HN posting: https://news.ycombinator.com/item?id=12210772
The message send is actually an object in Smalltalk.

So, in process, out of process, to another box, this shouldn't matter.

For performance reasons, all kinds of optimizations are present.

In Pharo (http:/pharo.org), which is "Smalltalk inspired", there are new developments like the remote debugger:

http://dionisiydk.blogspot.be/2016/07/remote-debugging-tools...

It is based on Seamless.
Of course it is.

In many languages that don't have microthreads baked in, this is not straightforward.

You either have to use OS threads, which have a way higher overhead in memory and context switching costs and are not trivial to get right. Or you use some async IO framework with callbacks or the event based OS apis directly, which is also FAR from trivial to get right.

Do you really want to think about memory fences and context switching when writing concurrent code? I don't. Of course you should be aware of how it works underneath though.
This. Negotiating a compensation package, in general, is asymmetric information warfare. Having to reveal your salary history you may as well not even negotiate.

I know so many women who are constantly bit by this and negotiating in general. Here's an idea: compensation agents who negotiate the compensation package on your behalf. Athletes and actors have them, why not everyone else?
Exactly. You have to trust the owners, management, admins, any maintenance staff, hardware, OS, VPN, and distribution of it & updates to you. Oh yeah, the jurisdiction matters too. ;)
There's another solution: Avoid closed source applications and closed source OS.

There's other OS besides the ones you mentioned. And there's other small form factor computers besides mobile "phones" sold by telecom companies.
There isn’t anything magical about it: Why more millennials are avoiding sex
They are also wrong since MA still has one of the tech centers in the US...

I do agree that banning non-competes would be good.
Awesome! Love it.
They spent an entire weekend on their corporate rebranding. How long do you think they should have spent on security?

http://adage.com/article/digital/marissa-mayer-yahoo-s-logo-...
If you want to be a friendly explanatory writer:

1. Adopt the inverted pyramid structure. This means to front-load your conclusion, to put the summary sentence first. In other words, if the reader stops reading at any point, they know the answer, at least in outline. Continued reading just results in more and more detail, more and more zoom-in.

2. Read The Elements of Style (100 pages) or On Writing Well (just need to read the first four chapters) or both. Both are short. These will help you word things efficiently. This doesn't mean you're leaving things out. But mysteriously human language is like computer languages in this: there are infinite ways to write something, and some ways are shorter than others --- shorter by several times!
Kind of stumped me. Good - they've got a new theory, bad - still no treatment?
Sadly it doesn't say anything about motivation. First instinct with Microsoft is that it is probably a dk move. So some explanation would be great. Oh well, let's see how it develops.
Curious how this would have worked with create-react-app?
It's certainly unfortunate, but "ridiculous" is a bit much. It's just a fact of history. FF is based on a very old codebase, before sandboxing and multi-process arch. was a thing in browsers. Chrome is much younger, and was designed with those features in mind. And while IE is also an old codebase, MS can devote far more resources to making these complex changes than can Mozilla.
well, that settles it then!
Thanks for the link. I'm actually under the impression that the situation in Haskell will be changing in the near future with the project called "Backpack"[1][2], which Simon Peyton Jones and Simon Marlow are both involved with.

[1] http://plv.mpi-sws.org/backpack/
[2] https://ghc.haskell.org/trac/ghc/wiki/Backpack
Have fun programming that in most languages, especially if you're doing some non-trivial combination of IO activities. Haskell's runtime allows you to program in a convenient and clear threaded style and automagically takes care of efficient polling and dispatch and such.

If you want to write a web application in around some giant epoll loop, more power to you. Have fun with fairness guarantees, buffering, ensuring that connections don't time out because you're favoring certain connections...
Completely agree. This is one of the things I really like about the book Functional Programming in Scala, which builds from the ground up. I haven't found an equivalent book in Haskell.
I like reading physical books, but don't like writing directly on the pages. Does anyone have a good alternative?
Hi all. I'm one of the creators of Noms. Happy to answer any questions!
I found the docs useless. I found earplugs helped a bit - they can prevent further damage and allow the body to recover.
I've never had any of these issues you've faced with Docs and I've been using it for over 6 years.
Copyright includes exclusive rights to determine use and distribution of a work of art. That means copyright owners may determining how their work is distributed, including requiring the bundling with other approved works for combined consumption.
"We want you to join us for the mission, not for the money. Be a team player and share your salary with us!"
Wrapping up with my first novel now. Very much fell into the gardener/pants faction. I had a concept "start up guys can't raise money so they sell cocaine" and just let it unfold from there. Any other fiction folks here subscribe to the planning method?
> Here's an idea: compensation agents who negotiate the compensation package on your behalf. Athletes and actors have them, why not everyone else?

I'd definitely be willing to pay for something like this. Make it commission based (pay as a percentage of additional salary negotiated) and the incentives between the negotiator and client will be perfectly aligned.
Unless you are writing your own, all the major game engines support multiple graphics apis anyway.
This is perfect. I wish I had known about this last week. I was volunteering for an event that my work place sponsored -- It was a "girls who code" thing, and I was helping them with HTML and they wanted something like this. All the ones I found didn't work out of the box.
I don't think you understand what you're complaining about. Each browser has had different types of sandboxing. IE's approach is to run the whole process (just the one) in PE mode. Chrome goes a step further and sandboxes each tab to its own process. Safari just sandboxes plugins. Firefox, prior to Electrolysis, sandboxes JavaScript, Media Playback containers, and Plugins. Post Electrolysis it does processes as well.
I've called out both Lavabit and jurisdiction-first claims on Schneiers blog repeatedly with similar points. I totally agree with this comment. That other companies were actively selling secure messaging or email services that avoided Lavabit's foolish design just supports it further.
Just got 'facebook-backend' lol
Or literally any statically-typed language I know of after C. I suppose it's possible there's some language I'm unaware of that has managed to somehow provide less type-checking than Go, but it's certainly not a commonly-used one.
Location: NYC

Remote: Some level of remote-friendliness preferred

Willing to relocate: Yes, if relocation expenses are provided.

Technologies: Ruby, Rails, Javascript, Node, Angular, React

Résumé/CV: http://bit.ly/1OuneZB

Email: neill@nbolt.io

------------

Hey all! My name's Neill. I'm your local linux enthusiast, web developer, cyclist, travel bug, anime fan, serial entrepreneur addicted to making cool stuff with awesome people.

I'm an experienced full-stack engineer and have been working with various companies and startups over the past four years and have taken on roles that include quality assurance engineering, frontend web development, mobile development, backend / database work, linux server administration.. if you have a vision I can own development from front to back and make it happen.

I'm always on the lookout for awesome workplaces with strong, engineering-driven culture to connect with and possibly be a part of and help grow. I learn very quickly and am always excited for whatever comes my way.
> Athletes and actors have them, why not everyone else?

Largely because the compensation changes are both rare enough and small enough that hiring someone to negotiate on your behalf isn't really worth the money for either side. Paying enough that the negotiator would be able to pocket a decent amount of money would probably not be viable.
Peter Thiel, literal vampire.
> I know so many women who are constantly bit by this and negotiating in general. Here's an idea: compensation agents who negotiate the compensation package on your behalf. Athletes and actors have them, why not everyone else?

Because most other workers aren't, even with an agent, going to get paid enough more to make it worthwhile to pay a competent agent to negotiate on their behalf.
That's why the measure comes across as empty pandering. (Hint: you can tell it's pandering because all the rationale is gender gap bullshit instead of the job application process being shitty for everyone.) If Massachusetts really wanted to improve the strength of employees with respect to employers, the legislature would do things like ban non-competes, ban non-solicits, clarify IP assignment rules, and ban mandatory binding arbitration clauses.

But what do we get instead? Identity politics pandering.
Isn't that basically what a recruiter does? Every time I've dealt with a recruiter, they've done the salary haggling for me.

EDIT:
I should point out that that's what they do in regards to full-time W2 work, not contract.
> I cant even understand why they would not just make it mandatory to reveal the salary range of the position at the beginning of the interview process.

Something of this nature would lead to the 'bait and switch' by companies with shady interview practices. Interview a candidate for a position with a $150k posted salary, then make an offer for a different position that is $100k and the company has deemed a better fit for the skill set.
because an athlete giving up 20% for someone who will fight for millions of dollars more is a lot different than janice in accounting giving up 20% to get the bump from $52,000 to $70,000.

you're all idiots.
There's probably something to the fact that it's biotech first, government contractor tech second and software startups third, though. Those employer-friendly and IP-friendly laws work a lot better for biotech's long product cycles and government contractors.. whatever it is about them.
This is desperately needed in the UK, the recruiters (external) here won't even let you proceed if you don't reveal it.
"Anon, I suggest you start flossing more regularly to clean debris in-between your teeth"

"No thanks Mr. Dentist, an article I read on the internet said that is dumb :-)"

https://www.youtube.com/watch?v=YWdD206eSv0
Well if this Nietzschean quest for superman immortality doesn't work out, I recommend reading some Sufi poetry to help come to terms with the passing of time. Future generations will just have to find other exemplars of libertarian smugness to look up to.
Why the hell should the authors rename their stuff just because Qt came along an named something QML years after this project?
Depends on the type of book and the copyright holders intentions for their work.
It makes me sad how accurate this is.
That's a very particular amount!
I never understood why they couldn't just give people the option to retain the chronological sorting.. It can't possibly be that difficult to give users the choice.
I would say the easiest way to check is if actions match the talk. If ideals are altruistic, then margins and prices should reflect the same. You cannot have 2x margins and claim your goals are idealistic.
> Athletes and actors have them, why not everyone else?

It's a simple matter of supply and demand: https://medium.freecodecamp.com/why-talent-agents-for-engine...
Chance to work with Mike Hearn and the R3 team? This should be top of the page.
It doesn't contradict what I said above. Supporting multiple APIs is a burden, whether it falls on those who write their own engines, or those who write those engines for others to use. You can view it as a tax which increases costs and reduces efficiency. The point of lock-in is exactly such tax, which will deter some from using anything else, or at the very least make it more expensive for those who will use something else. This tax is passed to the end user either way, in the form of slower progress, higher prices, unavailability on other platforms and so on.
Blood doping works: https://en.wikipedia.org/wiki/Blood_doping
> why not everyone else?

because you haven't built a startup to do it yet, and Gayle McDowell hasn't figured out how do it yet.
Appreciated, especially since the site is quite unusable atm.
Good. To be honest asking about previous salary is offensive, and only helps employers take advantage of employees who aren't tactful enough to refuse to answer.
The first Bourne movie did something similar.
Developers are just another means—we're not wizards. We are a commodity, and if you don't recognize that you're in for a hard midlife crisis. Do you really expect to make any money without taking the risk of deciding what to build? How it's constructed is a (admittedly time-consuming and distracting) detail—only a small aspect of the company's value.

Risk and comfort are tradeoffs. If you want to live without risk, you'll have to be satisfied with whatever salary you can negotiate as a commodity.
The Price Is Right: Essential Tips for Nailing Your Pricing Strategy
This is so needed in California. My past personal experience and my friends' experience in the Bay Area shows how hard the recruiters can push for the current salary. What they are saying is that we will give you a 10% raise from your current salary, but not what you and we can agree on is your market price. This is so against letting the markets figure it out.
I'd look at ant species rather than ants.

Note that ants don't directly compete for a niche with humans.

And megacolony species such as the Argentine ant are displacing other ant species.
There's a common saying "Nobody ever gets rich working for someone else". I am not sure how much that is backed up by any statistics but the Bay Area and employees of unicorns or Google/Apple/Amazon/Microsoft/... may be outliers to this adage.

Anyway the point I am trying to make is that as an engineer you either have the choice of working for an employer and living an albeit comfortable life (without any risk) or going it alone or starting your own venture with all its associated risk/reward profile.

You have already indicated that you believe in this adage and took the necessary steps to increasing your worth and would continue to take the same approach in future.

What somebody is worth is what the market is willing to pay for them either in salary or by investing in their venture.
When I say all predictions, I should have quantified it as 'all predictions used by policymakers'.

There are certainly apocalyptic models that have called for more warming then what we've seen. We aren't using them to set policy - we are using models that have been underestimating the impact of warming.
I'm assuming you're talking about third party recruiters, not recruiters that are employees of the company you're negotiating with. Yes, they do commonly do that, but they're only going to be involved if they've been involved since the beginning of the application process.
The malware known as PowerPoint has infected millions of systems worldwide and has cost businesses, NGO’s and governments untold billions in lost productivity. PowerPoint files seem to be self-spawning and capable of infinite replication in the wild. Small variations in the PowerPoint files forces administrators to keep endless permutations of these highly virulent files.

PowerPoint is often introduced into an organization by highly sophisticated threat actors using deeply customized versions of the software. McKinsey, BCG, and Bain deploy the PowerPoint malware to a multiplicity of customers whose human capital and infrastructure become mired in endless recursive loops known as PowerPoint cycles.

The actual introduction of PowerPoint is typically merely incidental to these threat actors ambitions. Most often they derive substantial portions of their income by reselling organizations intellectual property which they already own.

Once the organizations systems become bogged in ever more bloated PowerPoint files productivity plummets. Morale drops among employees and management often re-engages the threat actors to attempt to right the ship.

The PowerPoint Malware is seemingly unstoppable at this point. Any computers that contain it should be air gapped and protected by highly restricted physical access.
That article is about a different topic that uses similar words.
A Non-Technical Guide to the Technical Interview
>> a large ancient cemetery unearthed during the construction of a national opera house and library between downtown Athens and the port of Piraeus.

Typical. In most of Greece one cannot dig to plant a turnip without striking some relic of the ancient times.

It's not a joke. A friend's father who is a civil engineer has told me how the law requires anyone who digs for a house's foundations to report any archeological discovery to the authorities. Then all building work must cease until the archeologists come in, do what the do best, and finally give the OK.

Unfortunately this may take a very, very long time (20 years in one case known to my friend's father). This is because of the impossible bureaucracy in Greece, but also because there is very little money to carry out the necessary work.

As a result it is ...common that when something like this happens the person who has the house built will pay the builders something extra to cover up the finds and keep hush-hush about it.

I don't even want to think what treasures may be hidden under condos and summer houses.
I can assure you a typewritten letter, or should I say envelope, is a sure-fire way to have somebody open the letter.

It's interesting that you say that, as I'm a consultant who does grant writing for nonprofit and public agencies (see http://www.seliger.com if you're curious). We send fee quote letters via email but we also send snailmail letters that arrive a day or two later. Potential clients often make their decisions before the letters arrive, but sometimes those letters jar indecisive potential clients into making a decision, and sometimes those letters sit on their desks for months until another grant opportunity comes along. A physical letter and card are often easier to find and sort than voluminous email.

This might not feasible for high-volume businesses, but it's been very effective for us. The email follow-up arrives the same day, and the physical letter a few days after that.
I use post-its, and I let some of it stick out of the page in question to serve as a bookmark for important notions. Or if I need more space I write on a separate sheet of paper that I leave in there, at the risk of losing it though.
I'm sure this will inevitably happen with war casualties that were mass-buried with their dog-tags still on.

Or our pets, many of whom are injected with passive RFID chips. Assuming the vaccination database is still live somewhere, you could someday look up the name, owner, vaccination and vet history of long-deceased cats and dogs.
New Release of Dbbench Streamlines Database Workload Testing
$10/m? I must have really messed something up. I somehow got $150/m o_O. $10/m is much more reasonable, thank you
Aren't some BigCos a good place to do research? Have you tried that approach?
As a musician, I've recently started working with analog synthesizers. Digital synths tend to be very alienating devices, at least for me - you don't really program them, you just select a preset that sounds kind of like what you want. Software synths even more so. Then I picked up an Arturia Microbrute, and the visceral thrill of twisting knobs to get the sounds really turned me on! There are no presets. Want to repeat something? Figure out how you did it before, or put an overlay on the keyboard and mark it with ink to get the knob positions. And because knob-twisting is such a part of it, I find myself altering the sounds in realtime. As a guitarist, that sort of intimate tonal control is much more familiar to me.
But a good engineer will have a say in what to build, not only how to build it. Otherwise all dev work could just be outsourced. IMO, the role of a good engineer is to deeply understand the business/domain to provide good insight in regards to what to build.
As a side note, I've often noticed that the disclaimers in the pharmaceutical advertisements state the side effects in a slow, calm voice while the actor calmly walks though an abstract world which functions as a metaphor for living with the disease in question. In the end, the effect is that the listener stops paying attention to the words being said. The speed reading of the disclaimer is especially prevalent other types of advertisements though.
The only reason you really need is that the customer wants it done that way.

As I grow older, I become less enthusiastic about protecting other people from the potential consequences of their decisions. At this point, I will still warn about those consequences, but only so that my company will get contracted again later, to do the thing I suggested in the first place.

I: You could speed up this workflow by doing X.
They: No... It needs to look exactly like this paper form.
I: Your wish is my command.
[3 months pass]
They: We want you to change this form by doing almost exactly X.
Boss: [holds out hand, rubs fingers together]
They: [writes fat check]
I: Your wish is my command.
They: Just make sure that it still looks like the form when I print it.
I: [dying a little inside] Your wish is stu... still my command.
[3 months pass]
They: The printed forms are crap. We want you to export the data to an Excel spreadsheet.
Boss: [holds out hand, rubs fingers together]
They: [writes fat check]
I: Your wish is my command.
[continue in this fashion until your death]
I'm glad you mention that, because I just sent a letter to the editor about Unicomp's mechanical keyboards (https://jakeseliger.com/2008/05/07/product-review-unicomp-cu...), which are modern versions of the IBM Model M. If Hanks hankers for that sound, he'd probably like one.
Its really amazing
http://greenlahore.blogspot.com/2016/06/green-and-clean-laho...
Lost one Olivetti Studio 44 to a flood (and to a family member's insistence then that we get rid of it :-( Me: But, parts...!... ).

Got one remaining.