skysight-inc/HackerNews huggingface dataset:
I’ve spent hundreds and even thousands of man-hours to undo the lack of planning that developers have inflicted upon their early-stage start-up environments because they simply haven’t ever managed networks or systems beyond the scale of their laptops. They have no context for setting up VLANs or subnetting beyond their cute 192.168.0.1/24 home networks. Putting everything into huge /8 subnets, extremely loose IAM permissions, overlapping VPC CIDRs, etc. have caused a great, great deal of issues that make growth slowed or even impossible. For example, we’ve had to do a number of DB migrations resulting in some maintenance periods (when our product is sold as a zero-downtime solution as a competitive differentiator) because we had to re-IP our AWS VPCs from the ground up to accommodate multiple regions and accounts. If you read through the best practices of AWS networking, all of this would have been not a big deal.

You wouldn’t hire an operations engineer to architect your software, why would you have a software architect setup your network? Software may be tough to change but I can assure everyone that the millions of miles of cabling out there in legacy data centers out there would be much better if someone with sufficient networking backgrounds had gotten involved earlier. Operations is a cost center, but it can be a force multiplier for your revenue centers of less than 1.0

If you don’t have the knowledge and experience to lay out a network and expect to grow the footprint beyond more than a handful of instances, you should probably at least get a 1 hour session over coffee with a moderately experienced engineer that has actually thought about these things before. Heck, I’d do it practically for just beer money because I’d consider it an act of goodwill for any future infrastructure engineer that has to work on the environment.
> its request model is still based on CGI, executing a script for each request

And it turns out to work incredibly well for the most part. It's serverless by design!

> People are still relying on a webserver to rewrite URLs because PHP doesn't have the concept of an application server with a router

Again, I don't see how this is a problem. Routing is likely to be the most trivial part of your app, but it's also tied to business logic and should (IMO) be part of the checked-in code.
I have one of the Visio ones. Yes, good screen, but never let one of those things on your WiFi. Jeez.
> Imagine belonging to an expert, seasoned team that masters a given technique. Literally the worldwide top 1% for that technique works under your roof.

That would worry me immensely. What sorts of things are we not realizing because we're not exposed to other ways of thinking? What sort of talent are we not training up because we don't know how to recognize it? And what do we do when some of the people under our roof retire?

Have you ever hired someone who worked at Google? They're quite probably in the worldwide top 1% for software engineering talent, and still they come out of Google expecting everything to work in a Google way. And conversely there are folks at my company - skilled software engineers - who I wish would go work at Google for at least a few months, because they've been here for probably ten years and while they're very good they've never seen how other people do things. They're skilled, but they simply have not had opportunities to learn deeply from the outside world, and in a field moving as fast as software, no single organization can keep up.

This is why open source exists in the first place. Whether or not you think there's an ethical imperative to share software, the whole idea of open source is that different companies can share source code to produce better results than in-house development and buying licenses to closed-source software would achieve. At some point, if you're on an expert team that works under one roof, you're going to stop being the experts in the thing, because the other 99% of people interested in the subject can all learn from each other, can try the things you dismissed privately long ago, can experiment at scales you simply couldn't imagine.
Rare cancer linked to breast implant used by millions of women
> Smalltalk is beautiful, but can't do arithmetics properly (e.g., `1 + 2 * 3` == 9). Lisp lets you write correct programs, but breaks your parenthesis key

Are these actually problems? Just things you have to know, and get used to.
You’re speaking of design intent, I think. I’m speaking of point-in-time experience from a user perspective. It’s clear what GCP wants to transition toward—but:

1. that’s not where many GCP-aegis’ed services are right now, and

2. newly-absorbed Google properties will always start out looking like this, so there’ll never be a time when GCP won’t look at least somewhat like this (unless the post-acquisition integration process is changed drastically.)
I guess the word pinhole is misleading here, I think it's a few cm in diameter. Behind it there's an array of lenses that projects the view onto a fiber bundle, then a lens at the other end of the bundle projects that view out. That light goes through a beam splitter which shares it between our camera and another one in the shielding box.

Most imaging in fusion is done like this because of space constraints, magnetic fields, and neutron fluxes.
Royal Mail delivers surprise Christmas gift: musical letterboxes
Show HN: Nicely Featured Blog App in 108k
Because you have a working, but ugly, solution to a problem and can't figure out a solution that does look good. Or because it's a trade-off: the thing you think would be better requires more work than you think the feature is worth. Maybe you want to tractor to make it more reusable, but decide it is unlikely to be reused, so not worth the effort.
Spidermonkey will probably never get rewritten in rust, as the safety guarantees would be precluded by JIT.
How do you deal with things like system headers then? Force everyone to check in their OS (bye BSDs)? Assume everyone runs the same OS?

