skysight-inc/HackerNews huggingface dataset:
If you consider how fundamentally broken speculative execution from a security standpoint is, then a fully "fixed" processor will be significantly slower than unfixed ones. The benchmarking clause rather clearly shows this.
I'd suggest a two-stage process:

(0) Learn how they do things there, and why, and gain the respect of your coworkers by getting really good at it. You won't find you can make much progress along any axis without people perceiving you as already being successful.

(1) Write all the unit tests you possibly can for as much of the codebase as you possibly can, and try and get the rest of the team onboard with a solid testing philosophy. Extoll designing for testing and testability.

(2) Use these to confidently move through the codebase and replace portions as necessary.

This is the 'replacing the engine while the car is on the freeway' approach.
We're working on that though - many different species of pelagics are threatened by human activity :-/
This New York venture firm just closed on $520M from 250 people
Working anymore than 40h a week as developper for someone else is non-sense is you just earn a fixed salary
legendary hero
This. Don't change the code until you have reasonable test coverage. Only changes to enable testing should be allowed.
Eh, no. They did not discover that mining sites are being placed in deep locations. They discovered that whales visit those locations because they dive deeper than thought.

So maybe: "Deep diving whales may cause licensing issues for prospective mining sites".
React Native vs. Xamarin: Which Is Better?
As trucks account for a high (90%ish) amount of road wear, they actually probably should pay a high fee. Accurate costs might also make the rail freight industry more cost competitive, leading to better market diversity.
A lot of the bundled type of spyware I've seen relies on users clicking "I Agree" on an EULA. The problem is nobody reads the EULA, they just want whatever software it's attached to as quickly as possible.

I suppose my point being that just because users "agreed" to something doesn't necessarily mean they knew what they were agreeing to at the time.
Home Assistant: Open-source home automation platform running on Python 3
It was much easier to find places like that, though.

The rust belt was booming then. There were more options. Now for the best opportunity you have to take a risk and live in the major cities with astronomical housing prices or long commutes.
While I was thinking about moving permanently to Japan, I had a fun notice: in order to get japanese citizenship, I have to give up mine russian and I could be counted as a traitor in Russia (no peace treaty for 74 years and counting!).
I've actually seen it done within a large organization. It takes one boyscout who's respected and can clearly demonstrate the value provided by testing and designing for testability, and people will fall in line. Nobody likes building on quicksand, so show them what concrete looks like.
Microsoft Bug Testers Unionized. Then They Were Dismissed
I don't have any hard and fast rules, but if it is a big complicated project I don't usually try and come up with a single coherent diagram of my thoughts. Instead, I start out with a node for the date, and a child node for a subject, and child node of that with a sentence or two concerning a topic I'm working on. If there are more details to it, problems, questions, etc. they become sub-nodes of that, and so on.

I don't usually change the details of nodes that I already worked on, but rather write what has changed in a new node with the same name but under a later date node. I find that it becomes a mess if I try and keep every node updated to what I currently think about it, because too much information builds up to efficiently do so. Also, a lot of what I write only make sense in the context of what I wrote on other subjects during the same time period, so if I change one, I end up having to rewrite more and more, which eventually becomes a big mess.

The main benefit is that I can go through my notes quickly, skipping minutia of topics I'm not interested in simply by not reading the details of a node. I used to use a text file, and that was a very big problem, because not only would the amount of text that I'd have to go through became daunting. Also, I sometimes found it hard to interpret what I wrote, which means I wouldn't know if it applied to the problem I was working on or not.

However, in contrast to the above, I do try and make a definitive structure if it's a small topic or a quick idea for a new project or something simple like vacation plans.

BTW, it also works very well for taking notes for a class or self-study.
No matter how you model things and no matter what technology you use, a race condition like this needs to be handled one way or another. You either handle it such that the data is always consistent, or you handle inconsistent data.

