skysight-inc/HackerNews huggingface dataset:
Have a look at Steam. Their recent view is brilliant, and they'll flag it for the user if a long time solid title suddenly gets a barrage of negative views.
I know this is about Japan, but I did something similar. I went from San Francisco to Saigon about 2 years ago. Significantly lower cost of living, motorbike culture, great food and craft beer, super friendly people, easy travel to other SE Asia countries. I don't regret it one bit.
> I'm sorry but for this particular problem I have no sympathy

Isn't that part of the problem. Lack of sympathy?

Everybody makes mistakes from time to time.. and research shows that higher penalties have little effect.

Someone else pet peeve is people parking illegally because it blocks their drive way. Or blocks emergency vehicles...
I've read otherwise but couldn't find anything with a couple min free time. Anyone else read/know about this?
This is certainly sarcasm.
I wish... even GitHub won't work properly without JavaScript enabled these days.
Is this five different OpenAI bots cooperating in the game, or a single engine controlling five boots?
I've been on both sides of this issue in the span of my career. I've joined companies with absolutely horrific code, and I've hired people who thought my code was shit.

My advice is don't complain and don't attempt any significant rewrites for the first 6 months or so. Your job at first is simply to understand the code and demonstrate that you are able make improvements to it without breaking everything. Doing so will win you the trust and respect of your teammates, whereas if you come right out of the gate trying to rewrite everything there is a very good chance you will make yourself look like an ass by spending a lot of time and energy introducing bugs into a previously-stable area of the code. Once you have a decent understanding of how and why the code is the way it is, and the trust of your teammates, then you can invest effort into fixing the highest-priority issues with the code.

Being able to read and work effectively in legacy code is an essential skill for any software engineer. For now you should just try to focus on fixing bugs and implementing new features, and take pleasure in the fact that you are improving the project and developing a handful of hard and soft professional skills.

That being said - there should be a limit to how much bullshit you put up with. If after six months to a year you still find that you hate the job, and a better opportunity comes along, then go ahead and take it.
> By extension, you should take every back road while you drive, rather than the freeway, because there is a minute chance that you increase probability of human death by going 65 on the freeway rather than 35 on back roads.

Is it not illegal to be a pedestrian on a freeway where you are? Motorways are one of only three parts of the UK road system where pedestrians are forbidden.
That's the list and figure for women. For men you have to see the next graph which is slightly different. Then the next two graphs show you that outside of the US the opiod epidemic is not a big part of the reason. Then when you look at the 2016 estimates table you see that this is all just noise except for the UK and the US.
You meant domain name, not TLD, right?
Hi everyone! I did this. It was just a random cool idea I wanted to try. It worked a little too well and I quickly moved it to a disposable site to test if the page will get penalised by Google. I got busy with other things and forgot about it. When I bumped into it again I decided to write about it, for two reasons: 1) To me it's hard to believe that Chrome would allow for this to happen in the first place and 2) that Google wouldn't penalise a site doing this. Well, since the story was published Google tracked down my test page (most likely by using the source code I revealed on my blog) and completely de-indexed the whole domain.
They found one engineer who wanted to live in Japan and call it a story? You could do this for literally any topic about anything and call it a trend apparently
I'd like to compare the situation to the record industry, where artists usually get something around a measly 10% of the income generated by record sales. Artists are busting their asses of while the record companies are cashing in like never before. And yes, there are some artists that make more money than others, but they still only get a percentage of what their fans really pay them. I understand that they, being record companies or Google Play/App Store, need and rightfully should demand a fee for helping their content providers with a platform for their product. But at the same time, without the content providers, they would be nothing. The music industry has already seen the rise of various indie labels, artists starting their own record companies and such. And although I realize the difficulty in doing something equivalent within the mobile app industry, Google or Apple are already saying that you as a user should only download apps from approved and reliable sources, i.e. Google Play and App Store, I think we will see some sort of similar development. Perhaps companies will start providing app downloads on their own, create their own app store platform etc. Especially since the companies themselves get so little out of making their apps available on Google Play and App Store. They still need to market their apps for example.
The thing that concerns me is it's easy to wrap a JS API or unreference it if I know it's abused for ads/tracking. I don't know of good ways to go about tracking based on pointer events or scrolling.

