skysight-inc/HackerNews huggingface dataset:
Although we try to stay away from "creating a process" for everything, we've gradually implemented a way for people to give feedback more organically. The thing is, it's not the tool, form or questions you hand out - it's how people use them and think about them.

Over a period of time we started using Impraise (impraise.com), although it's not the best tool - it helps people to force to take the time and leave there current mindset to focus on something like giving feedback (on an equal base, because some people are just very good at giving feedback and keep on talking, while others are struggling and need to write it down). Every quarter, you review 2 other people. People read it, interpret it and carry on. However, I sit down with them after everyone has filled in the questions on Impraise (which are not the default ones, but they're pretty straightforward, like: "how good is the quality of your colleague's work?"). This information is used as a base to allow me to ask even more questions, like: "do you agree with this statement?" or "what could you do to improve this situation this colleague is describing?”. The result of this conversation are 4 things:

1. self reflection,

2. setting personal goals (which is mostly one of the things from the self reflection, getting more focus/attention than other things, which is not shared within the team),

3. create and/or help out with team goals, something we should improve as a team and shared within the team,

4. feedback on the process itself.

These results are written down as notes and then reflected on the next time we sit down.

We have some other tools, methods and things in place to have more of a continuous feedback loop - but it remains a living thing, rather than a set in stone method. If you have questions, you're always welcome to contact me :-)
What does it entail exactly? You get negative opinion from some people on twitter, but it doesn't stop you being on the news, political programmes, political parties or in the newspapers.
It's probably not something I should advertise, but a lot of my maths I learned from Wikipedia.
PS: Suprised to see no mention after 14+ hours on the entire sub-discussion that their tech stack appears to still depend on MongoDB (re: "service decay & delays").

Not sure what happened on this month's job thread (too late to delete?); it's not like it's a secret!

https://news.ycombinator.com/item?id=14902743 vs. https://www.coinbase.com/careers/477665

King_mansur 17 hours ago
[flagged]

AvenueIngres 17 hours ago
>* Our APIs are currently powered by Rails with a MongoDB backend

Everything makes so much sense now (Coinbase's single digit SLA)

--

In case you are wondering what technologies we use at Coinbase, we’re built using a combination
of Ruby, Node.js, PostgreSQL, MongoDB, Redis, Swift (for iOS), and Java (for Android).
Snap is in talks to buy Chinese drone maker Zero Zero Robotics for $150M-$200M
"one of my colleagues and friend was "forced" to quit the company because he scored really low on the jira burn rate metric"

This sounds totally insane. I Cannot believe this happens in real world.
Why are you shifting the goal posts? Also, Red Hat has not been a significant contributor to btrfs for a while (they've mostly been working on XFS and lvm/devicemapper) so them dropping it is hardly a surprise -- Red Hat is not the arbiter of what is a good technology, and there are many other parties that work on Linux.
Apart from "that, my friends, is science!", the follow-up he got is another nice example of https://www.xkcd.com/386/ — a.k.a. "Someone's wrong on the Internet"
Not only lazy but weak in academics.
That would be the P/E ratio. Luckily Red Hat is a public company so you can know both the P and the E. :)

Revenues in FY2017 were almost $3 billion per year.
Send your JavaScript as an image, then unpack it using WebGL.
Thanks, this is interesting. I am considering a similar 'until the kids are at school' approach. We will see how I want to spend my time when we get to that bridge, back fulltime, or maybe more time on hobbies?
Another question has to be asked: do they have the motivation to reduce the size of apps?

Earlier this year, Wechat released a revolutionary (kinda) feature called 'Miniapp', it supports releasing apps within Wechat itself (a bunch of xml/js files). All major Internet companies published their own miniapp in Wechat, which include s the most-used feature of their full app, and only takes less than 1MB of space. Guess what? the miniapps are not adopted by most users, it became just a fad.

This means most users are not sensitive to the disk space used by an app. Apps know this, and thus don't have motivation to reduce the size.
For a piece of jewelry, $300 is not that much money.

For a watch, $12 will do fine https://www.amazon.com/dp/B000GAWSDG/

The Apple Watch is neither a piece of jewelry, nor something that will just show you the time (something people stopped caring about wearing nearing 2 decades ago). Is that something worth it or not? Is that something a mass-market item? That's the question to ask.
ExtendedXP: Compatibility layer to run post-XP applications on Windows XP
I no longer understand my PhD dissertation (2016)
and on that day I would buy one. I don't need an accessory for my phone, something that merely extends its screen from my pocket to my wrist and that is all I see the watch as.

I have seen three reasons repeated over and over why people like them and it seems so minimal of reasons. like someone mentioned, no one seems to justify wanting one until they have it but then I just figure they have to justify it.

Airpods are very nice and those I can find every day usage for, exercising and the like. far more than having a watch on my wrist as I tend to sweat a lot while exercising and don't need that.

so when it does not require my phone because it is a phone, I might sign up. but by the time phones get to that size I would just slap it on my shirt like Star Trek
Facebook Developing Tablet for Video Chat and Smart Speaker
Right, but from what I've seen (though I'm not a JS developer, so I might be wrong) is that most projects are not designed like lodash. They are small, single-purpose libraries that would be much better served as part of a module of a larger library. That was the point I was trying to make with the whole "libstring" and "libleftpad" point.