You can use an SQL database with transaction and locking to ensure that you will never debit money that isn't there. Or you can save commands in a queue that only a single process at any given time (that incidentally includes the SQL scenario). Or you can use a distributed consensus algorithm with multiple stage commits. There is no way around it.
They didn’t even have a look at the code. Their task would have been to write and maintain end-user documentation and they left before they even had computer and stuff set up. Just never came back from lunch. Said they’d not feel up to the task. I was just a student at that time, so I can’t really say if that was a hiring fuckup or just an odd person. Certainly one of the weirder things to witness in my career.
Instead we get Electron, and people use it to make text editors that take up 500 MB of space.
POCO F1 Review: Xiaomi's OnePlus 6 Killer
>we as a society need to start thinking about how to halt the service-ization of everything.

People don't care unfortunately. Services are convenient and offer a better bang for the buck in the sort term. At some point though you lose your job and your music library is gone, you have nothing to watch because everyone streams and thus the movie/show selling market was never forced to solve it's copyright issues. You have no car because it was leased and you have no place to stay because the landlord kicked you out when you missed a rent( and buying an apartment or a house is crazy expensive across the board for some reason I still don't understand).

>Do we want to live in a world where every device is a black box that's only reparable by "authorized" personnel, where some hobby-level engineering skill won't help you prevent a 1$ dishwasher repair from costing 100$? Where every appliance comes with a plan, favors a "platform" and will make your life a headache if you disagree, serves you but also who knows how many other masters and economic agendas, and inexplicably goes dark because bankruptcy, bugs, hacks, your guess is as good as mine?

We need to find a way to make manufacturing electronics cheap. The cat is out of the bag and electronics and software will become part of everything. Maybe a smart fridge is a stupid idea now but it might make sense in a different context. I think Japan has been big on various home automation for many decades now before sv decided to reinvent the wheel but the cases I read about were much more respecting and user-controlled.

>Constant wariness and justified cynicism are exhausting and dehumanizing and will do their part to sap an entire society. We know how this goes in the case of corrupt illiberal states, but ending up in that same place via a corrupt corporate culture/state is also possible, happening as we speak even, and halting that should be seen as another layer of defense for the liberal order.

There is no liberal order anymore. Have you noticed how everything today is tense? Like every interaction has to be within very narrow and at the same time arbitrary limits? How everything even slightly political turns into a shitshow and not just online. Everyone has to be super careful of his/her personal ratings and there is no room to vent off and do your own thing because if society finds out it will tear you apart.
Redis is still very much open source and free; the difference is that there will exist some amount of code under Commons Clause which will support its further development. Moreover, nobody is forcing anyone else to use any of that Commons Clause code.
Interesting. Thanks for that. Sometimes we can get so caught up in our own tech-bubble that we don't really notice the usage patterns of the average user. So it's often nice to have a reminder like this.
My ISP / telecom provider (in my case they're the same company) is a legitimate corporation registered in my home country, against whom I can seek legal recourse if my data is misused. That's more than I can say about most VPN providers.
I have never had a salary job that did not require on a regular bases over 40 hours a week. I worked for a college and during August I would work easily 70+ hours a week getting ready for the school year.
> I’m going to assume that this job pay six to nine times more than the average developer can make

[...]

> I’m assuming there is no such upside.

So which is it? :)
Pocophone F1 review: Can’t argue with Snapdragon 845 for $300
This is why I stopped practicing law and started my own web design company where I could set my own schedule. We strive to work 35 hour weeks and usually come in around 35 to 40 per week. Burnout will happen at higher numbers.
I’ll admit in my early 30s I did 7a-12a 5 (sometimes 6) days a week. But I was the founding CTO and had a good amount of skin in the game. My hours broke down as: 7a-4p support, calls, meetings, being available to the team. 4p-12a working on my coding tasks.

It also involved walking around 6p-7p and “kicking out” others. Very rare was anyone else there on the weekends with me.

Do I regret it? No.

Would I do it again? Hell no.
My team at Vivint, the Space Monkey group, stopped doing whiteboard interviews a while ago. We certainly used to do them, but we’ve transitioned to homework problems or actually just hiring a candidate as a short term contractor for a day or two to solve real work problems and see how that goes. Whiteboard interviews are kind of like Festivus but in a bad way: you get the feats of strength and then the airing of grievances. Unfortunately, modern programming is nothing like writing code in front of a roomful of strangers with only a whiteboard and a marker, so it’s probably not best to optimize for that.
I think somewhere there exists a perfect happy balance between work hour requirements, project productivity and employee hours. My ideal candidate is okay with a 45+ hour requirement, BUT does not become a clock-puncher. Hopefully putting in 50+ because they want to or are deep into a project and can't step away. But, will easily coast out of the office after 40 hours on occasion.

I think the focus needs to be on setting a reasonable baseline and encouraging productivity without sacrificing well-being or the work/life balance.

edit: I think maybe I wasn't clear about my last point. I'm very much on the life side of the work/life balance. I'm okay with an employee who puts in 35 hours but is meeting/exceeding expectations. In fact, I encourage it. It's up to the manager and the individual to have an understanding of what's expected.
They aren't playing with the courier change anymore.
I assumed the tests were were ran on the new microcode version, as it was released a week before the tests, but it seems that Ubuntu didn't ship that update yet.

Their security advisory says that

> Optimized L1 data cache flushing is available via intel-microcode updates. The updated kernels implement a software fallback cache flushing mechanism for processors that have not received microcode updates.

It looks like the kernel will say "VMX: conditional cache flushes" on the new microcode so according to the Phoronix screenshots, they were running the older version.

Maybe we'll see a new set of benchmarks.
Goat into the car 2018
I suggest you read up on how VPNs actually work. You're just tunnelling traffic through someone else's connection. A VPN app included in your OS would relay all of your internet traffic through whoever wrote the OS (unless they partnered up with another provider, I guess).

I'll give Apple the benefit of the doubt but I'm not sure I'd be keen on this kind of setup in the case of Google or Microsoft. Then again, they have access to all of your browsing data anyway via the OS so what's to lose?
Yeah. Good luck filling that position when there's plenty of tech jobs that are sane, healthy, and respectful to their employees.
I don't know why you're being downvoted, but that's part of why I posted what I posted.
HN demographics plays a role, of course. More discrete and tailored manners through headhunters or, at the other end of the spectrum, cold calls to engineers working at direct competitors in your niche should give better outcome.
I think this is the relevant graph [0] for what you're speaking about - price changes of selected US goods and services from 1997-2017.

[0]: https://imgur.com/a/JVjIQ8r
Many earners are part-time earners nowadays. If you want to make that point, you may want to look at the median income for full-time jobs ($50k for men).
It should read:
"100 million suckers have signed on to pay $119 a year for “free” two-day shipping instead of free 4-5 day shipping"
Suppose we did what you said, and the back button only ever took you back to the previous URL.

I could still make a JS app that, on your first interaction with the page, moved you forward from https://example.com/ to https://example.com/#home. Then it sets a variable such that when you go back to https://example.com/ it shows a fake SERP. This is not an easy problem to solve.
For context: Firefox greys out anything that is not the "real" domain, which remains black. So:

google.com.fakesite.io/foobar

becomes:

(grey "google.com.")(black "fakesite.com")(grey "/foobar")

This makes it at least a little more obvious you're not on Google.

Although that's still a tricky one for non technical users to protect against. Aside from EV, I can't immediately think of anything else a browser could systematically do to guard against this, to be honest. Blacklists etc, but that's very unsatisfying.

It's a pretty old problem, to be fair. I remember almost being phished this way myself back on Myspace, were it not for Firefox's blacklists catching the form submission.

Domain names being little endian has been one of the most expensive web sec mistakes in history.
Samsung to Launch Galaxy A-8 Star in India
That would require storing where they came from as well as waiting for--or forcing--them to visit at least one more page on the attacker's site. So it'd still make backjacking harder.

Maybe pages that immediately redirect on first arrival should also not count toward back history.

Now a more perfect solution would require browsers snapshot where the user cane from then block or warn about pages at the destination that look too similar. Though that seems unnecessarily complex for most users.
In many programming languages, a % b is simply a - b*(a/b), where '/' is integer (truncated toward 0) division. I'm alright with this because:

1. this computation is typically more efficient on silicon optimized for arithmetic,
2. this computation is unambiguous and more straightforward to people who are unfamiliar with modular arithmetic, especially when negative a and b are involved, and
3. in contexts where the mathematical remainder 0 <= r < abs(b) is needed, b is typically always known. It is easy to see that knowing a % b and b it is easy to recover r, but knowing b and r, one may not recover a % b (we don't know if it was positive or negative).
Compare the benchmarks for those processors?
I started working on a huge, 10yo< codebase with ~500k LOC, but this was mid/large company with >50 developers with framework version from 2013. Now it is ~300K(unused code removed, some parts moved outside+rewritten), framework is the latest version etc., this was done due to a very good leader with a vision. Nothing prevents you from becoming that person that fixed that infamous project.

It is ok to complain about code quality, as far as you are doing something to improve it. Don't ever complain about a previous engineer, they might have been just implementing the sh*t product was enforcing on them or company asked an inexperienced engineering to glue together this project. It is rarely that a developer knowingly and happily writes bad code.
Try to improve it, it will move you towards becoming a senior sooner, nothing helps you in understand how to code more than how-not-to examples. :)
Also +1 to do-not-refactor-immediately comments here, observe the project and company and write tests until you know the project and culture well enough, then either increase refactor speed thanks to your tests or separate the project into chunk as micro-services or utility libraries/modules.

Also run static analysis on the codebase, you will be amazed how much "foo defined but never used" cases there will be, remove them completely, have a close eye on production errors when you release them and role-back on smallest of suspicion something is wrong. invesitage, fix, release and repeat. :)
What myth?

