skysight-inc/HackerNews huggingface dataset:
This person is someone I would hire over and over again, but they are a private person so I won't out them.

About 5 years ago I saw someone post a project to HN. The project dealt with stock predictions, and wasn't really unique. However it was some of the cleanest hobby code, tests, and documentation I had seen a single person churn out for an experiment. I cold emailed them and brought them in for an interview the next morning. They were very shy and kinda confused why I was interested, but I felt something about this individual that I couldn't explain. Gave them an offer on the spot and they started the following week.

They were the model citizen of work ethic and quality that most of the team took their cue from. Over the years they left the company and I eventually rehired them. I would again in a heartbeat. Personally and professionally they grew so much while I worked with them, with a dedication to goals that I really admire.

I'll never forget that person I took a gamble on and saw a tremendous ROI on everything they touched.
If your type system is powerful enough (like in Rust), then you can use it to express relations in your problem domain and have compiler enforce them for you before the code even runs.

Example: https://blog.chain.com/bulletproof-multi-party-computation-i...
You need to make it transactional. Upload to a temp file name (something easily ignored by whatever backend processes are looking at the files) and then do an atomic rename once the transfer is complete.
Jeep, New Electric Upstart Join Pickup Pack
What is Federal Land?
A free gift like fire to mankind can be both great if useful and bad if misused. Just nature. And the being helped it forever have an eagle chasing his liver ... or he has to do the stone.
I think this implementation uploads it to memory before going to S3. It usually won't handle 20GB files (unless you have like 20GB of RAM) and in this case, were it a smaller file, it'll just never upload.

https://github.com/moriyoshi/s3-sftp-proxy
I am not a lawyer, but my understanding is that the text of the MIT license is a potential defense to a suit, it does not prevent one. As in I try sue you, you say, "But did you read the license?" I do, talk to my lawyer, and still decide to sue you. You tell the judge, "But look at the license!" And then it is up to the judge to decide whether it matters.

Therefore the issue isn't the license, it is the rules of the law in question under which the author is being sued.

Therefore your intent can matter. Whether a valid contract exists matters. Whether I can be expected to have read it matters. THAT THE INDEMNITY IS WRITTEN IN ALL CAPS MATTERS. (I'm not making that up - see https://law.stackexchange.com/questions/18207/in-contracts-w... to see that it does matter.)

The result? The indemnity in the contract can say whatever it wants and still only provides partial protection. The real rules are complicated and elsewhere in the legal system.
I have a rule I don't maintain software I don't personally use. It's kept me from picking up projects other people ask me to do for them, and it's been a good dividing line when it's time to hang it up. I think his major mistake wasn't advertising he'd moved on, and I feel badly for the heat he's taking.
I think if a company has good answers to these questions, then they aren't really a startup. More often than not, if they're hiring you (being quite senior) it's because they need you to do all those things.

But I do get where you're coming from. In my experience, it's better to ask about the team and its CTO to understand how decisions get made, and if the team is capable of recognizing quality. I don't care if CI isn't in place when I join as long as the team recognizes its importance and knows they need to get to it.
> PHP is a nice language but is having trouble keeping up with modern languages

It's only "having trouble" because it can't change its API from month to month to match whatever's in vogue. A majority of the web still runs on some variant of PHP, and that guarantees that it's not dying anytime soon.

More broadly, it seems the author wants to create a version of PHP that's not focussed on web requests, which is sort of the entire point of PHP.
Show HN: Golang kafka consumer group based on saram, compati with 0.8+
https://en.wikipedia.org/wiki/Mark_Karpelès
There are a number of other "free use" bands (called ISM bands). See wikipedia[0] for more information. Some of the most interesting ones are at 433 MHz (Europe), 902 MHz (US only, often used for old cordless telephones), and 24 GHz (worldwide).

We have microwaves to thank for the 2.4 GHz band (and maybe 900 MHz as well)[1].

0: https://en.wikipedia.org/wiki/ISM_band

1: https://web.archive.org/web/20160304061338/https://www.itu.i...
(see page 464)
May I message you ? I feel you can help and advice me about a difficult situation.
I would say it's be smart about it.

I use Ansible quite a bit. When I first started, based on some examples I found, my play books were pretty complicated, with a lot of conditional steps, doing things (or not) based on results of previous steps, etc.

What I found is that it's a lot easier to have a lot of roles that each do one little thing, and then use them in a play book as needed.

A role might be as simple as installing a package, templating a configuration file, or maybe even just changing just one line in a config file.

When roles are small and do just one thing, they are easy to combine in many different ways, and it's more obvious what's going on.
you seem to be tacitly implying that better outcomes will come from those government subsidized endeavors rather than the revolution happening in the same field from the private sector. if that's your claim it's a ludicrous one. major impetus were provided by government research -- most of which knew where to stop once visionary entrepreneurs picked up the ball and took it to the next level.
> developers are actively denied access to the infrastructure

As it should be. Devs make apps, Infra guys, SRE, make these apps run in production. Different skills, PHP vs sysadmin's work.
Did you read my comment? I know yours wasn’t there when I added that edit :)
I agree it will change - actually if this becomes medically responsible nothing needs to change. we just need to stop experimenting on humans. once the science is sound it becomes healing humans with gene therapy
Form back end platform for designers  and developers
So a JCL then?

