skysight-inc/HackerNews huggingface dataset:
NYC is nowhere in the mess that DC is in. Mostly, because Manhattan, at least, is well-shaped to be navigated efficiently by rail. Because of height restrictions, DC has a relatively sprawled, 2-dimensional core, which means many common routes require transfers (also, the metro being so deep means a nontrivial amount of time is spent on escalators). For me, I often faced the decision of "$6, 10 minute Uber vs. $3.50 1 hour metro". Manhattan is long and skinny -- there's almost always a 0-transfer ride that can get you from point A to B + the wait is almost never longer than 10 mins. Every time I've said "I'm running late, I'll take a cab", it turned out to be a mistake. The situation is certainly different in the boroughs, though.
> and applying what I learned

This is a big part of it. This sort of improves with practice, but can also decay from lack of use. For me, I've found that regularly putting myself in a position where I talk to people I don't know helps a lot.
Invalidating the caches is kind of a cringe inducing approach on this (actual) problem. Especially in HPC radiation related single event upsets have become a real problem. If you do the math, all the silicon area devoted to memory (DRAM, caches, registers) adds up, and what you've got is essentially particle detector.

Compared to the effective volume of a purpose designed one (ATLAS, CMS, Super Kaminokade, etc.) rather small, but a particle detector nevertheless.

A couple of months / years ago, there was an article (also linked here on HN, IIRC) that did a few back of the envelope calculations regarding expected event rates. IIRC it was something on the order of 1 event per day per 10^12 transistors. (EDIT: not the one I thought of but blows the same horn: http://energysfe.ufsc.br/slides/Paolo-Rech-260917.pdf )

Also radiation hardened software has been researched (and still is). Essentially the idea is to not only have redundant, error correcting memory, but also redundant, error correcting computation. NASA has some publications on that. e.g. https://ti.arc.nasa.gov/m/pub-archive/1075h/1075%20(Mehlitz)...
Brings back old memories of using the Athena X window widgets.
A Man Who Designed Ghost Armies and Opera Houses (2016)
I agree. Working early on your side-project is kind of like the "pay yourself first" principle of saving money. It is also the same habit practiced by most writers before and after they publish their first book.

I've had the most success with this formula:

1. Every day, wake early and work on your project 1 - 2 hours.
2. Work your "day" job. If your job allows it, spend your breaks planning your side-project work.
3. Spend time with family and work some after dinner. In my case, I can usually code
and watch TV out of one eye while spending time with my wife.
4. Rinse and repeat

I used to strongly believe that side projects could only be done in four hour blocks of time without distraction but, often, that kind of time is in rare supply. However, when I got a job that required an hour train commute, I found that I could knock out some useful code even when my time between laptop-open and laptop-closed was 30-45 minutes. The tricks to making use of short blocks of time are:

1) Break the project into short, deliverable bits
2) Build placeholders/stubs as you go for things to flesh out later
3) Leave yourself lots of "do this later" comments with ample specifics.
Don't just say "finish this." Say "Use ABC parameter to lookup XYZ value to override the default."

Structuring the work for "resume-ability" makes it possible to squeeze short bursts of productive work into your day.
National/racial flamewar is not allowed here and we ban accounts that do it, so please don't do it on HN again.

We detached this subthread from https://news.ycombinator.com/item?id=18494646 and marked it off-topic.
U.S. banking sector reports $62B profit in third quarter
Likely the same thing that happened to all the mills throughout the rust belt. They'll get abandoned. The pessimist in me says that they'll get sold to a new corporate entity which will then file for bankruptcy and the government at some level will need to clean it up.
Yes, although looking at what other people have commented, "our" intuition is quite basic. I will try to read more about FEP.
I honestly think this website's negativity towards stuff stems from not understanding use cases and being a general curmudgeon.

"All major cloud providers have a managed k8 service, so you don't have/need to learn much about the underlying system. You can spend a few days, at most, to learn about dockers, k8 configuration files and helm and you're pretty much set for simple workloads (and even helm might be overkill)."

This is the reason why I use k8s. It is ridiculously easy to deploy applications and I don't have to worry about hardening the VM.
How so? You are nearly doubling your money every 3 months. What investments can do that? Crypto? Not guaranteed. Pretty much only usury and actual crime.
Your first tl;dr point should be "never sell options without proper risk management in place". Selling vol is a perfectly sound strategy in itself. It's just very easy to do wrong.
that's why you version pin and vet new updates before you let them in.
We're thankfully not cursed with a multitude of competing standards for bilevel monochrome 2D codes (they do exist, but 90+ percent of everything out in the wild is QR). I don't think an end user is going to be competent to understand the differences between them in any case. The standard operating procedure will continue to be "point the scanner at it and hope for the best." If multiple competing standards do become popular, the most likely result is that scanners support all of them and we just eat the software bloat.
You sound envious.
The data firms ICE hires raise alarm about a hidden surveillance industry
She should be eight by now, if that makes you feel any better... ;)