As you say, bigger companies have a harder time innovting.
Show HN: Reducing the size of PCSA to that of HyperLogLog
One thing I haven't seen mentioned is drawing a graph of dependencies using Graphviz. It's immensely useful for my current task - removal of two obsolete, fundamental variables from a convoluted permission system spanning a very big project. As a bonus, managers love it because it offers visual feedback.

Normally, unit tests would be the solution, but my ticket spans more than 10 modules (files), some of them suffering from the God Class syndrome. It's infeasible for 1 person with only moderate experience in unit tests to write enough tests before he's fired for not showing results. But it made me realize how important having unit tests in place is, and I made a resolution to write them for my future tickets spanning a single module.

Graphviz uses a super simple DOT notation that is perhaps best explained through showing the gallery. If you click on a graph image, it takes you directly to the source.
https://www.graphviz.org/gallery/

With a big enough graph, GUI tools like Dia or Astah.net just don't cut it anymore. Graphviz lets you focus on the only thing you care about - content, and the visualization algorithm takes care of positioning. Because the format is a text file, it's a very good fit for git, you can attach a modified graph to each git commit.

Graphviz is also a great fit for vim. For example, to color all edges leading to particular node, you can type:

:%s/-> ParticularNode/-> ParticularNode [color=red]/gc

Or you can manipulate lists of nodes or edges with VISUAL LINE select mode and type :sort. Lots of possibilities.
It's easy to extend a graph copying and pasting modules (subgraphs with cluster_ prefix ) or anything else, and it supports attribute inheritance so you can cut down on redundant lines. Just declare a node style, for example:

node [label="update"]
update0;
update1;
update2;
update3;
update4;
node [label="create"]
create0;
create1;
create2;
create3;
node [label="\N"] // this resets node labels to default behavior

This way you can have the cookie and eat it. All methods of endpoints are uniformly named, but it's not ambiguous which one is which.

And the kicker - graphviz was initially developed by AT&T, so you have a BIG NAME to back up your tool choice.
>will easily coast out of the office after 40 hours on occasion.

This is sad to read. 40 hours is the max unless you are paying overtime.
Fuck your carbon tax scam
A total disaster. From all I know, any thorough fix of the exploits of speculative execution will slow down the processers significantly. Unless the terms are just a terribly blunder (which would be bad enough on its own), this points to a rather big marketing nightmare to show up. First of all the bad PR for those terms, and of course, sooner or later there will be thorough benchmarks on the net. I would even guess, one of the larger hardware review sites will openly ignore the terms and run them and wait for Intel to sue them. I could not imagine such a law suit achieving anything but directing even more attention to that publication and the obtained results.
My ideal candidate works 35 hours in the office, is engaged enough to think about work problems in their "shower time" and has enough energy to be effective whilst they work.
WOW. As a former Music Theory 2 and Music Theory 3 student in college this is awesome. I am also very disappointed in myself for not trying to do something like this and failing earlier in my life.

