skysight-inc/HackerNews huggingface dataset:
In our team, we have our custom implementation of a web app like https://bonus.ly . The idea is, every member would be given a certain points(we call it jems) at the start of the month. He/she can give those points to other members who help them with the reason specified and it will be posted on a slack channel through slackbot.

Using this, everyone can know what other people is working and who is helping who like that. For every month at a team meeting, people who got more points will be appreciated in front of the whole team. The total points is calculated using a formula such that a member who just start giving/receiving more points per jem than other so that new comers will be appreciated more.

It works really well and at performance review, managers will consider this stats. Also the performance review contains two peers (chosen by us), and all kind of managers who we are reporting.
Root cause analysis, in the simplistic form, without a fishbone tree of events and failed controls, means that failure is inevitable. Again and again.

Edit: This document is actually cool: it uses RCA as a term and actually teaches failure analysis!
Become a cryptopreneur – Part 2
On the one hand it is indeed disappointing that nobody would help you with this. On the other hand, there's a more pro-active role you could have played yourself in this as well. "When everybody is responsible, nobody is" - what often helps is specifically asking people, by name, to sit down with you for a bit and help you get through it.

In fact, there are many social group situations in which asking specific people is far more effective than asking questions "to the group".
TouchID means nothing to me. I mean, it would be nice if it worked - I have to disable TouchID on my devices. It simply does not work on me.

Though, I have trouble with fingerprint scanners in general (have to disable them on laptops also).
IIRC, at Google the levels below Senior Engineer require progress toward a higher level as a job requirement. So that even if you're performing well at that level, if you aren't showing progress it gets counted against you in perf increasingly until eventually you are at risk of being pushed out.
I too was also intrigued by the statement "best engineers in the world" and then subsequently reading that Google engineers suffer from the same BS as any average software company.
> - iOS11 airplane mode no longer turns off WiFi

Just tested this and it 100% turns off WiFi on 11.3b3.
Show HN: Codenames AI Using Word Embeddings
Kraken Exchange Closing USD, EUR, and GBP SWIFT Accounts
It lets you generate makefiles in a less verbose way. Like if you have a lot of files in a project or a bunch of targets Makefiles can get a bit unwieldy by themselves.

I've only ever used it for C++, but I don't see why it (or something like it) couldn't be used for other languages too.
Incremental builds. It's a pain in the ass to write this in a good, generic way yourself. If your build tools don't already understand it, then make (and similar tools) makes for a nice addition versus just a script that invokes everything every time.

EDIT: Oh, and parallel execution, but smart parallel execution. Independent tasks can be allowed to run simultaneously. Very useful when you have a lot of IO bound tasks. Like in compilation, or if you set it up to retrieve or transmit data over a network.

It's not too hard to do that in your custom script, but more care is required because until you custom script reaches make level internal complexity you will have to manually track dependencies or make sub-optimal assumptions.
Why is Cybersecurity more difficult today than 2 years ago?
Tarsnap is great. I love supporting it.
My sisters teacher was a Catholic nun who would get mad and slap them if they played sloppily. My teacher was a very nice lady who never raised her voice. My sisters progressed a lot faster
I very much prefer Rake for orchestrating multiple build systems in a web project or dependency installation or just any sort of scripting. It comes with a simplified interface to shelling out that will print out the commands you are calling.

If for some reason the project is ruby allergic, I'll try to use Invoke [0].

Sometimes I feel like people's usage of Make in web projects is akin to someone taking an axe and hand saw out to break down a tree for firewood when there are multiple perfectly functioning chainsaws in the garage.

[0] http://www.pyinvoke.org/
I'll second this. I had to use CMake for the first time recently and was pleasantly surprised by the experience.

This tutorial was making the rounds (on HN and elsewhere) last week, but in case anyone missed it, here's a link: https://github.com/pyk/cmake-tutorial I found it to be a great primer/refresher.
As new apartments are built around Pittsburgh, older apartments get cheaper
If that's honestly your attitude, good luck! Its only a matter of time before your customers realize you aren't adding any value.
As a junior engineer, what the best way to learn about and master the political game? I feel like it all goes way over my head. Does anyone have any recommended reading?
You know you're privileged when you ask questions like that which have obvious answers for the unprivileged...
Speaking as a >6 year veteran (Xoogler) some of this rings true. Still a couple of points:

> No, managers at Google can’t promote their direct reports. They don’t even get a vote.

This isn't quite true. It's true that the promo committee doesn't include your manager and it's that committee's vote that determines your promotion BUT your manager does get to say whether or not they support your promotion.

Anecdotally, committees expect to see manager support so if a potential promotee has it, it doesn't mean a lot unless there is a lot of specific information that the manager can provide to support the promotion (ideally peer feedback should do this anyway). It tends to be an issue if your manager doesn't support your promotion however. And this happens. It also happens that people get promoted without manager support.