How do you deal with compiler provided internals, where someone might be using clang which has behavior X, but gcc / icc / msvc doesn't?

These problems are more prominent in C/C++, but are everywhere... Not easy...

Google can probably check in everything for themselves... Probably not so easy for other companies? Maybe? Can Google solve this without sinking too much resources into it?
Delaware - where most of these startups are incorporated - does have a way for employee-investors to get this information

Except you have to be an employee share or options holder already

And you have to sue for it (or launch an administrative proceeding)

/facepalm
How to divide by zero
From orange bags to Essure: why we’re examining the implants industry
The Ethical Maintainer
I dropped two nuclear bombs
While the risk of infection isn’t binary depending on whether there is infected blood or not, they mention transmission is lessened by the diminished amount of blood left in the syringe-needle system but don’t cite and don’t say by how much. I’d be curious how much that reduction is.
Could it be that your description of Zuora as a simple USP/single driving change business is actually a testament to the simple way they tell their story? I'm the author of the post, and every business I consult with is, as you say, "complex...addressing multiple trends or with multiple layers of innovation..." That hasn't stopped any of them from crafting a similarly simple story -- starting with a single change. Usually that means either (a) focusing on the most important one; or (b) naming a change that subsumes many of the others. Getting leadership teams to align around one change isn't easy, but I'm getting better at it :)
It's painful how many people don't seem to think this way. If you've ever contributed a patch to an open source project, do you think you should be obligated to maintain this patch for the foreseeable future? If the answer to that is 'no,' then why would a greater contribution, such as an entire project, be held to such obligations? It's disappointing.
> I think Sourcegraph is trying here but that still does not seem to use some kind of accurate and structured information like you have in the code, it still seems not use build rules

Sourcegraph does use language servers (same as your editor would use) to get precise definitions and references.

For example ("find references" on some open-source code):

Go: https://sourcegraph.com/github.com/theupdateframework/notary...

TypeScript: https://sourcegraph.com/github.com/ReactiveX/rxjs/-/blob/src...

It understands many build tools, but not all. Go, JavaScript, TypeScript, Java, Python, and PHP support is all pretty solid. If you use the most common build tools for your language, it usually works well. It degrades un-gracefully if you use custom build tools or scripts, unfortunately, but we're working on making it support more build tools and customization. Sourcegraph development is open source; if you notice any problems, let us know in the issue tracker at https://github.com/sourcegraph/sourcegraph.
There are gender-specific laws in the US. For example, selective service registration, which is mandatory for males. Without having a legal definition there is no way to enforce this law since everybody will be able to claim not being a male to evade it.
Hi HN, I submitted this, looking forward to your feedback!