I've seen people try to package JS projects inside a distribution. >800 nested dependencies is simply not sane nor sustainable. The fact that they're small is even less excusable because it means that there was an active decision to not consolidate them into a single dependency that is properly maintained.
Kubernetes runs on GCP, AWS, and Azure, and in various on-prem configurations (including on OpenStack).

Disclosure: I work on Kubernetes at Google.
While I understand/agree with most critics, some sound naif but it's understandable taking in consideration her age (architects use to age well). My take on her critic (first image only):

http://imgur.com/a/cHpor

How to criticize architecture? Start by thinking that architectural theory is based on values. An example: it's widespread in society that pretending is a bad direction, so using cheap materials pretending that are the real ones in order to mimetize certain styles is seen as ridiculous.

By the other hand you should avoid to criticize based on your personal taste and diving in the subjectivity. E.g:

http://imgur.com/a/UNTuC
I must be missing some nuance of the argument here. If it is nonsense then why is it in his paper? If you are citing poor quality sources then that tells us something about your paper and to not do so would be dishonest. We're not seriously saying that you should be trawling for similar ideas to your own and then citing them, just where you have used other work you must give credit.
I'm not sure I get the Dirty Writes example about not always being able to rollback: it first says going back to state A would lose w2[x], so it stays in state C. Then it says that aborting t2 can't go back to states B or C, concluding that the scenario thus can't be rollbacked. But what about going back to state A in case of a1+a2?
Every dependency can run code on every computer your project runs on. That means you have to trust its author to:

1. not be malicious

2. not write a vulnerability by accident

3. not get their computer infected, their email account hijacked, etc.

4. be wise in transferring ownership

5. not add a dependency with a license incompatible with your project

All the above concerns apply recursively to the dependencies of the dependency.
Yes, this is important:
Maven Central/Sonatype only checks if the submitted artifacts are signed (regardless of the used key).

The work is shifted to client, but there's currently no standardized way on how to verify dependencies and plugins.

There's an issue in the Maven bug tracker with the idea to extend the POM to allow trust information:
https://issues.apache.org/jira/browse/MNG-6026
> In Europe, the 'no hate speech' idea has very quickly expanded the concept of hate speech to include any rightwing opinion around certain topics (mostly religion and immigration related).

That's because last time rightwing speeches about religion and races (that's "immigration-related" really) were permitted and tolerated in Europe the result has been WWII and the Shoa, probably.
Thanks for the big write up, very insightful.

I actually own my own business so focusing on things during work time isn't too hard (Always too much to do regardless of the hours I work). The need for some social contact is an interesting one as I we are also considering moving out of the town we live in with my family. I think we will use that as an excuse to join some local groups and get involved with things and hence meet people that way.