I'd put more research into generating fake events or limiting them for an untrusted site, so mouse behavior can't be used for "where are they looking" analysis.
Like it or not, it is your responsibility to inform management if/when there’s a problem. It is their responsibility to decide what to do about it. Be transparent about the impact that the current codebase is having on your estimates, bugs in your code, and job satisfaction. Analyze the situation and offer solutions. If you have provided management with accurate information, you will have no reason to feel bad about the outcomes, and there should be no surprises for anyone.

I understand that you do not wish to offend your coworker who wrote poor code. That’s good, but it is also your responsibility to find a non-offensive way to communicate when their work is not ideal. I recommend using “code-first” language when talking about the code. For example, do not say “what you’re doing in this function is wrong”, say “this function is incorrect” (basically just never say “you” when discussing the code.) If they get defensive, remind them that your goal is code quality, and that you are not trying to be offensive. Be precise, informative, and most importantly: humble.
> OpenAI is a non-profit artificial intelligence research company that aims to promote and develop _FRIENDLY AI_ in such a way as to benefit humanity as a whole.

I find it amusing & ironic that they're pursuing games of efficiently & strategically killing enemies as examples of their successful progress. ;-)
> assumes most of the modern web is worth using

But it is, are you really going to ignore reading some huge breakthrough in physics because the site uses react? Also in many situations there's absolutely no other choice. Government sites, e-stores, banking.

And then there's the buildup of recorded urls. Private browsing is somewhat less useful when your scipt blocker whitelist is full of porn sites.

I use it for security in specific browsers but happily admit it's not an actual solution for normal people. Adding another 3 clicks, then another 2 for the inline JavaScript contained within after reload makes the internet incredibly annoying to use.
This is a poorly written advertisement.
Wow. How in hell did they (Saudi Arabia) manage to become the Head of the UN Human Rights Panel ?

https://www.independent.co.uk/news/world/anger-after-saudi-a...

Reeks of corruption at the highest level.
Modern version: http://www.nuclearsecrecy.com/nukemap/

(no reason to use classic except in very rare circumstances)
Not really answering the question, which was "how do you know it works?"

I would contend that if you have proven to yourself that your code works and are therefore capable of proving it to other folks (via e.g. solid testing), you should not be ashamed of the spit and glue.

It is research code, we all know what that looks like. But if, on the other hands you haven't proven to yourself it works, then it's definitely something to be ashamed of - scientifically speaking.
I'd be curious how many of them were engineers.
> We’re heading for a future where the only people that can afford to write OSS projects that actually influence the world are those who work for FAANG or in academia.

I think the strength of an OSS project (or really a single individual at that stage) can be to innovate - make something that in a corporate setting, FAANG or not, can't be pursued because it hasn't a chance to become projected since business value isn't tangible, and anyway needs meandering around to find solutions in its problem space. Once something demoable is created, it might attract corporate backing. But corporate development is actually very bad at developing the kernel of something not seen yet. Maybe there should be a market place for initial designs/concepts to grab beyond VC funding?
To anyone who is thinking about going: you should really go.
My student who was of Korean decent but was the most popular person in high school and went to a good university would disagree with you. As would my friend who was born in Korea, married a Japanese woman and moved to Japan. There is discrimination in Japan, but it's frustrating to see this trotted out time and time again as if you'll be systemically discriminated against no matter where you are. It's just not true.

But if you don't speak Japanese, it doesn't matter if you are Asian looking or not, you won't fit in here. There are lots of other ways you won't fit in here too. Not speaking Japanese well is an absolute deal breaker, though.

