skysight-inc/HackerNews huggingface dataset:
Let me try to straighten this out out loud:

(1) We develop sexual desire because we evolved to do so. Indeed without it we couldn't have evolved.
(2) Sex is essential for starting a family which is extremely beneficial for your physical and mental well-being.
(3) But too much masturbation/sex is bad for your physical and mental well-being.
(4) In particular sex can be an addiction which changes the way you view reality (up to and including preventing you from acknowledging this. People used to call this sin. Actually I think some of them still do).
(5) Yet telling people that sex/masturbation is sinful can be repressive and harmful.
(6) Unprotected sex leads easily to STDs (which in the middle ages were no doubt widely considered to be divine punishment).
(7) Education is a vital means of preventing STDs.
(8) Yet talking about sex is generally consisdered rude.
(9) As is having sex in public.
(10) Yet sex addicts and religious maniacs think about sex all the time...

It seems the topic remains confusing half a millenium after the middle ages. Please don't take this as any kind of advice or political statement.
I am a posteo [1] subscriber.
Superior set of features [2] (privacy, security, encryption), runs on green power, no ads / tracking, groups in address book, nice staff -- for 1€ per month.
Also supports mandatory TLS transfer (or doesn't send the email), if wanted.
Couldn't be happier since ~5yrs!

[1] https://posteo.de/en
[2] https://posteo.de/en/site/features#featuresprivacy
this is going to fail because blockchains solve this much better.
Every point in the list of data cleaning tips removes contextual information that may actually help models learn. I'd be careful with applying this advice blindly.
Increase salary over a certain point has decreasing marginal utility. Where that decreasing marginal utility is, is based on the person.

In the last 6 years. I've had two major bumps by changing jobs - both 20K. The first 20K made life a lot easier on our family. Allowed us to buy a house the size we wanted in the neighborhood we wanted. The 2nd 20K helped us be able to save, pay down debt aggressively, help our older son who is just starting out on his own. The path to making another 20K bump would lead to either contracting (would probably mean giving up my flexible schedule as the dev lead), consulting (a lot of traveling), or middle management (no interest in giving up actual hands on coding). The first two options aren't something I want to do until my son graduates. I never want to do the third options.

If I was forced to make the same choices to get the first 20K bump, I would have, the second bump, maybe. But I'm not willing to do that now.
an alternative: http://recordit.co
“Hide N Seek” IoT Botnet Using Custom-Built P2P Communication
> No one is putting a gun to these people's heads and making them do these tasks.

...mainly because the ones who refused were fired or let go to make room for those who won't.
But why was it so short?
Any way we will see an update which allows us to capture 'only' a specific window. ie recording terminal session for replay?
Meltdown doesn't involve speculative execution across branches. It is out of order execution through instructions that will fail.
I have a mild critique of this: Small teams can get a lot done, and there certainly is a diminishing return per extra developer on any team, but most development isn't slow because it has too many people but rather the problem being solved has become large enough that a small group can't keep all of it in its head.

Eventually, those three programmers have built so much that even with their productivity, their entire time is spent on maintenance. Replace 3 with N programmers, especially understanding the diminishing returns.

Then take into account that if one experienced programmer leaves a small group, picking up that domain knowledge takes a significant amount of time. While having a team of 50 makes each engineer slower, it means that losing one or two isn't a company-altering event.
Space burials [1] are a thing. When I investigated this, I found that in Germany the cremation industry is against separating remains, i.e. don't bury a part on Earth and another on the Moon. I'm not aware whether a legal background exists, but at least some might consider it as morally dirty (though I doubt people would really complain over here, but in other cultures people might react stronger). So it depends on your country (culture, jurisdiction) whether it's a viable business case.

[1] https://en.wikipedia.org/wiki/Space_burial
Fiverr acquires AND CO, maker of software for freelancers
Research prototype tool for modular formal verification of C and Java programs
Visualise content of a NES RAM – wall art from old games
> If they committed their dabbling, that is almost certainly on top if you go to the commits screen.

If they committed their dabbling right, and the default branch is still master, it will be in another branch, possibly with a PR attached. It's certainly possible to use a fork master directly, but I think it's a quickly learned lesson to only use a fork master for upstream tracking. (How far behind a tracking branch like that is can be informative, sometimes.)
It may be you simply don't have time to do all your work. If you're continuously interrupted for code reviews and interviews and so on, you won't get uninterrupted time for coding.

So you can choose to say "I don't have time for coding, this is more important", or whatever method of prioritization you can come up. And/or get your company to hire someone to take some of the load off of you.

Or: you need a (very long) vacation.
That was long. Static fires of Falcon 9 rockets at the Cape and VAFB are normally 3 seconds.
Someone should build a wifi-enabled touchscreen shower door for saving shower thoughts to the cloud.
I wouldn't say they're broken, they're bloated. When you build something that has to fit the multitude of Fortune 500 requirements, localize to 200 countries, you'll end up with a lot of complexity that is unnecessary to most users.
Selling Airborne Opulence to the Upper Upper Upper Class
I hardly ever write comments for code I write. My philosophy, which I took from Uncle Bob, is if code is so complex it needs commenting at a statement or method level then it's too complex. Simplify the logic, put complex clauses or statements into meaningfully-named functions (which you can test too, so win-win). But don't rely on comments to explain your code. Your code should explain your code.

Only "overview" comment blocks for entire files, which describe the overall purpose of the class or module, are useful to me and my team.[1]

1. https://softwareengineering.stackexchange.com/questions/2857...
I'm just saying that the way compensation is determined currently (primarily per tech stack and years of experience) doesn't seem to have a good effect on the industry as a whole. It encourages rushing into "hot" technologies, and discourages sticking around with a single company and project for more than a couple of years. I think companies have to start taking into account the possibility that the value of certain classes of employees (like software developers, for one) to the organization might drastically increase without that person learning any new skills.

If I'm making $50,000 as a developer at Company X, but I know that other developers using the same tech I do at other companies are making $75,000, what are the chances I'm going to get a $25,000 raise from Company X? Probably nothing. But the chances of me getting myself a raise by switching jobs are pretty good. Likewise if I know that developers using Tech Y are making $100,000, I'm going to try and get my company to adopt Tech Y, regardless if it's good for the company or not. Then, once I know enough about it to impress an interviewer, I'm gone. I have a theory that this dynamic is behind the phenomenon of new techs coming out of Silicon Valley suddenly becoming extremely popular and then causing huge waves of buyer's remorse.

My observation from working in this industry for 10 years, is that the true potential of software is not unlocked until it's been in production for at least 3 years. This is a bit of an oddball view of mine but I believe it's backed by research. 3-4 years is around the time when the developers are familiar enough with the requirements and the code to make big, bold plans and execute on them. But usually that doesn't happen -- usually, the developers who created it leave before then for greener pastures, and the new folks who come in have zero context on the decisions behind the original system. So they try to rewrite it, repeat all the original mistakes, and maybe even add some new ones.

The easiest thing companies can do to fix this is just get more aggressive with counteroffers. If a developer quits, ask them how much they're getting and then match it. Counteroffers happen all the time with new hires, but rarely with existing employees. It should be flipped; companies should try harder to retain than to hire new.
A photophoretic-trap volumetric display
I'm thinking of building a blogging API as a Service (kind of like moltin but for blogging instead of ecommerce).

Would anyone be interested in that?
The good news is that the announcement calls out FHIR which gets rid of the pipe and carrot format for json or maybe xml if you must.

It’s not beautiful, but definitely easier to debug - https://www.hl7.org/fhir/patient-example.json.html
Just in case there's any ambiguity - and it doesn't take away from the obituary - she died in November.
I occasionally interview candidates for a small software team (less than 10 developers). When evaluating a candidate's GitHub account, I look for any non-forked projects (projects that they created/own), then I look at the structure, code, documentation, and commit history of those projects.

At that point, the quality of the project can either help or hurt the candidate:

- The most important thing is that whatever project content they have, it is understandable. The ability to write sensible code that follows conventions and is well-documented (in code and commit history) is highly desirable.

- Ideally, they'd have an open source project with recent releases, issues, milestones, contributors, PRs, etc. (basically all the signs of a healthy open-source project). If they had this, then they'd be way ahead of most candidates.

- It's easier to evaluate docs and commit messages than it is to evaluate code quality, but I do try to pick out a few files and have a look to see if they make sense.
'Floating 3D printing' brings sci-fi-style projections closer
How would that work with a company like Qualcomm, that doesn't sell directly to consumers, and whose products are embedded in devices manufactured outside the EU? Technically, wouldn't it only be doing business with Apple?
I'm wondering the same thing. It seems to me that people who have classified information that shouldn't be released to the public shouldn't be put in a position to have to lie about it under oath.
Top JavaScript errors and how to fix them – data from 1000 real-world apps
Chronicle Security, a Google X Cybersecurity Moonshot
I'm not sure what you mean by "readable line breaks". Segment terminators for HL7 V2.x messages are clearly defined in the standard and done the same way by all major vendors. The standard is also quite clear about how to represent visual line breaks inside formatted text reports.

HL7 V2.x messaging is a bit of a monstrosity since the most common ER7 encoding is based loosely on old EDI standards. There is also a standardized XML encoding for V2.x messages which is a little easier to parse, although it's poorly supported in the industry and the schema doesn't really follow XML best practices.

The HL7 standards body has developed many other standards including V3 and FHIR (which is effectively "V4", it just didn't get a new version number in the same series). Most vendors and provider organizations are now moving toward FHIR since it's based on modern open Internet standards and somewhat easier to implement.
I think he kind of fell off-topic there, too. I interpreted it as a very non-sequitur dig at Steve Jobs. Either way, not relevant to the conversation.
I have stopped reading anything in Medium because I cannot save the page for offline reading using the Evernote Webclip browser extension.
The obvious problem is that Debian is not in a position to demand https support from the companies that provide them with free bandwidth.
This was an interesting read, but when I read sentences like "The words it picked up look much more relevant!", I'm reminded of the XKCD explanation of machine learning: https://xkcd.com/1838/
This seems to be targeted towards people who want to make living out of it. My personal conviction is to write for myself first, and develop my own thoughts and not rely on it for commercial reason, but to clarify my thoughts, and develop communication. Aiming to make money of it results in a different type of writing, imo.

Here are some more thoughts I recently wrote on a related topic:
http://dimitarsimeonov.com/2018/01/24/on-hungry-artists-and-...
gRPC in Unity for all platforms
Looks like HN loves to shit on Gitlab.

I will chime in with my experience. As a small startup, we have been using gitlab.com with a private CI server for over a year now. The UI performance has _most definitely_ improved. And their deployments do not cause outages anymore.

Great work team !
"It seems the bigger a company gets the more they favor predictability over excellence."

In addition to the reasons other comments have pointed out, this is likely economically rational. If a startup does nothing, they die. If they do something but it's not excellent, they die. Thus they have a strong incentive to do something excellent even if they have to fail a lot of times beforehand.

Whereas a big company is already doing something that's working and bringing in billions. Just by regression to the mean, there's a good chance that anything additional they do will make things worse. So they have a strong incentive to be conservative and protect the golden goose rather than trying things that may work out well but have a chance of harming the brand or business.
Hot startups in Silicon Valleys should take notice. You know who hired hundreds to thousands of engineers in a year or two, when there were really not that many significant engineering challenges. Productivity and morale dropped after certain threshold. Chaos and unhealthy dose of politics ensued. Yeah, really fun stuff.

If we look back, Google made really good decisions in its early days. Founder's bill is a brilliant invention, thanks to Eric Schmidt
I was thinking of https://news.ycombinator.com/item?id=16208095 and https://news.ycombinator.com/item?id=16192384 when I posted that. But you're right, your other history looks fine, so "a fair bit" was too strong—sorry!

The word is 'unsubstantive' and we use it to mean empty comments that lower the signal/noise ratio here. The idea on HN is if you have a substantive point, to make it thoughtfully; and if not, then simply to not comment until you do.
Thanks! I totally hear you about the menu bar. I used to laugh at Windows machines with all the crap in the system tray, and now look what I've become.
bag of n-grams can help here, but yes you will still run into a wall quick if you require phrase understanding or context.
Curry spice turmeric boosts memory by nearly 30%, eases depression, study finds
Uber CEO calls for new ebenfits system for gig economy workers
Java Microbenchmarks
I Answer the Frequently Asked Question: What Do You Do All Day?
I hate Google Sheets. Pasting X lines cause it to complain a minute later that "You don't have permission, and changes might be lost". Ok fair enough... I will just import the whole file... "the file is too big please delete some columns or rows".

We aren't talking gigabytes of data. I can't wait for these shitty cloud services to be replaced with something a bit more capable than pre 1988, whatever form that takes.
Argentineans have similar sayings and attitudes. The one I find the most amusing is "God's omnipresent, but he serves his appointments in Buenos Aires."
I'm not trolling you - but yes I am that heartless. This could have a lot to do with upbringing, but mine was full of analogies of humanity to nature. One of those was a firm belief that there is no "safety net" to catch me or my family. If I succeed, they succeed - if I fail, then we all fail. Everyone is responsible for themselves.

Everyone's particular set of values will vary, but that is mine.
I always thought the Eddingses threw a bit too much energy into the "love conquers all" trope. But I still concur.
Timer-based debugger detection
I wonder the same about pharmaceuticals too. And even in a way.. spacex did a similar thing.

Big ventures become superstitious, too many agents know a bit, nobody understands enough to move things. That's how it is in space or airplane. They live on a fragile thread, they can't afford to change things, the knowledge is in the product somehow, not in the employees.
My 1st grade teacher was an abusive alcoholic, so if I ever found that out I would have laughed and called it poetic justice. That yours was a nice person but maybe not great with money just means you should be sympathetic.

As far as data terrorism--I noticed on some bs website that had my info that it also showed an incorrect political affiliation and now I wonder how many potential employers searched for me, found that, and immediately developed some sort of bias about me. Ah well, I didn't want to work for any a-holes that would consider my politics as a fault anyways.
Show HN: Log middleware for express server traffic to file
First, there are two sides to every story. And QCOM is already facing regulatory heat in the USA.

Second, QCOM has already been fined similar amounts for similar behavior in China and Korea. Any regulatory action by the USA has to keep in mind the ramifications of subsequent such action by foreign governments. That is to say, there is an economic incentive to let QCOM keep bullying manufacturers, because they are a US company in a largely international market.

Personally I think AVGO is nuts for wanting to buy this company. Without their bullying behavior in the licensing sphere, QCOM would be worth a fraction of its current price. They are majorly vulnerable here -- take a look at any regulatory filing from the past few years and you'll see that the lion's share of their profit comes from licensing.
>> "enjoyment is subjective" and "who is the critic to judge,"

> ...are both valid positions and ones that I hold axiomatically true.

Maybe in some cases, but I don't think it's correct axiomatically assume every repeated behavior labeled as "entertainment" is one that at least someone "enjoys."

> there exist people who find the same level of "happiness", "enjoyment" and "joy" - broadly defined - from slot machines as from any other activity.

I think that's an assumption, and I'm pretty skeptical of it, personally. I have not doubt there are people who genuinely enjoy other types of gambling (e.g. poker), but I doubt slot machines are anything better than an expensive distraction. They're just profitable Skinner boxes [1] that use variable-ratio positive reinforcement [2] to attempt to create a lasting habit that's resistant to "extinction" [3].

[1] https://en.wikipedia.org/wiki/Operant_conditioning_chamber#C...

[2] https://en.wikipedia.org/wiki/Reinforcement#Simple_schedules

[3] https://en.wikipedia.org/wiki/Extinction_(psychology)
I hadn't realized this was going on until today. Makes sense with the stock all getting absorbed by cryptocurrency miners. It is a problem that needs solving though, because it's turned the DIY PC building market on its head right now (for those that need a solid GPU)

I was looking in the used market for a 1060/1070 to get some ideas of what I need to budget for them and noticed the prices in used markets had jumped significantly. Seems like I'll be holding off for a while longer before making any purchase.
"Euvoluntary exchange" is one of the most important ideas of our time. I think an understanding of euvoluntary exchange motivates one to focus on the root cause of a worker having poor alternatives, and not the perceived injustice of a particular opportunity available to this worker.

"The confusion that arises in judging exchanges that are not euvoluntary is understandable, but unfortunate. The observer, seeing the degree of inequality, or desperation of one of the parties to a potential exchange, is actually perceiving a disparity in levels of welfare of the respective BATNAs, or “Best Alternatives to a Negotiated Exchange.” This disparity is a consequence of differences that come before exchange is contemplated, and are not caused by the exchange." - Mike Munger

http://people.duke.edu/~munger/euvol.pdf
> It seems the bigger a company gets the more they favor predictability over excellence.

This is one of the key themes of the book "Seeing Like a State". It describes many efforts by states to regularize their populace and make it "legible".
This makes sense. Years ago when I worked in fast food, I noticed that about 30 minutes into my shift, I'd constantly tap the side of the screen when taking orders because the rate of tapping necessary to keep up with people talking would keep my hand moving quickly, then during the pauses, I'd find it difficult to hold still.

It's actually not uncommon and you can probably see someone do it next time you walk into a fast food joint.
Chances are most people are reading this story on a phone that costs $200 to make and sells for $700.
From your timesheet I see that there are more people taking more than 20 days off, than not. This seems to contradict your premise..?
Minor suggestion - would be nice to be able to rotate map to align street grid (eg, NYC) to top vs true North as used.
Apple who had root able to use on a Mac with just hitting enter a few times is not very encouraging to protect my health data.
That scary because in all the repositories I've made public so far, I always have a private version with the full commit history and start a new public repository when I'm comfortable publishing it.

I don't even know if I could do it another way because at the early stages of a project I tend to leave a lot of junk in the commits that I wouldn't want to be public :/
I never made that claim, and you're ignoring investment gains.
How much space does it take up?
It is using JSON (or XML), but the underlying data model is largely carried over from V3 (or more specifically, the RIM). The problem with HL7 isn't the data format itself, but how information is encoded and the amount of variation that exists. The parent comment was a little misleading in posting a V2 message since that isn't what Apple is using, but as someone who works with HL7 on a regular basis V2 is actually more straightforward to work with a lot of the time.

FHIR is definitely a step in the right direction but it is plagued with the same issues as their other "standards" so I'm not holding my breath.
Hold that P.R. there. Apple will sell your data out when compelled [1]. This is NOT a technology problem, it's a policy issue. And Apple isn't immune to governments & greed.

[1]: https://www.nytimes.com/2018/01/23/opinion/apple-china-data....
I could act like Richard Stallman, and refuse to run any JavaScript. That doesn't sound very appealing, though. I would argue, however, that we need a culture shift away from JavaScript.

As far as verification goes, if authors use a GPG private key to sign their code, and distributors (package maintainers, etc.) do the same, they can be "verified" by the web of trust. That verification could also be hardened by a third party certificate body, although I'm personally wary of letting certificate authorities decide which code I can run on my computer.
Wont start. Dont know if it has anything to do with me being on mobile.
I fully agree.

My biggest regret today is that there’s not a 2nd device that I almost always have with me for doing 2FA. Watch may become that, or maybe there’s a future for jewelry.