skysight-inc/HackerNews huggingface dataset:
I really hate the whole non-determinism in sites. First we have A/B testing, then we have google search showing different results depending on what computer/account/country of the ip address you are using, youtube showing different recommended videos (rather than basing it on the current video), etc.

It would be great if instead they had a deterministic way of looking at it. For example give an easy way to anyone to select a different "perception" for the map borders.
Pedanticly, "casualty" does actually mean specifically soldiers (or other military personel). Civilian deaths are called "murders" (or "executions"/"resisting capture"/not-at-all if your side is doing it). The term "civilian casualties" is a euphemism that was made up (IIRC during WWII) to obscure/excuse bombing of civilian targets (especially factories). In practice, the euphemism has largely won, though.
> It randomly inserts layers of computation between the networks’ input and output, and tests and trains the resulting wiring with the limited data. If an added layer enhances performance, it’s more likely to be included in future variations.

Sounds a lot like genetic algorithms but with neural networks. I suspect we'll see more of this as people figure out how to run the search over neural network architectures that fit their own domains. Convolutions and transformers are great and all but we might as well let the computers do the search and optimization as well instead of waiting on human insights for stacking functions.
I don't have a strong argument against that. And I've never seen convincing evidence that a drug-war-type focus on restricting supply is worth the cost.
Do whatever the hell you want with FB, Zuck!

Stop worrying about trying to please the PC police and just run the most addictive and profitable BBS you can. Promote whatever you want and shadow ban whatever.

The Europeons may object, but ultimately in the US the political will doesn’t exist to make you do more. A few politicians like Hawley on the right and AOC on the left may have an issue that works for them, but the American majority is going to look pretty skeptically at any significant regulation.
I've found questions about past jobs and why I left to be common enough. So I feel it's beneficial to have a narrative that paints one in the best light (ignores the negatives, promotes the positives, etc.).

>Also, even if you're aware of the question — do you rate yourself below 7, or hide the fact that you've been let go by the person rating you 7 and above?

That depends on your ethical views on lying. Personally, I don't owe companies anything and they will lie to my face about things if it benefits them (like layoffs, financial state, worth of options, etc.).
If it's anything like amazon they will just be able to look at all of your code for the last N years which is a very strong signal to go along with interview questions. For internal transfers I general focus more on design questions and check the code history for "can they code IRL". Design is harder to check for and also is more dependent on "can we work together to solve problems" which isn't always apparent from just artifacts.
Yup, this is spot on. In our startup one of the challenges to hiring isn't a lack of money or need, but rather that we need people who can bounce around a lot of somewhat specialized topics, while generally no one topic is big enough to justify a full-time specialist.
It's a shame because if you kept reading you'd have reached the disclaimer that he has broken (and still does) all of the above rules.

I think this list is sound. In my world, rules that are not able to be break when needed are not worth having.
This only works for management, who are not actually doing any of the tangible work, but doing diversion work instead. For the kindergarden style teams, there are multiple non-productive diversion people already telling different stories to various other functions of the company. Then you have the next legs beyond that telling wilder stories. The dysfunction only grow worse as the system tries to scale the dysfunction.

Today most of business side has simply become too incompetent to be able to complete a dialogue with devs. Same goes for dev side, but is nothing new.
> 3. Pofit!

Was that "Profit!" or "Poof it!"? ;)
>it doesn't seem like there's even any extra benefits of using robots

you mean other than the $375M you can walk away with by claiming you're using robots to make pizza.
There are lots of ways to test and to map potential features to customer problems. Launching features because _you_ think they’ll resonate with users is a complete crapshoot. More often than not, people inside the company are way too close to the product to be able to determine which features are the right ones. I recommend “The Right It” by Alberto Savoia, “What Customers Want” by Tony Ulwick, and “The Lean Product Playbook” by Dan Olsen if Cutler’s essay doesn’t convince you.
Monorail System Debuts in 1910, Wins Praise from Churchill, Then Fails
This sounds like every place I've worked at ever and I don't expect it to change anytime soon
Thanks for sharing. I didn't know and I still don't know how much typically a (good) health insurance costs. In most countries in Europe, however, it doesn't justify the lower salaries in the SW industry.
Why work around it when the Go version worked as is?

I’m not sure I really see the benefit of working around it when Go fit the use case as is
That's not how that works out in practice though. When each function does one thing, the cognitive load is low and you name things appropriately that make understanding each function on its own easy. You can scan an area of code quickly and find problems without having to build the whole house again in your brain.

It's much clearer when you hit some unintended edge case then having to maintain a mental model of a huge function doing a lot of things.