Edit: I should point out that there is nothing wrong with the Wikipedia page. As far as I understand what it states is absolutely correct. It's simply that Japan does not have dual citizenship at all. So if you want Japanese citizenship you can have it -- you just have to give up your other citizenship. Japan also does not give citizenship automatically if you are born here. You have to have at least 1 parent who is a citizen. However, you can apply for citizenship and you will get it -- as long as you give up any other citizenship. Otherwise you will essentially have permanent resident status. The latter point is admittedly crazy and it is very unfortunate that many Koreans are born into this situation, but they can fix it by naturalising. They don't want to. BTW, the student of a friend of mine was American and had exactly the same issue. It's not an issue of racism.
But is it real, 6-core 3GHz+ i7? Or is it this mobile crap Intel has been pushing lately?
> "Finally they let you hire some help and instead of getting busy helping writing tests and refactoring he starts thinking about the best way to throw you under the bus to your superiors."

Here's what actually happens.

By that point in a project's lifecycle, that's not what they usually ask of the new hires. People are usually tasked with fixing bugs/maintenance, and implementing new business logic. Both of which are extremely challenging and stressful when working on a project that comes with no tests, or documentation.

Your actual task as the new hire is to start generating more value for the company, but that's so much more challenging when you have no way of validating your solutions, no infrastructure to rely on, and no metrics or documentation to consult. At that point, being the new hire, you're taking a lot of heat for not getting things done on time - mostly through no fault of your own. At that point, "wanting to throw you under the bus to your superiors" is a very natural response - it's a defense mechanism, you're (rightfully) frustrated. You're between a rock and a hard place. At that point you're no longer doing software engineering, it turns to politics/coverups/fire-extinguishing on a daily basis. Can you not relate to that?
The Unlikely Return of Birkenstock
> Isn't that part of the problem. Lack of sympathy?