Thanks!
That's a fundamental misunderstanding of the purpose and value of story points. I hope that comes up in retrospectives.

Aggregating them for an individual developer over a long enough period of time might work, but I wouldn't trust it without some statistical hypothesis testing backing the idea up.

But using them to evaluate productivity on a small scale violates the collaborative culture (people over processes) that agile is supposed to foster. I've also seen them misused by:

* mapping them explicitly to hours or days

* thinking they are estimates of value produced instead of work required

* having project managers point and pull in things for developers

I'm not sure what an individual contributor can do about that kind of cultural issue. Insisting on using story points properly seems academic or pedantic, but the second- and third-order effects are an expensive-to-maintain product, a decrease in velocity, and probably developer retention problems.

But, no, I've never heard of agile mistakes coming up in a performance evaluation or a 180 review for a manager.
Nuclear has the disadvantage that high-profile accidents actually happened, and the period where everyone in western Europe had to watch their food chain for bioaccumulative radionucletides tends to stick in the memory.

http://www.bbc.co.uk/news/uk-wales-17472698

Part of the problem was dealt with by export:
https://www.wiseinternational.org/nuclear-monitor/349-350/co...
That, exact, question is the question you get, and has got for years and years, when questioning btrfs maturity. It seems as if btrfs always "just yesterday" got mature just when that last thing was fixed.

Sorry, but I don't believe enough in btrfs to try it out for real (and don't have time to play with it just for fun). Especially when playing with more advanced features, the status page does not inspire confidence.

The paragraph on btrfs in https://www.patreon.com/bcachefs seems spot on and exactly the feeling you get after spending a decade of hope on btrfs. And that kind of review is exactly what you don't want on the brand new finally-we-can-store-data-properly-on-linux solution.
Decrypting Amber Rudd
You don't have to parse every single module at page load. You can defer, or only load code the first time it's used. This 10-15% of time saved is only on first load. If you have a web "app" it's not like the user will reload it over and over again like the old school server rendered apps, which still works fine btw, they are even faster now with faster computers and better network latency. So if this is not the problem of classic web apps, nor the problem of modern web apps, who's problem will it solve !?

Make cache-friendly modules, only abstract code that can be reused, keep the rest of the code in-line.
Well I guess a nationwide power outage will have bigger implications than Netflix going down...
same tool for gopher: http://git.2f30.org/stagit-gopher/file/README.html
I think it's quite strange that when respected and rational people like Elon Musk and Stephen Hawking warn against dangers of AI, some people still dismiss it as irrational FUD. Did you consider they might have a point?
Your data still needs to live somewhere and giant VMDKs being copied around aren't a reasonable solution, I'd argue.
You're proving my point - both disagreeing with the idea that sex and gender are independent, and hating and assaulting trans people, get thrown in the same 'anti-trans' bucket.

Wouldn't it be more fair, even necessary, to just say "he doesn't want pronoun choice to be enforced, and doesn't think biological sex and gender are distinct"? Why distort his views by condensing them to 'anti-trans'?
> If the file system supports snapshots, then the package manager could automatically ensure fully atomic package upgrades.

That's exactly what openSUSE / SLE do with snapper. Every upgrade or package install with YaST/zypper creates two snapshots (before/after) and you can easily rollback to an older snapshot (even doing so from GRUB). This has been enabled by default for years.
It seems like this is a very small gain. After the initial fetch everything should be cached locally. If it's not you did it wrong.