The stack: React with Material UI, Scala, MySQL, Redis. The static website uses Hugo with custom theme (it was based on some themes, but I can't remember).
Anarchist cookbook also said that nutmeg would make you fry.
Didn't work though for me,
However thier morning Glory seed recipe was right on the money
I've used, worked on, and depended on an enormous amount of software and I have literally never seen such a thing.
Although there is of course no warranty, I think it's fair that when projects have marketing websites saying how great they are and encouraging widespread use, users can complain when the software isn't fit for use.

If you're going to be strict about how you don't owe anyone anything, it might be a good idea not to undermine that message in your marketing. Better to tell people all the reasons why they shouldn't use your code. Not for production! There may be bugs that you have to fix yourself!

And then work with developers who don't scare easily.
That's two CEOs from two powerful, long-established, tech firms. Whatever her reasons, I hope this starts a trend...
Not to mention that Bitcoin has a very low value proposition outside of being a store of value. I can see a crypto economy where Bitcoin backs the value of other cryptocurrencies, but it’s not a good first-party currency. It’s a mere store of values nd people don’t really agree that it’s useful to exchange for services. They just see it as useful to hold value.

Something like Ethereum, with a real value-proposition, is a more worthwhile cryptocurrency.

Basically, I see crypto evolving into pseudo-fiat currencies with some large financial institution (that isn’t a nation-state) ensuring it’s a valuable commodity. I’m just not convinced we can (or should) escape a fiat-like economic system.
I'm a physicist by training working as a software engineer at one of the large tech companies. I have multiple physics friends doing the same.

We'd gladly be working on fusion (or other physics stuff) but our present jobs pay much better.

More money, and better pay for hard science careers, actually would make a difference.
There are a lot of invasive species you can actually (theoretically) get high on. E.g. Phalaris, white mulberry, mugwort, non-native sweet flag, parsnips, etc.

Most (but not all) things growing in your lawn you can eat though, if the area is free from toxins. The reason we have invasive species is because they came from somewhere else, and usually the reason they came from somewhere else is because they were what people ate before we discovered/invented better crops. Or at least this is true in New England and the mid-Atlantic regions, I can't speak for everywhere else.
> Isn't adding another potentially unknown maintainer generally better for the community than a project dying?

no. What does "a project dying" even mean? The code still runs, and will for the foreseeable future. If it was half complete, then that would be bad, but this was clearly a complete solution. Let it remain complete. This was a quick way on dominics part to kill the project actually
Banana peels might be fake but you can get high off nutmeg....if you can stand to eat enough of it...I have zero personal experience with this.

https://erowid.org/plants/nutmeg/
That's great. Bitcoin needs to get to the state where mass media also thinks that it's over for Bitcoin. The desparate phase is when the last weak hands get rid of their Bitcoins, and that marks the bottom of.the crash.
I found this comment insightful: https://gist.github.com/dominictarr/9fd9c1024c94592bc7268d36...

Summary:

1. Mark as deprecated

2. Change the name by adding "-archived"

3. Turn off Github issues

4. Give away ownership if there is at least a mini-community
It's relevant because the whole thing was just a timing issue, not some program that had been operating and was halted. The USA in its 242 years had never done such a thing. Further, since such testing had never been performed, there's little or no evidence that it would have been effective in this instance. And why the 5 year delay under Obama?

This is precisely my point that people incorrectly blame anything and everything on Trump.
Getting the root out of the ground kills them a lot more dead.
UK firm sold spinal implants that disintegrated
I think a worthy and more relevant successor to classic cyberpunk may be bio/ecopunk or whatever it's called, like The Windup Girl and much of what Paolo Bacigalupi writes.

It describes struggling or weird futures without the somewhat outdated trappings of cyberpunk, but with some of the same attitude.
So NPM users et. al. are a hoard of unwashed children. This is like Lord of the Flies.
> one of the more common error cases is nil, closely followed by out of memory and zero division ... which in Go causes a panic just like every other language.

Just FYI, out of memory is Go doesn't cause a panic. It is a fatal error which is unrecoverable and will crash the whole program.

BTW, your "More correct" version code is hilarious and very not professional.
Lots of projects, including windows and linux have had security holes that allow remote control of your system. Security flaw does not mean failure, its always about weighing the cost of security flaws against the utility the software provides. Even a completely compromised system can provide utility to many users.
That's not what OP said. Is your claim that no field of mathematics is esoteric?
Hi there, looking to move away from another hosting provider. I think what GSR really needs for that to happen is the PR feature, along with integration with Cloud Build at point of PR.
Thanks. At the end of Spolsky's article he mentions a way to survive:

"A good platform always has opportunities for applications that aren’t just gap-fillers. These are the kind of application that the vendor is unlikely ever to consider a core feature, usually because it’s vertical — it’s not something everyone is going to want. There is exactly zero chance that Apple is ever going to add a feature to the iPhone for dentists. Zero."
Paid software most often contains open source components that are equally vulnerable as this one, and if you expect paid software to be explicitly better maintained in terms of code than free software... you are in for a surprise (hint: corporate release cycle is a grinder)
Faulty pacemaker raises concerns over medical device testing
Low power,high performance wireless microcontroller-NXP JN5169
Introduction of Wireless Microcontroller-JN5169
JN5169 is part of the JN516x series Wireless Microcontroller.The JN5169 is an ultra low power, high performance wireless microcontroller suitable for ZigBee applications.

It features 512 kB embedded Flash, 32 kB RAM and 4 kB EEPROM memory, allowing OTA upgrade capability without external memory. The 32-bit RISC processor offers high coding efficiency through variable width instructions, a multi-stage instruction pipeline and low-power operation with programmable clock speeds.

It also includes a 2.4 GHz IEEE802.15.4 compliant transceiver and a comprehensive mix of analog and digital peripherals. The best in class RX operating current (down to 13 mA and with a 0.7 μA sleep timer mode) gives excellent battery life allowing operation direct from a coin cell.

The peripherals support a wide range of applications. They include a 2-wire compatible I²C-bus and SPI-bus which can operate as either master or slave, a 6-channel ADC with a battery monitor and a temperature sensor. It can support a large switch matrix of up to 100 elements, or alternatively a 40-key capacitive touch pad.
> This whole thread started because the top comment said that a physics theory predicted the value of the fine-structure constant.

Yes.

> Which is wrong

No. I even provided you with the reference to the paper in question. Did you even try to read it?

> as the fine-structure constant is one of fundamental constants of the universe and one _whose value is not predicted by any theory_

This is where you go wrong, and where you misunderstand Feynman's point.

The correct statement is that all respectable theories of physics (to date), including the Standard Model, include an irreducible number of values which must be plugged into them "by hand". In other words, once you've written down your theory, there are some parameter values in it about which the theory itself gives you no guidance; you could give them different values, and the theory would still work. It would just be describing a universe with different properties than ours. In order to make it describe our universe, you need to get those values from experiment.

Feynman's point is that we don't have a theory without at least some such parameters (even string theory, which he disliked, has the string tension, and it skirts the need for more by randomly picking a vacuum, which sets the values of low energy theory "constants"). It is not that the fine structure constant has some particular status as "more fundamental" than others.

The choice of constants which you can determine by experiment is constrained by the theory, but generally not locked down completely; you can choose your set of constants, as long as they are independent, i.e. as long as measured constant #1 can not be determined by plugging measured constant #2 into the theory and doing some calculation. If constant #1 can be computed given the theory and constant #2, then they are not independent, and the choice between them is arbitrary; a convention.

The choice between fine structure constant and magnetic moment of the electron is one such arbitrary choice. Given one of them and the Standard Model, you can compute the other. And It turns out that it's actually more convenient to do it this way: measure the magnetic moment, then compute the fine structure constant. There is no reason at all to regard the fine structure constant as more of an "input to the model" than the magnetic moment, as you claimed at the start of this thread.

Needless to say, Feynman knew all this perfectly well. You are just taking away the wrong message from an attempt to popularize the topic. "QED" was a popular book, not a graduate text.
Not really. The big issue is with long-term deterrence, not short-term. It is fairly easy to isolate something for 30/50/100/200 years. It is much harder to isolate something from future humanity with a high level of certainty for 200,000 years. Even things with low levels of radioactivity will kill you if ingested and do a lot of harm if kept near. The problem of communicating this to future humans is a big one. How do you keep future humans who may not have the level of technology we have from deciding that the magic, glowing, heating stone is a source of healing and prosperity instead of something to be avoided?
"The first person in Britain to receive what was heralded as a revolutionary pacemaker has told of her nightmare after it stopped working and surgeons were unable to extract the implant from her heart."
Google Cloud is worth checking out. CSR is just one of their offerings in the GCP ecosystem.
What if we could register ourselves and update our poetries? So we could like or dislike and find people with the same "taste".
It seems like you have the perception that top talent is easy to hire. In my experience that hasn't been true at big or small companies, and if a candidate is exceptional companies will go the extra mile to get them. And if we're talking about early stage startups the power dynamic is totally reversed - the senior candidate actually has a ton of negotiating power because a startup can't compete on salary with FAANG companies, and good candidates know it.

Good senior people are selective and want to know a lot about the companies they might be joining. If they didn't ask perceptive questions I'd think it was a red flag.

I mean seriously, a startup is trying to hire a senior engineer, is offering less base salary than Google, stock with an average value of nothing and they don't even want to answer the hard questions? How would they ever hire anyone good?

The only people I'd give a pass on not knowing asking good questions in an interview are interns or new grads.
The nutmeg thing is true, but you do have to eat a considerable amount of freshly ground stuff, which is revolting. And it's not a good trip, either.
gp comrade must have some russian background - "samodelkin" roughly translates as DIY
It's honestly one of the greatest advantages of working in google3. GitHub search is honestly pitiful next to it.
Cryptographically-backed version control system (2016)
LOC is a very very bad metric. How exactly is it counted? Include mass refactoring? Is there a better metric? Yes, a long list of testimonials from happy customers.
Its sad to see the contortions my boyfriend makes to support his purchase of a headphone jack free android, despite his desire for high quality audio (he hates bluetooth with a passion). USB C to 3.5mm adapters are cheap, but break at the drop of a hat. His integrated speaker meanwhile has blown, and makes for terrible calls.

Headphone jacks serve a useful purpose, most phones could still have them without compromising other properties, but its been made fashionable to go without.
OCaml is not for the masses, it never has been
You want evidence that humans are able to be manipulated at scale?

https://en.m.wikipedia.org/wiki/Religion

https://en.m.wikipedia.org/wiki/Capitalism

https://en.m.wikipedia.org/wiki/Nationalism

https://en.m.wikipedia.org/wiki/Advertising

Etc, etc...

There’s an interesting parallel here. When an obvious thing is granted a software patent because it’s the first time it was done “on a computer.”

Human society has a long history of being gullible and easily manipulated at scale.

Facebook is just tapping into that nature “on a computer.”
I believe that you get good by getting better. And I think it's easier to tell that you've gotten better than it is to tell that you've gotten good.

Look back 6 months, a year, 2 years. How have you grown? What can you do now that you couldn't do then? Are there things that you'd do differently? Things you wouldn't do at all? That might give you a sense of where you are now.

Repeat the process of getting better many times. Then one day you'll take some call, draw some diagram, write some code and you'll know. For a brief shining moment you will know without a doubt that it is good and you are too. Then the moment will pass and you'll spend a couple of years trying to find the next one.
I'm not saying it's a slam dunk argument. I have no opinion on how this case will go because I don't know much about the law. I just think it's pretty clear that setting a 99 cent price floor increases the price of some apps.
Kind of like soil growing?