For breaking the law?
Show HN: Json-aggregate – js utility to perform aggregations on JSON data
Yeah, there is not even a good model. The UniProt entry could use an update (Human, https://www.uniprot.org/uniprot/Q8TDI8), I will pass it on to my colleagues.
I quite like reading this guy's point of view - and Anthropology PhD candidate studying atomic weapons:

https://deusexatomica.wordpress.com/

(Sadly gone quiet. I hope he got his degree and is doing something fun...)
Obviously, they already do. The company is willing to pay this amount and there are enough people willing and able to work for this amount, hence the amount is correct.
B is utterly unacceptable if you're funded by public money. As a matter of fact, I don't understand why public research grants don't come with a binding obligation to make all results available, including source code.
While I do not regard it as an accurate view of cities, I also do not regard it as “extremely bizarre and off kilter” — I have noticed similar patterns of hyperbolic anti-city thoughts amongst many people who prefer rural areas to cities.
It'd be ironic if those sea floor nodules have value now. "Mining" them has an extremely interesting cold-war story.

https://en.wikipedia.org/wiki/Project_Azorian#Building_Gloma...
My opinion of Bruce Perens just decreased markedly.

Hopefully he will edit this blog post with better advice to the "casual" computer user.
"Elusive Whales Set New Record for Depth and Length of Dives Among Mammals. A new study of elusive Cuvier's beaked whales shows they can dive to nearly 10,000 feet (3,000 meters)." [1]

[1] https://news.nationalgeographic.com/news/2014/03/140326-cuvi...
I started using NoScript a while back, just to see what the web is like without Javascript. My plan was to uninstall it when it got too annoying, but to my surprise it's actually not bad at all. I'm quite lax in whitelisting domains I actually trust, but even then it's nice that it doesn't load Javascript from all other umpteen domains, which is often the case.

Of course it's a very blunt weapon for blocking abuse like what's described in this blog post, but for sure it works.
Hyundai leads $14.3M investment in Indian car rental startup Revv
I agree with your core thesis, but it could probably have been expressed better. In the USA there's a moral system that some people have that equates wealth to virtue. In my experience, it leads to conclusions that are generally dehumanizing and unempathetic of others, which is definitely not a long term sustainable foundation for a free society.
I fail to understand the issue here - Successful companies do often stretch the limits of engineering to fit design goals (assuming that the design is an informed one to begin with). If design was always fitted around what is known to be possible with engineering, we would have much less innovation around.
It sounds a lot like you are blaming someone else for not having control of your computer.
> In Germany there is no (general) speed limit

Yes there is. The autobahn may be roughly 50% without speed limits, but every other road has speed limits.

Unless otherwise indicated these are 100 km/h between villages, 50km/h in cities and villages.
Isn't a big chunk of wash trading om a dead asset an issue? Doesn't that indicate something unsavory going on? Ianal, but, my understanding is that wash trading us illegal on normal markets - and for good reason.
I once did a major cleanup at the start of my career. The above advice is closest to what proved successful to us, together with the response by JohnBooty https://news.ycombinator.com/item?id=17825093.

In our case, I think we didn't write a lot of tests, because we didn't know they're so useful then. But much later I did a few ports of FOSS software between programming languages, and comprehensive test suites were absolutely godsend in those cases. So, if you can, try to write tests as first thing indeed.

Other than that, we took a kind of "organism fighting a cancer" approach. In a spaghetti codebase, we tried to find some smallest possible islands of the most isolated code (a lot of detectivistic work). Then try to improve the isolation even more — slowly engulfing the "tumor" in a more reasonable API. Once we had a somewhat acceptable API, with mostly well understood semantics, rewrite the internals of the tumor from scratch. Rinse and repeat.

Notably, as mentioned by JohnBooty, we did talk this with management. It made our product release late by ~1yr. The argument was that there was a particular critical bug, which would result in lost consumer data. This one bug was found very close to original release date, and opened our eyes to the horrors in the codebase (actually, a big part written by a subcontractor).

Sorry if the reply is somewhat chaotic, I didn't have much time to write it.

EDIT: Also, I believe the term "technical debt" is reasonably good when talking with management/owners, as it has correct connotation of an investment at early stage, which however has to be repaid later at a cost.
If you want better quality watch the viedo by dota 2 rapier
Copying someone elses site and tricking their users to use your copy is a copyright violation and fraud. Nothing cool about it.
Thank you Cyrus. I thought it would be obvious that this isn't a practical tactic a reputable brand could risk doing.
Completely disabling Javascript isn't feasible, but you can use uMatrix or NoScript with all scripts blocked by default, and only whitelist ones on sites/domains that you trust.
Just say one of our grad students implemented your ideas. Done.
I think browsers currently have to limit the precision of their built-in timer APIs and they had to kill shared mutable state support for their thread APIs so attackers couldn't implement their own.
Pretty much. Though it is still bullshit
Even if I trust you about the code being really bad, I'd still advise you to read this: https://www.joelonsoftware.com/2000/04/06/things-you-should-...

Joel makes it pretty clear that all codebases go through some kind of "maturing" where the quality is lacking, usually. It kind of made me change my opinion and approach to old codebases. Still, I think /u/freetime has the correct idea in not jumping into refactoring the first weeks of your job. Makes you look like a jackass (I made the same mistake at my current job). It might hurt, but I'd also advise to wait with improvements.
My five cents: maybe try and work on setting up testing for the project?
That's exactly right. Google has already punished me once for exposing a flaw (which they still haven't fixed): https://news.ycombinator.com/item?id=4748094
Sort of makes you wonder why the word "sequencing" is used to describe the procedure. Sounds more like throwing the vase on the floor and carefully picking up the pieces.
> I don't really speak legalese, but does permit include having to then make all of your own users agree not to to avoid a penalty?