(Sadly, at age 53, I probably cannot get away with trying to make letters happy or otherwise be "cute", or I might well be inspired to try to do some kernel dev in the near future.)
Yeah I know. But I think at MS they work closely with Intel and think of other vendors as not as important.

I did work there too, and to be clear, did not witness anything like this. Just a personal opinion/hunch.
At my work everything has a bar code on it. It seems carry have enough information.

High capacity code have probably different applications. I haven't seem them anywhere yet, but there are several products around them. I think printing a public key with such a code on a business card would be cool.
Make Linux Fast Again
and more generally, the ship of Theseus
Theoretically, if a gamma-ray burst was pointed directly at the Earth. I assume that the chance of that for a particular event is quite small.
I used to work in DRAM manufacturing. I believe 100% in bitflips -- we saw them in testing all the time. I also believe the rate at which bitflips are caused by gamma rays is absolutely dwarfed by the rate at which bitflips are caused by manufacturing defects. It's really easy to manufacture a weak cell when you're making billions of tiny capacitors at the same time. SRAM might also see lots of bitflips, but that seems even more likely than DRAM to be driven by manufacturing defects, given the greater complexity of the SRAM cell.
Ah, it can work that way as well? That is indeed slightly faster - I'll consider it if Gmail doesn't have Reminders by the time I'm forced to leave Inbox.
Radical new 3D body scanner delivers startling first human images
>He'll continue to wear a watch worth more than my car

It's a Rolex Datejust 41mm, $9350. And it can be had new from a dealer for less than that. Just an FYI :)
Bodil Stokke has many other interesting projects. Check out her other repos too.
People generally prefer public servants to earn less then the person bringing their latte. Meanwhile, HN posters balk at mere 160k starting offers.
Because trade secrets are not a respected form of IP.

- Patents serve to provide a temporary shelter for monopolizing new ideas and methodologies to allow them to be developed

- Trademarks serve to guarantee consumers can differentiate products and their producers

- Copyright serves to allow people to make money from creative works while distributing them widely.

Trade secrets? Trade secrets allow a company to monopolize a market with no benefit to the public in the long run. They deserve exactly zero legal protections.
Like I said above, only talking about dude in charge.
I came to say the same about Dale Carnegie's "How to Win Friends and Influence People." His teachings are aimed at being a better salesperson and you should treat it as such. Taking it as self-help advice is going to lead to frustration. (As a guide to sales, it has mostly evergreen, if hokey, advice. It was first published in 1936, after all.)

I don't know if reading a book will fix everything in this situation, but if you really want one, get closer to the subject with "Secrets to Winning Office Politics" by Marie McIntyre.
Maybe, though the stigma there took the form of legalising it, allowing people to openly come forward and seek help, and levying heavy taxes. I'd say drugs are even more stigmatised (to the point of being largely illegal), which so far hasn't really result in lowering usage numbers.
> Bit flips in network surely is many orders of magnitude worse

Yes, but because it's so prevalent that people expect it, they've added checksums on multiple levels, so the network actually performs better. In this particular instance (DNS queries), it's very unlikely that the data was corrupted in transit: "We believe that UDP checksums are effective at preventing 'bitsquat' attacks and other types of errors that occur after a DNS query leaves a DNS resolver and enters the network."
It demonstrates how Linus is not only a good programmer, but also a good leader.

I get the same idea as with the first Gordon Ramsey Kitchen-fixing programmes. Apparently, people said it was insane how he dared to swear on TV. But basically, he notices things are very wrong, makes sure he gets to the bottom of the mess, and hammers the ugly message very publicly into some owner who lost any connection with reality. If the cost is some swearing, that's the least of the problem. The failing businesses get fixed at least as much on a sociological level as on a cooking level.

Linus does the same. A big software project's problems are more sociological than technical in nature. Sometimes, the ugly message has to get trough, an another famous rant is born. But most of the time, work gets done, probably with a reasonable amount of smiles.
Should I include CSRF protection on a login form?
Wikipedia disagrees.
Skara Brae was occupied about 3190 BC.
Earliest Egyptian pyramids were started about 2630.
The Great Pyramid was built about 2560 BC.
Most of your comments break the guidelines by being uncivil and/or unsubstantive, so we've banned the account. If you'd like to start using the site as intended you're welcome to email us at hn@ycombinator.com.
From Wiki:

> Einstein's refusal to accept the revolution as complete reflected his desire to see developed a model for the underlying causes from which these apparent random statistical methods resulted. He did not reject the idea that positions in space-time could never be completely known but did not want to allow the uncertainty principle to necessitate a seemingly random, non-deterministic mechanism by which the laws of physics operated.

The underlying assumption for Copenhagen was to try to preserve locality by assuming non-determinism. However, there’s no saving locality — and non-locality is enough to leave determinism — so there’s no reason for the non-deterministic axiom.

I think I also meant “definite” instead of “deterministic”, but it works out the same.
> Honestly, your proposed solution goes too counter to human nature to be viable, in my opinion.

I know it does. That's why we are well and truly screwed. But to be honest it's the only thing I can think of that would give us even a fighting chance, because a century of 7+ billion humans will absolutely suck this planet dry. BTW there is no such thing as "sustainable growth". It is a contradiction in terms.

I'll refer you to Al Bartlett.
https://www.youtube.com/watch?v=V3LryW47B_M
Isn't this like, one year old news at this point?
> The problem for me with the old big-server-many-apps approach is the way it becomes hard to manage. 5 years on, I know that I did a bunch of things for a bunch of reasons, but I don't really remember what or why.

I thought this was a solved problem.

I use SaltStack for config management & orchestration on my own machines. (I suggest any config management tool becomes 'worth the effort' once you're managing more than a handful of machines, and/or want to rebuild or spin up new machines with minimal effort and surprises more than once a year.)

Why I do something is described in a comment in the yaml that does the something.

For more nuanced situations, I'll document it in my wiki. (With a yaml comment pointing to same -- I am extremely pessimistic about future-Jedd's ability to remember things.)

If you're running a big-server-many-apps or many-servers-with-their-own-apps, I'd expect the same approach to work equally well.

Though the whole idea of virtual servers & config management (but not necessarily docker or k8s) is that you don't have a bunch of disparate and potentially conflicting apps with potentially conflicting dependencies on a single server.

> But "virtual server" is like "horseless carriage". The term itself indicates that some transition is happening, but that we don't really understand it yet.

That's a challenging assertion to fully unpack. IT's undeniably in a constant state of transition -- and not always thoughtfully directed -- but the problem isn't _'virtual server'_.

The general trend is obviously towards isolation -- but the tooling, performance, scaling, design, and security disparities make the arguments around what level you try to implement your isolation so interesting.
Does it count if the building is continuously maintained along the way? Something like https://www.smithsonianmag.com/smart-news/this-japanese-shri..., but with less conscious effort towards ritualistically maintaining the layout.

If so, I think plenty of buildings will survive. If not, it’s a strangely specific definition to me, since still standing but un-maintained and unused isn’t a goal I would shoot for.
You don't have to be an asshole all the time to be an asshole.
I think it's early days to judge the effects of the GDPR. If websites are anything to go by, the primary effect on cars will be (if not already) pop ups on the touchscreen to agree to the new T&Cs.
And here's how you get junior kernel devs :D

I hope you're still hacking on it and other projects, Maisa Roponen... Now 8 year old!
Doesn't WordPress already do this? Not sure this is very helpful for WordPress users. Although, I do see the use for static blogs and those that do not already send emails when posts are published.
Exactly. It solves some of the most important problems that come up of working with microservice based architectures, and establishes mature patterns around the ability for multiple developer teams to update and scale each piece of a distributed application.

Also, what do you do when your digital ocean droplets needs hundreds or thousands of customers on it? Maybe each customer needs it's own database (well in my case they do), configuration, storage requirements, and multi-node requirements. How do you keep track of all that, how do you automatate it and QUICKLY recover in failure scenarios. You need to be able to deal with failure on a node, or if there's a bad actor you need to be able to move them off easily without downtime or affecting other customers, automatically, seamlessly. You need to be able see an overview of your resources across all nodes and where apps are placed and have something decide if the hardware your new container is being added to can handle another JVM or whatever. For cost effectiveness, you want to be able to overcommit resources, so you want containers. You want those to translate to other platforms, AWS, google, azure, on-prem. You have a single declarative language that works anywhere you can deploy a k8s cluster. You need to deal with growth, good patterns for rolling back and updating versions of parts of the stack. You want all of your deployments to be declarative and to be able to tightly control the the options for each one and get back to where you were.