The largest code base I worked on (a map reduce based billing system), also had for the time early 80's a fairly complex set of JCL that could compile and build all the systems module's on dev and also push it out to the 15-16 or so live systems.

This also handled all the glue that held together the map reduce.
When the map starts to reach the same size as the territory, don't you then need a map for the map? Pervasive monitoring sounds like one hell of a dataset to search through. Sure, you can use it to follow things you have already identified, but just because you have recorded something, doesn't mean that you know that you have recorded it.
It's annoying that consumers cannot opt out of these fees. I have Comcast, but use an antenna for ~30 minutes each day to watch a single show. The Xfinity Roku app is not ideal for viewing content.
What does it mean to have an npm publish event content be different than the source repo? Doesn't npm publish just "push" the source repo to npm?
Most unlicensed radio gear chooses between the 2.4GHz and 5GHz ISM bands. 2.4GHz offers longer range and better penetration of walls, but a lower available bandwidth (fewer/slower channels). 5GHz offers better bandwidth but lower range and less penetration. Perhaps 3.5GHz provides a happy middle ground for Amazon? Not to mention there is much less interference on that band because they don't have to put up with everyone's wifi, bluetooth, microwave ovens, etc etc.
Maybe this one will free some memory once in a while.
Server 2016 removes NTFS Permissions on PARENT folder when Child folder deleted
The blood sugar spike and trough (from eating recently) is what makes you feel hungry. So avoiding that can make it easier to eat less.
> The concept of code sharing—which is a good thing, this incident notwithstanding—goes all the way back to CPAN and Perl 5.