As a service provider, you will need to inform your existing users about this restriction and put the restriction in your user agreement for new users. After that you can relax, if any of your users publish benchmarks, you'll have to warn the user and then take the benchmarks out. You don't have to actively search for violations, but if you notice one on your own, or you get notified (for example via email), you'll need to take it down.

If we're not allowed to share the results of benchmarks and comparisons, the only action that comes to my mind is:

1) Never buy Intel again, if presented with a viable choice!

2) Prepare and share ready-made benchmarking live USBs/utilities, so people can see the horrors Intel has caused them without violating the license.

3) Dump benchmarking results online from countries, where the Delaware courts mentioned in the article has no jurisdiction upon.

4) Get every copy of this microcode license prepared for different countries, sue the license in each of them, and have Intel struggle with it.
As also a native german, I have to disagree in turn. Story time:

In the 90s, when the Internet started to come into popularity, me and friends were desperately trying to get a connection that didn't cost money per time unit.

For the longest time, with no free local calls like the US had, that simply did not exist, at least via dialup. One option was a "Standleitung", which was almost literally a permanent landline between you and your provider, same signaling and all. Only small providers would usually be talked into it, but then you had to pay a (at the time) huge monthly fee to the Post/Telekom because the line took resources away permanently. Some few people were lucky enough to be able to establish radio channels with their provider (this was long before WiFi was a thing). At one of my first jobs, I got ISDN "callback" as a benefit, which meant that I could call the router, hang up immediately, the router would call back and establish the connection, company would pay!

Finally, after what seemed like an eternity, the first few flatrates appeared. Stay online as long as you want, download as much as you want (at speeds that were still measured in kilobytes/second, but completely adequate for the time). It was definitely Unlimited.
Hey, that's not very nice.
They needed black LPs with lots of money... engineer or doctor money doesn’t make you an LP at A16z. Where are they going to get them? There aren’t too many black startup founders or hedge fund managers. So they went where the money is. (I’m not sure if you’re aware that this list contains several tech executives such as John Thompson, former Symantec CEO).
Is this an appropriate place in HN to say "Me too"? :-) Moved here 10 years ago. Don't regret it for a second.

But seriously, in the past 10 years I've noticed a lot of high tech people either moving here or wanting to move here. When I first came, it was really rare to bump into a foreigner who was a programmer. They were either English teachers or factory workers. Now I run into people relatively frequently (even out here in Shizuoka prefecture).
Are you aware that all people die?
> the lock was being acquired and released ~49,000 times and was held for, on average, less than one ms at a time. But for some reason, even though the lock was released 49,000 times the Chrome process was never able to acquire it.

Well, locking is hard.

> The good news is that even though there is occasional unfairness, there is unlikely to be persistent unfairness. In order for a thread to steal the lock, it needs to hit the tiny window where the lock is available. In practice, a thread is unlikely to be this lucky repeatedly.

https://blogs.msdn.microsoft.com/oldnewthing/20170705-00/?p=...

> The fact is, any time anybody makes up a new locking mechanism, THEY ALWAYS GET IT WRONG. Don't do it. Take heed. You got it wrong. Admit it. Locking is _hard_.

https://yarchive.net/comp/linux/locking.html
Forget shared hosts, how about when I write something for my client on my employers machine? I'm using the software for the benefit of a third party...
This borders on unbelievable...

I checked at intel directly just to make sure this is true: https://downloadcenter.intel.com/download/28039/Linux-Proces...
The file https://downloadmirror.intel.com/28039/eng/microcode-2018080... contains the license file with that laughable clause included.

Now hand me the popcorn...
Mozilla Announces 26 New Fellows in Openness, Science, and Tech Policy
I would like to see the New York Times co publish benchmarks with phoronix (or whomever has the relevant expertise and credibility) with a box detailing the ridiculous license and an editorial suggesting Intel investors may have cause for concern about managerial competence.
That would be marvellous.
This kind of splice repair should be rare. It only needs doing when the original splice was badly done.