Am I missing something? How is this better than normal web caching?
I had no idea that was happening. Thank you for making this important point.
I set mine manually only once, when I bought it, and it has never changed.
You are assuming they are. This Dotcom clown could say there were aliens in his bedroom, would be compelled to believe that?
Ask HN: Apache Kafka applications to study?
I'm building an application using Apache Kafka, please suggest some open source application which I can study to understand how they use Apache Kafka.
That kind of economic warfare seems very risky to me. Miners, at least, are ultimately businesspeople, and the risk/reward for dumping either coin doesn't seem all that attractive to me. Why not just keep mining whatever they've chosen to mine, and switch to the other chain if it looks like they made the wrong choice? Or just mine whichever coin is most profitable at any given time?
Varnish Cache DoS Vulnerability
The Languages which almost became CSS
It sounds like justification for a decision made for less quantitative reasons.

Managers don't say, "So let's see who's the worst performer... it's Tom! Weird, he seems to be one of my best developers. Oh, well! The metrics say he's the worst. Off to fire Tom!"
What I actually meant that I switched platforms...
iPXE uses the iBFT[1] to pass this information to the OS.

ftp://ftp.software.ibm.com/systems/support/bladecenter/iscsi_boot_firmware_table_v1.03.pdf[1]
In Crystal, we've decided that the dependency manager shards will have no centralised package repository, which we hope will solve problems like this. It makes forking shards very easy, it completely avoids name squatting, and it should help prevent typo squatting like this.

We also don't want shards to become yet another system package manager, used for installing executables to your PATH. Shards should never be run as root, unlike npm and pip.
The particular bug that sparked that warning was fixed a while ago, but as a precaution against "btrfs ate my data" stories they've removed the ability to create btrfs-raid from the CLI tools (you can still use md RAID with btrfs but you lose most of the benefits of btrfs that way).
It's a good practice to use LVM there between disk partitions and volumes. It has negligible performance implications but makes things very flexible when you need to resize volumes or add space. You also gain reliable snapshotting from device mapper, although that does have some performance effects.
>CSS + HTML

AFAIK, CSS + HTML is not Turing complete, but CSS + HTML + "Human pumping tab and space" is, which makes infinite loops less of a problem.
$140k Blockchain Hackathon
I was an Informix DBA years ago and the other day an old friend who now works with a company supporting game developers told me that Informix is (still) really popular principally due to the way it handles locks and multi-concurrency. Surprised to say the least.
> What I'd really like to see is a JS implementation of the "dynamic" features like diffing

That's possible. I've made something like that (dynamically fetching git info via dump HTTP server protocol) using Git.js [0] although for a different reason and it worked very well. Some caveats: the decompression must be handled in a WebWorker or the UI is stuck pretty easily. But objects can be fetched on demand so it's kind of like Microsoft's Git Virtual FS. As you've said cross origin policies apply so either have the viewer on the same site as repos or add appropriate CORS headers.

[0]: https://github.com/yonran/git.js

I see git.js even has a "repo-viewer" demo [1]. Although it's very primitive it shows the ref list and diffs.

[1]: https://github.com/yonran/git.js/blob/master/demos/repo-view...
How Banking Trojan misuses accessibility services which are meant for disabled
Typically you use flow with Babel so you can use newer JavaScript features. Babel creates messy JavaScript in the process of transpilation.

Typescript combines typing and transpilation together, essentially doing what flow+Babel does. Typescript allows you use newer JS features like Babel but produces much cleaner JavaScript.

If the choice is Typescript or flow without Babel Typescript is the winner by a mile. Without Babel hooked up to flow you can't use any new JS features.
Sabienzia Technologies | Backend Engineer Golang | Berlin | ONSITE | http://sabienzia.com

Sabienzia is a Software as a Service provider who has pioneered the virtualization of call centers.
It offers VOIP Services as well as web based real-time statistics and management.

We are going to develop a new Backend with Go, Protobuf, SQL and Containers.

Please apply to jobs@sabienzia.com
I don't think that number is even close to accurate. SLE almost certainly makes up more than 15% of the market alone. And that's ignoring all of the other enterprise distributions.

I believe that 2015 estimates from the IDC[1] had RHEL at ~60%, SLE at ~20%, Oracle Linux at ~12% and "Other" at ~8%. But I can't access the document at the moment.