Personally I never understood how this situation arose. I operate under the principle that there should never be "negative surprise". So if your manager doesn't support your promotion (which, hopefully, is solely because it's the manager's informed belief that it won't pass committee) then the report should already know this before they decide to submit for promotion. If they don't, that's a giant manager fail.

If the report goes up anyway, if I were a manager there's absolutely nothing to be gained from not supporting the promotion.

Moving on to the other points:

> Metrics or it didn’t happen

There's a lot of truth to it but not in the way the guy intends I think. He goes on to say that there were no metrics for what he was doing.

Well that's the first problem. You should create them. And it sounds like this guy was looking to a T4 to T5 promotion. There's a certain amount of independence and proactiveness required for T5+ so not creating the metrics to measure his successes by is an issue.

The manager again bears some responsibility for this. One of the primary jobs of a SWE manager (IMHO) is coaching their reports for situations like this and building their careers.

A better way to say this is that impact matters. Working on a bunch of small, unrelated things is not impact. Promotion isn't a matter of doing a lot of work or being helpfully necessarily. By T5+ it's an issue of having impact across your project and to your wider team.

Also, it's worth noting that often people do have to go up for the same promo twice. The natural instinct for committees is not to promote and they'll give you feedback as to why. So then 6 months down the track you submit an updated packet that includes all the ways you've addressed the previous committee's feedback. That's really common.

As for the holiday gift, yeah I was there for that. All I was say is that it was bad optics, particularly in light of say, how much money was handed out to Levandowski. The argument was that it was too expensive to adminster across so many different countries. This may be true but it feels like penny-pinching and cost-cutting. And as they say, as soon as they take away the free drinks it's time to pack your bags. The issue isn't the free drinks, it's what it signals.

Project cancellation! Been there twice. It's highly demotivating.
Did they retract the tweet? The link now 404s.
My iRobot Scooba does that--poorly, but it does that. The Roomba handles the initial hard floor cleaning, and also the carpets.

I don't have a robot yet to clean the toilets, but I hear they exist in Japan, and my parents have one on their most heavily used commode.

Thank goodness California phased out most of its public telephones before sending all their telephone sanitizers on the 'B' Ark to Texas.

Whether there is a problem in pushing out all the low-skilled labor depends largely on whether all the work that those people do is automated yet. My concern is that jobs that require some on-site human judgment, but not a lot of skill, will start to go unfilled before robots are ready to step in.
Ability to work independently is a double-edge sword.

I’ve been in situations where independence was communicated to be desired. Yet CTO was a micro-manager and very nit picky during code reviews. This kind of approach backfired and I ended up asking a lot of questions and consulting them on every decision to make sure I don’t waste time writing things that were not up to his unwritten/uncommunicated standard.
Hell? I'm out of the loop a bit for sure, but in two hours when we do our sprint planning.. their backdrop is a tiny windowless office while mine overlooks the pacific ocean.
This is great - you should really put your name and details on there. You deserve the recognition!
Is it worth moving to this from 1Password? I mean I don't have any problems at all tho I use an old version (6 on Mac, 4 on Win), the permanent license version not this new subscription.

I was thinking to use this with Dropbox, Chrome, and iOS client (MiniKeePass?)
Most pages should work by default because more and more start to use Schema.org to markup their pages. In case a website is not supported or the needed data is missing it is possible to add support. The easiest by simply writing us and we add it ourself. The alternative is to use our point and click data-selector tool which is similar to how kimonolabs worked. It can be accessed by logging into link.fish and then select in the header menu "Plugins >> Data Selector".
I laughed for full three minutes. Thanks for this stranger.
I'm currently going greyscale and have not noticed many differences in my habits. In the past week I've been using YouTube less but my YouTube habits have always ebbed and flowed. I'm reading the news apps on my phone slightly more.. greyscale makes articles have a dead tree newspaper feel with the black and white photos. Google maps is noticeably more difficult to use and so is Google calendar, which categorizes events by color.
Show HN: Domain Wheel – Domain and company name generator
Most genomicists don't care how the system works under the hood. They've already abstracted things to the level of base pairs and working with statistics. This

Biophysicists are the people who care about the underlying physical mechanisms of those systems.

The thing to understand is Barb was cross-trained- she worked in a deep statistics group (Jordan) but was embedded in a bio lab, and picked up all the necessary knowledge to understand the biological context. Most CS and stats people don't do that- they move up the chain to the convenient level of abstraction, and ignore the details below.
Ha! Hi Dave! I've been watching your little business flourish via your LinkedIn page for a couple years now and it's been a joy to observe it blossoming. Keep up the good work and I bid you continued luck in the future!
They just need to use Java9 modules so they can use jlink to produce native binaries. No need to use another language.
IMO these two are mutually exclusive:

> successful profitable business

> provides the majority of the owner's income

Building a business takes a lot of time & dedication. It's going to be very challenging to reach long-term stability and profitability if you go into it with your sights so low that you think "this will be successful and I can coast if it makes $100k per year."

Play to win.
Yeah man, drinking coffee is totally the same as doing drugs. If only the rest of the society could see that.
By default, but you can easily accidentally change that behavior:

https://www.macobserver.com/tips/quick-tip/airplane-mode-ios...
CMake is mostly dedicated to C/C++ projects, but also has built-in support for assembly, Fortran, and Java. CMake has templates for adding a new language as well. The benefits are: cross-platform "shell" commands (you can copy files without using an explicit cp), standard lookup for programs, and easy target generation from a collection of files. Most languages are pretty similar to C/C++ when it comes to the build cycle. Portability (i.e. testing for existence of headers) is less of a concern for something like Javascript, but everything else still applies.
On the other hand, make invokes well known shell commands; I already know what they do, when I see them used.

If you are invoking your functions (or functions imported from random library), I have to check them for what they do.
I still use a passcode... I think true authentication should come from my conscious awareness, rather than the mere presence of some biological characteristics.

Haven't actually found any AR use cases that has been compelling, didn't get into the Pokemon Go craze and in the mapping world I think I would trade any AR capability for compass functionality that could actually tell which way my phone was oriented without endless calibration and movement.
I see. I guess it was just me misinterpreting "perfect". To me it's obviously not perfect to play like a robot.
Buy a YeeLight, it has a local API. Mine can't even get to the internet.
I'd add another component:

The people usually tasked with figuring these things out are new to the team. There can be all kinds of politics and interpersonal baggage with helping the new person with old configuration/ compilation/ deployment stuff.

Often, it'll take one of the legacy leads to step in and clean things up. By then, everyone's annoyed at the new person, and the failure of this effort will get saddled on their back for some time more.

I had this exact issue at a recent gig, and the application architect spent months poking at jenkins to get a clean build. Once he quit in frustration, one of the legacy leads re-engineered the whole thing, in a different language, in a few days.

Legacy lead was one of those "untouchables" in the eyes of the CEO, so there was no influencing him to help earlier, and his reticence cost us a good application architect.

To my mind, this is often a sign of a poisoned, political company culture. The work can be done, but there are non-technical reasons why progress can't be made, even by earnest effort.
cmake is good but it is quite heavily geared towards C/C++ development. I would love to have some modern makefile with a bit nicer syntax. Fitting into 80 columns is no longer a must.
Bringing search to Angular
I completely agree.

My point is opportunity cost. Unless you have a very clear idea of what you want to do/build--which many people do--you're better off with a day job.

I see a lot of people essentially rage-quitting (let's be serious, that's what happened here) and then wasting years of their life working bottom-of-the-barrel contracting/crappy startup jobs because they "don't like big companies". I made this mistake and it's cost me enormously in money, time, and career development.
The 48 Laws of Power by Robert Greene is an absolute must, regardless of the position.
This looks nice! How does your product compare with Patreon? (edit:) The difference I notice about it is that this looks a lot less demanding than Patreon. A lot more laissez faire if you will.

Oh and, https://buymeacoff.ee/nettem :)
And Google Sheets would do well to improve the add-on development experience. It's absolutely awful and the documentation rarely tells you what you actually need to know
Maybe I'm in the minority, but I've always found its syntax to be quite nice (though admittedly a departure from most modern languages). Then again, I find using JSON or not-quite-ruby to configure a build incredibly bizarre and confusing, so I guess I'm just set in my ways...

In all seriousness, what's wrong with it? Significant tabs aren't great, but I feel like that's a relatively minor wart. The simple things are _very_ simple and straightforward. The more complex things are more complex, but usually still manageable...

I've seen plenty of unmanageable Makefiles, but I haven't seen another system that would make them inherently cleaner. (I love CMake, but it's a beast, and even harder to debug than make. If it weren't for its nice cross-platform capabilities, I'm not sure it would see much use. It's also too specialized for a generic build tool. Then again, I definitely prefer it to raw Makefiles for a large C++ project.)
Its also excellent, one of the best FP books I've read, and I've read quite a few. It might be the best self-study programming book I've seen as well, all the answers are included at the end of exercises at the end of each chapter, it goes from fairly simple to a theorem prover by the end. Spectacular book. I look forward to seeing how this pdf compares.
How is abusive content handled on this platform?
Built in camera and video capture has improved an incredible amount. I think the value this provides to people with modern "phones" is pretty significant.
It is, to some extent, a direct function of scale. The larger you get, the more you need to rely on systems instead of individuals - because it's easier for bad apples to hide in the noise. (How's that for a horribly confusing metaphor? ;)
False headline. It does depend on neodymium, on the "fraction" it uses is a large fraction, if I remember another article correctly. Of course, "somewhat more efficient in the use of rare-earth elements" isn't nearly as good clickbait.
You should look up http://doc.cat-v.org/plan_9/4th_edition/papers/mk