If your way of grading someone's code is to make sure you can build the whole house in your head, rather than have an exhaustive set of test cases to validate your specification and a simple "each function is appropriately named and does exactly what's intended in the correct manner", then the grading method is the problem, not the code.
Entrepreneurial Spirit: The Force Behind the World's Greatest Minds
Clean up your .NET with the Dispose Pattern
I think Sweden is very romanticized in American media and amongst the elites. Having lived there for 6 years before moving to US, I think it's an ok country but nowhere near the paradise that is promised by the American media. They say the best thing in Sweden is its health care. In the entire time I was there I attempted to see a specialist for a condition that I had maybe two or three times, I ended up giving up every single time after I was told the wait time is between 3-4 months. I keep my American employer sponsored private insurance and employer determined time off policy, thank you very much.
No real reason except no one has tried yet. It's extremely difficult to get search right, although Moore's law and tensorflow has probably made it easier to attempt today. Latency would be significantly worse than major search engines though. I think for the people who care about the open web, having a libre alternative search engine should be the highest priority. It's one of the few classes of software/services that no one has tried replicating open source.
Makes some sense, but that got me wondering if medical guidelines are going to start getting updates every few weeks like web browsers do.
Several of these exist and predate webpack. Webpack became popular precisely because it wasn't grunt, gulp or npm run scripts.
I agree and think it’s a divide between product and engineering. Product managers (at least good ones) love thinking about the problem, while developers love thinking about solutions. I’m generalizing of course, and both mindsets are needed, but it’s the product manager’s job to make sure the developers are solving the right problems and not just launching features that don’t speak to a customer benefit.
Agreed. A decent build system language and separate tools would be a lot easier to understand than one megatool that does everything in a magic way with plugins and a mega-config file that's impossible to understand.
I think also France allows that, not just for entrepreneurs, but for anything. A colleague of mine just took a sabbatical and next year he'll be back.
i believe that's the reasoning for why many systems have devolved to boolean choices rather than multi-tier (distortions in voting cause mispresentations of the customer population's sentiments).

but boolean choices are really 3-tier systems where it's assumed that only the extremely statisfied or dissatisfied customer will vote (up or down), and the lukewarm/indifferent customer is assumed not to vote. however, that assumption very likely misrepresents the sentiments of the (majority) non-voters and thus the population as a whole.

you might address this by moving to a 3-tier system: (1) unsatisfied/bad, (2) acceptable/fine, (3) exceeded expectations/great to more accurately differentiate the non-voting/indifferent customers, but non-voters would have no incentive to suddenly voice their opinions and make the system more accurate.

you might be able to counteract that impulse by incentivizing customers to vote on every product/service delivery event (like earning points for future discounts) to lower response bias. you could also do a separate study to see how the voter/non-voter population differ, and adjust the boolean ratings accordingly.

in any case, rating systems are tricky.
Well, sans magic wand, I guess they could try to sell Alien Scout Cookies to try to fund the SETI field.

You could probably sum up much of your statement as self-sabotage, since that seems like all the rage nowadays (politically and monetarily speaking).
A lot of people seem to struggle with initial setup.

There's a lot of threads at https://www.reddit.com/r/Traefik/ about that but there's also a ton of guides and help so I'm not sure why there's so much struggle.

Maybe it's because they're so used to doing it with nginx.
I've found a fairly workable solution is to have an origin for the API in CloudFront and a behaviour to route /api/* to that origin. Saves any CORS headaches. Obviously this won't work in all cases.
> Configuring CORS is probably the biggest pain about this approach and is necessary if you want to send data to and from an API.