[1]: http://www.idc.com/getdoc.jsp?containerId=US41360517
Uber isn’t stealing the property of others. There isn’t a federal law that you must have a taxi medallion.

Owning a taxi medallion of declining value is a consequence of the market.

Having songs you have recorded, spent money marketing on be stolen? That causes financial harm to the artists.

Imagine spending 40 million to make a movie. Now have your work given away for free to anyone that wants it. That is theft.

An unlicensed “taxi” service isn’t harming the rights of innocent people. It isn’t stealing. Who are the actual victims of Uber (besides women employees?) Really nobody. If you own a taxi, nothing is stopping by you from driving with Uber. Uber isn’t stealing your car.
Hi all, we just updated the advert, so please find the new link: https://www.geckoboard.com/careers/#op-201233-ruby-backend-d...
4 Tips to Make Your Computer Work Faster
Ask HN: How do you manage SSH known_hosts?
In our company we are managing a few dozen virtual machines. A lot is automated, but we still need to manually ssh in to machines often.

How do you manage your ~/.ssh/known_hosts file, to make sure you're not connecting to a malicious host? We spin up machines often, and it's not feasible to manually check every new host key. Additionally, DNS entries are often updated to new hosts, which produces nasty "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" messages, which some people also learn to ignore after a while.

Are there any tools to keep a company-wide known_hosts file in sync? Or should we not be using SSH directly to all these machines at all?
I don't think you have the same definition of "REST API" as I.
It's hard not to have some sort of review process if you want to be able to fire someone. If anyone challenges their dismissal for performance reasons, you'll want a record of the "conversations" (1) you had. This is why a lot of review processes include some sort of sign-off by the parties involved.

(1) Scare quotes around "conversations" because I've never seen management approach an underperforming employee and then realize that they had a big part in that. Conversations tend to be more two-way than that.
Not in general, but I'm sure there are some that might.
That's not a jab at your post. Look at Swift and the way they encourage creation of new frameworks and server applications [1].

Then look at the hostile atmosphere in the Go community and tweets of its core team members stating that "http" package is great for everything, no need to use anything else. The framework (or as they prefer to call it toolkit) authors are throwing shit at each other accusing their opponents of creating something not "in the spirit of go" / unconventional, usefulness for the end users is not taken into account. Some others are creating posts about how everybody should stop creating frameworks immediately because that makes them uncomfortable. People hesitating to open-source their code because they are afraid to become a victim of crusade. That's not exactly healthy athmosphere, and it is nourished by core team members.

[1]: https://swift.org/blog/server-api-workgroup/
for every node package, see what node packages are 3 or less levenshtein distance away when it's uploaded, and go through all existing packages. Add an optional flag that will, if you try to install a package that has a package within that edit distance that is an order of magnitude more popular, give you warning and skip that package, an optional flag that errors, and a way to force it for a specific package. In the future, make the first optional flag the default, so people get warnings with instructions to override. Allow white listing of particular packages that may be problematic, and expect a shared white list Then, a year later after repeated warnings of the coming nodepocalypse, make the second optional flag the default, so if you haven't white listed or explicitly forced installing such a package, it will fail.

You will, of course break production for a few people who just didn't listen.

Alternatively, instead of edit distance, allow users to report problematic packages and do a similar thing. Do not provide a explicit award to users who report, so nobody would create fake malware just to report it.

In both cases, either implicitly or explicitly you are using the wisdom of the crowd to figure out the bad packages.
The video which was posted on July 25 reached 21m views
Great... So can I please have something that can do transparent compression? That is my sole reason for using btrfs. (My personal stack is on ZFS with Debian and I'm never going to look back from that, even if I sometimes have speed issues due to SATA instead of SAS system underneath it; ZFS compression and snapshots are incredibly powerful.)
More people won't necessarily help solve any problems though. (Insert obligatory Mythical Man Month mumble mumble, hand-waving, etc. here.) Perhaps additional resources could help.

In general I agree that Mozilla has lost its way with its current head count; successfully funding a company with advertising revenue tends to do that.