The concept is significantly older, but the implementation of a systematic facility for it rather than more ad hoc mechanisms may date from then. (It's a lot harder to sneak in and use an exploit in books of source code used in the 1970s-80s, though; convenience comes with a price.)
Breast implants study reveals serious safety concerns
Per 6 if they are in a cube though
First Gene-Edited Twin Girls Born November in China
do you know how many of your paid software contains a similar disclaimer that removes their responsibility for the damages caused by the software? Only you'd never have a chance to look at that code and find this injection...
3-5 years old with $100M revenue is deep into unicorn territory already. I'm sure you can count companies that currently fit those criteria on one hand.
But... why?

If you are going to write a go program to run PHP to use go specific features, why use PHP at all?
>Ultimately, you can't take dependencies for granted.

The problem is that JS dependencies are so modular that shifting the burden to vet your dependencies to developers is generally not realistic. Creating a new project with one of the current popular frameowrks will bring in hundreds or thousands of dependencies. Who can possibly vet that?

To compound things, this package could be a transient dependency of a transient dependency, so I may not even know the person who decided to depend on it in the first place, or the reason why, or what the package does.

It's not that people are taking dependencies for granted - it's that there is no reasonable alternative.
I saw it around the dot-com days along with a lot of other extremely dubious terms for extremely desperate founders - at least in NYC.

Agreed that more than a 1x liquidation preference these days would generally be surprising, but in a low end scenario or with a few big rounds, all it takes is a 1x to wipe out any upside for founders and employees, but if you're deemed worth it, the acquiring company can offer you a worthwhile incentive to stick around.
Then don’t do that. But CF at least now has drift detection

But what I prefer about CF is the “easy button”. If something weird happens or I can’t figure out something, I can use our business support plan with AWS.
Sure git is just git. I was referring more to the other features this PR piece is promising: Fast Code Search, Debug in production, Detailed audit logs.

I am curious how they relate to say Github or other services.

Also as a sidenote, the Quickstart link for Debug in production and Detailed audit logs is the same. Is it so for a purpose?
A perfect example of error handling in go in the wild:

https://github.com/MagicalTux/goro/blob/3cb3dfe0eef910c03e41...

More php interpreters is of course nice.
Except no one's proven that to work yet. For the same level of investment dollars, you'd be better off buying a mom-and-pop service company and throwing the software in there.
I disagree that CSR serves the same purpose as code.google.com, and is likely to meet a similar end.

code.google.com hosted public repos, issues, wiki, downloads, etc., and was generally just ripe for abuse. Google created it largely because Sourceforge was the only thing that existed at the time, and it wasn't doing a great job. Today there's GitHub, Bitbucket, Gitlab, and more.

CSR is primarily for hosting private code, shared among teams, and adding integrations with other Cloud services, in the Cloud Console. It also adds code search, which is pretty great. Hosting private repos, it's much less easily abused (it's not impossible). There are plenty of private repo hosts, and this one aims to be the one best integrated with GCP. It has, I think, a much better business reason to continue existing. It might not make money (I legitimately do not know) but it helps drive GCP adoption/usage, unlike code.google.com which didn't.

Disclosure: I worked on code.google.com, and helped turn it down, and helped create CSR from its ashes. I don't work on either anymore.
If you're interested, these slides are a cool introduction to the complexity of air travel:

http://www.ai.mit.edu/courses/6.034f/psets/ps1/airtravel.pdf

Edit: I missed that someone had already linked to them - https://news.ycombinator.com/item?id=18531203
Funny how so much is missing. I mean what does work?
The author misses the significant issue that this ultra-simplistic approach works only with the simplest USP businesses: established markets with a single environmental factor driving change and a single paradigm shift in response.

More complex businesses, blue ocean (new market) businesses, businesses combining insights from multiple trends or with multiple layers of innovation will find this approach completely infeasible.
>He had no way of knowing the person who took it over would use it maliciously.

Then it was, clearly, negligent of him to give it to this person. He gave a stranger the power to do things in his name.

He doesn't have to maintain the project forever - it seems like a much easier solution is: don't give away a project with your name on it to someone you don't know. Instead, encourage them to fork and release a new version under their own name. This is a surefire way to never have an exploit spread to thousands of people with your name on it.
Do you think people that are able to grow some, if not all, their own food and heat their homes with renewable wood is so wrong and inefficient?
I’m confused. How did he hit the ground running in C++ without being aware of new and delete?

Edit: also, how did he pass the interview
For completeness: there is also a 900MHz band, and 24GHz and 60GHz bands.

Microwaves I assume refer to ovens, which use a frequency related to the nature of the water molecule.