CORS is only needed for the API, not the website, and only if you don't control the API or don't make it so the API can be served (from the client's perspective) from the same origin, perhaps because it's fronted by the same Cloudfront distribution.
Thanks for pointing these out; I've avoided using Blender for sculpting for a long time since the performance wasn't even close to ZBrush and it didn't have equivalents for Dynamesh/ZRemesher. Maybe it's time for another look.
This benchmark mainly measures the performance of the HTTP parsing and database libraries, often in a suboptimal default configuration. In node land, they're admittedly not amazing, but nothing about the language prevents them from being better.

For example, for a long time, the only reason that node was slow on these benchmarks was the built-in URL parser. Replacing it with this carefully written module https://www.npmjs.com/package/fast-url-parser resulted in 2x improvements on the benchmark. I haven't looked closely at the situation nowadays but I imagine its still quite similar with lots of low hanging fruit lying around and stalled due to backward-compatibility concerns.

For proof find "es4x" in the benchmark list, which basically replaces the entire stack of HTTP parsing and database libraries with the ones from vert.x and runs JS on Graal, even though Graal is currently at least 2.5x slower than V8 in terms of JS performance: https://github.com/graalvm/graaljs/issues/74

Node core (and the libraries around it) has unfortunately stalled in the "good enough" zone for quite a while. The good bit is that they stay in the good-enough zone after adding your own code.
It’s very much true that Sweden’s labor laws are deeply influenced by a heritage of large industries like Ericsson, Volvo, SKF and the like. They work well when employers are large, employments are long.

It’s equally true that these laws may not create a great climate for small tech startups.

I don’t think there is an easy answer to how to liberalize the labor market without it damaging large groups of blue collar workers (which would make it politically impossible). Denmark has an interesting model where employment security is weaker but in return the safety net is better. I think this is where Sweden could be headed as well.
I was a tech lead for a team in a startup but not particularly high.

I know other people that were on similar salaries and I had friends who did the same thing as contractors that had much higher day rates.
CF is not necessary anymore for SSL since GH can issue LetsEncrypt certificates automatically. https://help.github.com/en/github/working-with-github-pages/...
Jethro Kuan’s earlier posts on Org mode for planning finally made the idea click for me (maybe just the last straw on the camel’s back). I strongly recommend checking those out too.

Btw, to Notion users — does anyone feel that it’s matched/surpassed Org mode in the breadth of workflows it supports?
I have a huge soft spot for NetBSD because it was my first BSD and first foray into kernel work. The more alarming issue affecting Open and Net is that commodity computer architecture has wildly changed in the past 10 years. A late 1980s style locks and CVs approach to SMP is only good for a handful of cores. Consequently, if you run one of these on what are becoming standard desktop class systems like Ryzen, you are throwing away a great deal of performance (and therefore energy efficiency). Basically modern computers look a lot like an HP SuperDome or whatever from 2000 which is wild and inconvenient for programmers, but reality. FreeBSD (HEAD) is now generally competent on something like an Epyc or multi-socket intel box, and there isn't much left to eek out on an 16-thread laptop.

I funded and helped stabilize a technology called Epoch Reclamation into FreeBSD that can be thought of like a cleaner version of Linux' RCU at least for tracking object liveness. One of the most interesting things I've seen go into FreeBSD recently is a further improvement on that, a novel form of safe memory reclamation directly in UMA: https://reviews.freebsd.org/D22586. This is really exciting because for instance RCU suffers from time of use to time to free issues in Linux, and this new holistic approach really does not for fast turnover workloads.

NetBSD does have a form of SMR called pserialize(9), but ignoring some of the algorithmic weaknesses it also has a lot of global or oversized locks in critical subsystems like the VFS and network stack that turn it into a fairly non-SMP friendly system let alone consideration for different memory latencies like NUMA.

A lot of these ideas from FreeBSD can be copied into Net and Open but the code bases have diverged greatly where it's not some simple forklift (for instance Net and Open use a similar kernel memory allocation that is totally different than Free).
Do you think that there's something an interviewer could have done to help you get the solution written within the interview instead of after?
Microsoft pulls security update after reports of issues affecting some PCS
Done poorly, all that process is going to hurt you. You'll end up with teams of people who know their role, celebrate the process, but don't know or care how to connect their work back to the bigger picture.

Agile and Sprints can lead to this. You will see a lot of ceremony, and the team might increase their throughout. But you find your team disenfranchised and producing substandard code that doesn't really do what it needs to do.
Show HN: The Battle for Rust Knowledge Supremacy
Well, unless a company has a specific policy, it's something you'd probably need to negotiate. What you describe seems pretty reasonable as a leave of absence for a valued employee who actually has an option to take a leave of absence but it certainly isn't something I'd assume was anything like a universal formula. (Certainly continuing healthcare is a big deal for many people unless they're covered by a spouse's policy whether or not they have to pay the company portion or not.)
This smells of security through obscurity to me.

Unless you’re defending against zero days (unlikely) an up to date Linux box must surely be more secure?
Online retailers are destroying goods but won′t say how much ends up as trash
The 5 hour work week was an isolated thing reported as somehow a national change (i.e. BS).

This might actually be true (that people are entitled to this) I guess, but you are correct that basically no one does.
Security update for Windows 10, version 1607 has been removed
Show HN: I Implemented 'Defer' for C
There are private health insurances here too. If the public system would be so bad as you describe it everyone would use the private ones but very few do.
any idea on ml on k8s
Has he proven that? One successful toss (Alibaba), i.e. a sample size of 1, doesn’t really prove anything does it?
Windows server 2003 had NUMA support. I am not sure that Server 2000 exposed any NUMA capability, but there were a lot of things cut from that project because it was running late. My guess is NUMA was one of the things that got pushed (in terms of release) to 2003.

They used to have a "Datacenter" SKU of the server where you'd find most of these kinds of features. This was only available with OEM hardware IIRC.
> What else links Austin and the Netherlands in computing at that time?

It could be related to the fact that UT Austin wrote and maintained their own OS (UT-2D) for the CDC/CYBER architecture, and maintained it well in to the late 1990's/early 2000's.
This was reported a few weeks ago, and there's a podcast (This Week In Virology) that goes into a little more detail - highly recommended.

The researchers that mapped the virus were part of a team that was sent to collect samples from bats to help us identify and study viruses for the next SARS/MERS outbreak.

Note that "similar" is far from meaning the "same" - it just means the closest match we've seen thus far, and therefore means it's very very likely to have also evolved from bats. ...and they did not test human virulence, so I think the notification n of "missed opportunity" here is a bit of a stretch.
The most painful part is the founder lingo all this technical superlative 6-axis factory line robot [0] and laser triggered faucets just to make your sad blind ambition sound valueable. Also patenting ovens in a van. Icing on the cake. Or should I say robotic top filling on the automated dough.

To honest though, they look like fresh pizzas. And if by some chance, the system yields stable long term value (happy employees and eaters) then.. why not.

That said anybody gets depressed by the dehumanizing aspect of this era ? drone delivering robotically made pizzas.. it looked funny in the jetsons but in reality I'd like to keep the good'ol restaurants with noisy people in it.

[0] "that we have yet to master" because it's so useless and we're so unqualified to understand it
Related from 2019: https://news.ycombinator.com/item?id=19725823
wait until you see their boston dynamics licensed cheese slicer.
Is it just me, or is this a rather low-quality article to post to HN given the subject matter and this audience?
What I think is odd is that it is so outrageous and conspiratorial sounding to even consider malicious intent on the part of the Chinese government.

I’m not saying I have any idea what the real impactful decisions that fuel this problem even are, much less who is making them, triple much less what their intention is.

I’m not sure it is clear what is really fueling the opioid epidemic, many theories of causation are plausible.

But it seems hopelessly naive to discard outright the possibility that aggressive intention by the Chinese Government is a factor here.

Countries have done much, much, worse to each other (and their own people) in pursuit of various strategic objectives throughout all of recorded history. Why should we flat out assume that has somehow fundamentally changed?
Fair points. “Simple” to me means a familiar API, and the fact that I don’t have to install any dependencies. I either add it as a git sub module or just copy the file into my project.

> Also, when coming across a project where other solutions exist, it's nice seeing an explanation of why you created your solution instead using prior art.

> However I get that because it's new, documentation probably isn't the main concern right now

I’ll be working on both very soon (life gets in the way during weekends!)
Domino's pizza was one of the fastest growing big companies in the world with a 30 minutes guarantee. It's quite similar to the pizza chain in Snow Crash actually. I would say Snow Crash predicted it before it became so successful.
Ask HN: Disklike of modern trends == Becoming a relic?
I have been in IT and software roles for 3 decades, yet nowhere near retirement. I still get a lot of stuff done (solo and teams), but only feel productive when pragmatic approaches are taken. I often find a carefully written but quick prototype is valuable while laying the foundation for a permanent system to be built if needed. Problem is, most of my company insists on first developing fully fledged platforms that attempt to solve years of future assumptions, while the business waits and engineers work excessive hours.

If I suggest a simpler prototype approach, incorporating internal customer feedback, with a second long term cycle of engineering, the response from peers and management borders on disdain or contempt. I am a team lead and get this response from all angles.

I’m no tech stick in the mud. Where scripting and RDBMS worked for 20 years, I incorporate “new things” where needed: Go for speed, Spark and S3 where vertical systems don’t scale; Rust when performance of a non-GC language is needed.

Conflict occurs when I resist over engineering: _Everything_ in a container; Kubernetes by default, as in 10 node clusters (am aware of its utility in much larger deployments); Clever code that will be extra work for future contributors to grok. Anywhere resume driven development appears to be creeping in.

I believe one of the responsibilities of management (and team leads) is to reign in architecture astronauts, but I rarely see it and am discouraged from doing so, in some cases due to fear of upsetting the “10X engineers” [1].

I have seen this across 4 companies in 15 years, with increasing severity. Is “build to minimum requirements” no longer appropriate? Have I selected roles poorly, and my experience is abnormal? Do people still just get stuff done both in the short and long term [2]?

Or is it time to hang up my spurs and take up golf?
The submitted title was "Goodwin: Did the early internet activists blow it?", but we've switched to the article's own title, as the HN guidelines request.

https://news.ycombinator.com/newsguidelines.html
[1] For context I put zero belief into the idea of the 10X engineer or full-stack developer. Most real world projects are addressed by a _team_ of people that must work in concert. The idea that one of them is superior to the rest is toxic - and most often nothing more than an overgrown ego.

[2] “Get stuff done” != “Break shit and move fast”. That is an entirely different problem. I’m not referring to disrupting industries or putting people in space. I’m referring to typical, somewhat mundane business technology.
Because the company with the de facto monopoly on web search is the same company that bought the company with the de facto monopoly on user generated video content.
Blizzard moves previously canceled Overwatch League games from China to Korea