https://9fans.github.io/plan9port/

http://www.vitanuova.com/inferno/papers/mk.html
Good point - cross platform issues are a concern. I've noticed in the past that OS X machines tend to run older versions of Make (unless the owner has installed a newer version with Homebrew). It is a good idea to pay attention to the Make features that you use, understand which features were added in recent versions, and be aware of which features are specific to GNU Make. In my projects I recommend that users make sure that they are in fact using GNU Make.

Some systems might not support the `-p` flag in `mkdir -p`, or the `-rf` flags in `rm -rf`. There are scripts distributed on NPM called `mkdirp` and `rimraf` to work around such issues.
Yes, people who have been around the block come to the same realization that the author does re: filing bugs. Any type of written communication or record that is not either undeniably necessary or unambiguously favorable must be avoided.

I've had the experience several times where extensive, detailed emails would always meet the same reply: "Thanks. Let's talk about it in the morning." These people are wise to the game, and they rely heavily on the imperfect nature of human memory; memorialization in the written record must be approached very carefully.

The email chain that shows Employee A to be a hero equally shows Employee B as a victim in constant need of assistance, obstructing other work, taking valuable time from others. As such, "Bs" will avoid asking in a recorded form, avoid giving credit to helpers when writing about their work, and so forth. Even if they mean well and earnestly want to credit the many people who've helped, it's too easy for a malevolent actor to turn it against them, so after a few raw experiences, they learn to avoid it -- just like what happens in the article.

The only real answer to these questions is to have an informed, rigorous, and fair-minded chain of command that has experience and cares deeply for the company's long-term well-being, which is, needless to say, quite rare. It is also worth noting that such noble persons are likely hurting themselves by acting this way and making enemies for themselves, as people who truly didn't deserve promotions, etc., whine and search for flimsy excuses.
Thanks for sharing that. That describes feelings I had working there. I think the idea of rules and meta-rules is a good way of explaining it.
I do freelance development work and sell video courses focused on building and deploying web apps.

I started by thinking to myself "what would happen if I tried to make training videos?", slept on it and dove right into it the next day without knowing anything about creating videos.

Hosting fees and a hell of a lot of time are my only expenses.
You should check out RedisLabs and read about their story. I'm not affiliated, but I always thought it was amazing how successful they are given that AWS has redis ElastiCache.
I think that for those that go for the visual experience this may detract them. But I go for the text experience, so..
OP's claim is that black holes infinite amount of time to form, because matter would take an infinite amount of time to fall into it.

Personally, as a layman on the subject of black holes, what I understand is that mass does take infinite amount of time to fall into an event horizon. But I don't know about the formation process of how/when that event horizon is formed.

Perhaps you can help me, and him, understand why his claim is false--that it would happen in finite time?
Google has one of the worst monocultures I've ever seen in my life with a heavy emphasis on commoditization. It's a giant machine treating software engineers as nothing more than easily replaceable cogs.

The perks and "easygoing" atmosphere play into this facade and are designed to delay the process of discovery. If you are after [significant] material benefits, by all means go work for Google but be prepared to be treated like a commodity. Ideally you will go through the same process of discovery the author did, faster, and will be able to adapt to extract the most out of the situation.

If you think programming is an art and despise corporate processes that constantly devalue it, then
Google is one of the worst places you could be.
Wow if you consider Makefiles easy to read...
Google is changing the promotion process such that managers have much more power (for all promotions up to level 5 == senior swe).

Previously it used to be, as Michael says, very much in the hands of the committee members who never heard about you or even your team.

Now the committee will be composed of your manager and some other two managers from a related team. The committee will not see your own promotion rationale or your own description of your projects and achievements, rather it will be the job of your manager to present these points and advocate on your behalf. The committee (except for your manager) will also see only limited peer feedback compared to before -- no free form text, only multiple choice questions/answers.

If all three managers agree that you meet the bar, you get promoted.
At my job, we use HeyTaco, a Slack bot. Every day you can give up to five tacos out by @mentioning somebody with a :taco: emoticon. If you answer a question or help somebody out, they will probably give you some tacos. The app keeps track of who gets the most tacos with leaderboards and the like. This has instilled a culture of helping others out on the team, by gamifying it and making it visible.
It’s called “swing”, right?
I suggest using Bitwarden (open source) instead. See my article: https://greycoder.com/bitwarden-excellent-free-password-mana...
Do you also disapprove of the word "assembler"? (Honest question.)