There is really a lot more that could be gained from this work. I am sensing someone's PhD project.
Iterative refinement. Start with the most problematic parts of the code and work from there because you don't want to have to redo code because it didn't mesh with the higher priority fix. Unit Test extensively!
It’s just a populist move by a shit right wing government. But they won’t be around for too long.
Also: Is there a 'Hacker News' with less politics and politically motivated voting? Please?
Show HN: LAN clipboard using socket.io and Vue.js
Ask him/her the exact same question: „What questions would _you_ ask to evaluate a tech lead?“ This will tell you his/her priorities for the job.
Dr. Death
Thomas Kuhn Threw an Ashtray at Me
That 60+ hour week job ad is a bit weird- surely anyone good who reads it would immediately be put off? Why would you include that?

Then I read the CEOs reply after being called out for it on Twitter: https://twitter.com/larbysamirouche/status/10314168074526351... If you don't want to look at twitter:

"Update: @dhh Nobody @GitHub cares about your tweets. The post expired. Focus on your irrelevant development framework, failed career as a race car driver, or Basecamp, which as you know, has no future and has been replaced by much better alternatives that are highly innovative."

@dhh created Ruby On Rails

No wonder their website is still "under construction". Who funds these kind of narcissistic idiots?
I am in the market for a new rig- looks like I'll be going with AMD.
Everywhere else immigration and Japan are mentioned on HN, the consensus seems to be that Japan is doomed to lose its unique culture and societal cohesion due to immigration and the loss of its ethnic homogeneity... but apparently not when "we" are the immigrants.

Odd, that.
I guess you don't put locks on your home because you have a 'dont come in' sign on the door right?
Ask HN: Modern alternative to Facebook events?
I have been without Facebook for about a year now, and the one thing that I really miss are events. On the one side, there are a lot of events that go over my head simply because they are advertised solely on Facebook. And while I know I cannot do anything about that other than having a Facebook account, what I also miss is a convenient way of managing my own (social) events, being able to send updates to my guests, changing the event details, etc.

I feel like Doodle covers part of it, but I've always used it in a formal/professional setting to schedule meetings, and I think that a Doodle invitation will be perceived as such. I wonder if there is an alternative closer to Facebook events that allows me to manage my (social) events?
They'd definitely show reproducible results. eg either get their mates to submit matching fakes ones, or just submit an extra set themselves after slight tweaking

That being said, as soon as someone with a clue comes along + tries them out and finds it's bogus... that would lead into potentially weird territory too. eg the dodgy submitters likely attempting to discredit the er... whistleblower(?).

Seems like a re-run of an old story. :/
Watching neurons in action
Do you expect these hours to be as effective as, say, a 40-hour employee?
Would be cool if this was blown out by the courts.
New from Intel: the Scrum processor.
Beijing retaliates as new US tariffs kick in on $16B of Chinese goods