The 2.4GHz ISM band supposedly exists because commercial and military users didn't want to deal with interference from ovens.
I have to imagine there are people who could offer the same “hang out” accommodations and have little or no turnout.
Thanks, I thought this was new, and was kind of amazed that they were doing this again.
Not a thing in the US for private companies.
Personal attacks are completely unwarranted. I think a more useful (and certainly more constructive) way to look at this is to frame it as a learning experience and figure out what we can do to minimize the effect of this in future.

It's almost impossible to vet every sub-sub dependency of a large codebase without dedicating huge resources. Perhaps there needs to some sort of a javascript code signing standard that requires a level of user identity verification. This is a solved problem with Authenticode and Gatekeeper for executables on Windows/Mac. We have been able to hide behind the fact that we're devs (we know what we're doing!!), but many consumer-level applications (mainly Electron-based) now run node modules with user-level (or higher) permissions. Maybe we need to become a bit more diligent in this area and look at less ad-hoc ways of managing dependencies and identity verification.
It's the same reasoning used by computer enthusiast on why RGB led on any peripheral are now profitable.

The same reasoning for accessorizing cars to look like UFO.
It’s not procedural. You write what you want your infrastructure to look like in the case of CloudFormation yaml or JSON.

The first time you run your template it creates all of your infrastructure and is usually smart enough to figure out dependencies.

After you make changes to your template and run it again it knows based on the changes in your template whether it can modify the existing resources or whether it needs to delete and recreate your resources.
Thank you for sharing your story. I hope you don't mind if I turn it into a thought experiment, because I find it a good example of how tricky finding and fixing a problem can be. I know nothing about water quality standards, so they might be naive, but the following questions stick out to me:

* Is there a reasonable contamination hazard from water sitting in pipes that are flushed daily with chlorinated water? In other words, is it vital that there always be residual chlorine 100% of the time, or were the standards designed to accomodate this sort of periodic lapse?

* If the dips were harmless, would the inspectors be willing to accept that?

* Was the dump solenoid effective at flushing the entire network of pipes, or just the branch containing the sensor?

Depending on the answers, the end result could range all the way from "the new system let us eliminate a serious hazard", through "we were probably fine before but now we can be sure at a little extra cost", down to "now we have to waste water to avoid tripping a sensor so we don't get fined, with no actual improvement to the water quality". It's a great example of how what we want, what we test, and what we enforce can get just a little out of alignment, and make a hinderance out of what ought to be a definite improvement. Thanks again for sharing.
I recall hearing that sunlight sterilizes E.coli. Not sure what can be made of this. Here is an example of the claim from an article[1]

>In 1890, the German microbiologist Robert Koch (who had isolated and described the tuberculosis bacterium in 1882), showed that sunlight killed TB bacteria. Later on, research showed sunlight also killed E. coli bacteria in twelve feet of seawater and in waste stabilization ponds.

[1] http://sunlightinstitute.org/sanitizing-with-sunlight-the-be...
> That wasn't me who made the initial argument.

My apologies. I wasn't paying attention to the names.
Used large declared static array, make his own heap.

He was interviewed on stocks and bonds. Would have been hired probably even if he came clean about programming - we had no expertise in stock feeds and could have paired him with a programmer.
Interestingly enough, there are arguably better tax benefits towards capitalizing licensed software (Capex), instead of subscriptions (opex). I have a lot of PE clients who actually prefer CAPEX because it can make EBITDA look larger, but like the simplicity of OPEX.
> Just because corner cases cause problems doesn't imply we should do away with any attempt to identify anyone as anything.

That's a complete straw-man argument, no one is arguing for the complete abolition of gender categories. They are there, they are useful, they fit 99% of humans, and 99% of humans can be correctly categorized at birth. It's perfectly fine.

The argument is that legal gender shouldn't be compulsory or immutable.

As for sports, which still doesn't have anything to do with legal gender, it's obvious that trans women could have an unfair advantage over cis women in sports that require strength or reach or bulk, therefore they shouldn't be able to compete professionally as women. And for sports where there isn't any noticeable difference between genders, it's to whatever governing sports association to decide on their own rules, if they want to allow trans women - fine, if they don't - fine. Whatever.
Paradise camp fire aftermath interactive drone video and imagery
Am I crazy, or are bunk beds the stacked kind?

There is absolutely no reason for stacked beds to be queen size.

https://m.ikea.com/us/en/catalog/products/art/50269029/
I thought the most significant claim for intermittent fasting is the anti-aging effects through autophagy, not just weight control.

The study seems entirely focused on bodyfat.
The community discussion is focused on the wrong thing. Here is the problem:

https://github.com/dominictarr/event-stream

Look at that URL. It has "dominictarr" in it. Now click on the URL. Look at the big "dominictarr/event-stream" in the upper left of the screen.

Many are going to conclude that this package belongs to dominictarr. Almost everything in the UI indicates this.

Developers don't trust code, they trust people and organizations. NPM and Github needs to make it very clear when ownership has changed. And needs defaults that properly inform all users when ownership has changed. For example, when I SSH into a server the first time, it asks if I trust the key. Then one day, what if it asks again? Then I can stop and investigate why the key has changed, what's going on, and if I should trust it again.

With the current NPM/Github there's no warning to users. A developer could've checked dominictarr's background and decide they are trustworthy, which would then extend to event-stream as well. But where's the warning to users when ownership of event-stream has changed and they need to re-evaluate whether to trust the new owner? And why does it look like the project still belongs to dominictarr when it actually doesn't? Those are the key issues here.
meh. using python/node/etc hacks to manipulate env instead of containers these days just feels wrong.
Infrastructure is special - if I make a change to my code, it usually won’t kill a whole database, load balancers, knock out connectivity, etc.
He did spend some time in jail
You are misunderstanding what 'variance explained' means. It means 'variance', as in, average differences between individuals; nothing to do with the average effect size or possible maxima or anything like that. It refers only to predicting the net effect after, being distributed at population frequencies, most of those hundred variants have canceled each other out. In editing, the population frequencies & distribution don't matter, only the summed effect size of all the variants flipped. Confusing one for the other is like confusing waves on a beach with a tsunami: https://www.gwern.net/Embryo-selection#limits-to-iterated-se...

Since they have an average effect size of ~0.05-0.1 IQ points or so, a few hundred of those would in fact be many SDs. You can download the PGS, grab the top few hundred or thousand betas, and sum them if you don't believe me. (I show this with Benyamin et al 2014 in that section above, but no reason one couldn't redo it with a better PGS; the results won't change much.)

And yes, Hsu really does believe this, he is quite explicit in that 2014 paper that that is how it would work (in addition to countless places on his blog & Twitter) and I've discussed it with him in the past.

(As other comments point out, the real problem with this logic is that the hits are usually not causal but tag the causal variant, even if you had some magic CRISPR which could make hundreds of arbitrary edits. That's soluble, but not easily. It is, however, not a problem for selection procedures.)
Dependencies should be nailed to versions and upgraded conservatively. The default shouldn't be the latest and greatest, it should be the last thing that worked.
Users have to come to grips with the possibility that the "free" code they download might be malicious.

To mitigate the risk they have these options:

1 - Don't use the software.

2 - Audit the software themselves before they use it.

3 - Pay someone to do the auditing for them.

Even if they choose options 2 or 3, there's still a chance the some vulnerability of malware could sneak through (especially if they're getting a binary blob or source code written in a language like C that makes obfuscation easy).

But if they choose to use unaudited software, they're playing with fire and shouldn't be surprised if from time to time they get burnt.
This is a report by a recurring contributor to the publication which contextualises a news peg with other events relevant to the peg. Whatever your semantic disagreements with the contemporary tone of web-based reporting, this is textbook journalism.
This sums it up perfectly.
One of the most "hip to hate" languages implemented in one of the most "hip to love" languages...