I agree that it doesn't make sense for everything, and it requires fundamental understanding of linux and software before it even makes sense to try shoehorning onto, but it solves real world problems for many people, it's not just a hype thing. I would say docker itself was more of a hype thing than k8s, the maturity and features of k8s and other orchestration systems that came out of the docker model is there for a reason, because it solves all of the real-world problems people couldn't solve with vanilla docker without tons of custom scripting and hacky workarounds. Docker solved the big problem by providing the isolating environments for each app and splitting things out into microservices that way, without having to commit a full statically resourced VM or bare metal per service. K8s solves all of the other problems that came out of that (pods, stateful sets, init containers, jobs, cronjobs, service definitions, deployments, volume claims.)
I work in the same environment, and hiring is the only downside I see. Resume Driven Development and "Dev Sexy" has made it difficult to find developers who are willing to come on board, despite the sanity provided by simplicity & comp.
For the love of god I still don't see an 's' with a missing (or newly inserted) "=". I've spent way too much time looking at this
Hear hear. I lead a team that builds and manages critical emergency services infrastructure.

Our stack is pretty boring, but then it has to be running 99.999% of the time. Rather than wasting time chasing the latest flavour-of-the-month tool or framework we invest our time in plugging any kind of gap that could ever bring our service down.

We don't need people who are only looking to pad their resume with the hottest buzzwords, we look for people who want to make critical services run all that time, that rarely fail and when they do, they handle failure gracefully.

The number of devops/agile/SaaS style shops I have seen where the product falls over for several hours at a time is astounding, and it can often be attributed to rushed/inexperienced engineering or unnecessary complexity.

Lucky for them it's usually just the shareholders bottom line that is affected. If the services my team provides don't work, ambulances and fire engines are either not arriving fast enough or at all.
Luke Howard “Namer of Clouds”
That's me admitting that my already dubious source was not from California... unfortunately we don't get to choose how high quality and relevant our sources of anecdotes are.
These stories are so interesting & tragic because the weakness being exploited is that uniquely American breed of optimism... the one that's maybe one part American Dream (capitalist patriotism), one part Jesus (including both the Protestant work ethic and the belief in "deserving") and one part The Secret.

You can't think a fax is a gift from God if you don't think there's a God, for example. And you won't be as predisposed to look at it as a break for you, if you don't think you "deserve" a break (or to be rich, or to be in business at all). And you immediately see the downside of any loan, the second you consider "Hey what if tomorrow isn't more flush than today?"
> There's nothing stopping you, except the one thing that stops a lot of people

FTFY. There's a non-zero amount of time investment required to submit kernel patches (learning enough git, using the mailinglist, responding to questions, submitting revisions, etc)
Games not running on Linux is slowly becoming a thing of the past. The largest hurdles are studios that develop their own engines from scratch and do not support anything other than directX.
Not that this comment is good advice, but that this comment is downvoted, but the comment about being a backstabbing, lying, traitorous arse survives… We have a long way to go as a species.

A drink with coworkers is probably okay. "lose your inhibitions", however… no. Remain in control of your faculties, please. I've had to help more than one coworker who has drunk too much, and it is obnoxious, and it does lower my opinion of that person.

Don't feel obligated to drink alcohol, either. I wouldn't question it, and there are plenty of drinks that visually aren't distinguishable from alcohol if you need a cover (e.g., coke vs. rum and coke, sprite vs. gin and tonic), and a drink in the hand is a nice stressball of sorts. (And I've used "I have to drive later." as a reason to not have alcohol, but still enjoy the company of others.)
Perhaps my language was too dismissive. I regret that. Are you suggesting that pharmacists who refuse to hand over drugs that they disagree with for whatever reason are doing so because they have the patient's wellbeing in mind?
Getting Started with Serverless Angular Universal on AWS Lambda
> A Kubernetes cluster is not a computer, it is a cluster of computers.

That statement is true, but the thing it implies isn't. A cluster of computers on a common backplane can certainly present itself as a single (NUMA) computer, with one process scheduler, one filesystem, etc. Most HPC systems are built this way.

As well, when your workloads are, themselves, VMs, there isn't much of a difference between having a Z-series machine as a hypervisor and, say, a vSphere cluster as a hypervisor. Either way, you get a pool of CPU, a pool of RAM, a pool of storage, etc. And either way, you get VM workloads with transparent migration on node hotplug/node failure, etc.
...and those that do are often making money out of it.
It takes some time to get used to Finnish style of management.
It may be a fallacy to assume a neuron is less complex than a brain. Depends on how one measures complexity and at what scale... but living systems -- unlike no living systems -- strangely get more complex the closer in one goes. That is, it's fairly trivial to simulate an earthworm... it's trickier to simulate the components of the earthworm.
Thank you! We have plans to build many more frontends in the coming years, so it felt like an appropriate time to step back and see what other solutions were out there.

For the e-commerce part of it, it's a custom API written in Scala that handles our inventory, warehouse, and fulfillment needs. As well as interfacing with Stripe for actual order processing. Want to get that team to write their own blog post as several people have asked about it!
From January 30 of this year: https://www.bloomberg.com/news/articles/2018-01-30/crypto-ex...