skysight-inc/HackerNews huggingface dataset:
"Only assholes get patents"... Everyone would get and enforce patents if it weren't so hard and expensive to obtain them... I think saying don't get software patents is terrible advice...

Of course, don't go and patent a mediocre interaction or technique, but definitely, pursue a patent if you have worked hard on researching and developing something that is key to your business and that could be used by a better established and wealthier competitor to take a market advantage.
> Presumably it costs them money to develop these new features. Why do you feel like you should have access to new features if you are not a subscriber?

Nobody said anything about not being willing to pay money for (new) software/features.

The problem is the subscription model. On of the problems with subscriptions is you loose track of what (new features) you are paying for.
Especially when you don't have a lot of money, this is problematic.
When making a 1 time purchase, it's very clear what you are paying for.
(and cloud services are free already with iCloud sync/Google drive/etc. so the 1password cloud is superfluous, feels like just another excuse to sell a subscription model.)

I mean, are you aware that you are paying $2,99 * 12 * 3 = $107,64 for 3 years of 1Password usage? And that's just 1 of the many app subscriptions...
Ask HN: Do put the name of your current employer on your resume when applying?
When applying for new jobs, do you leave out the name of your current employer? Do you think it's a good idea? I thought about replacing the name with something generic, like "Embedded Systems Company".

My fear is that if I'm mass applying to other jobs, especially to startups with small teams that may not have a formal HR practice in place, a tiny set of them may call my current place for whatever reason without my knowledge. I would rather not tip off my current employer that I'm thinking of leaving; my place is a bit trigger-happy at times.

I do have colleagues in the company who will vouch for me, so references are not a problem, but there's no tactful way to put that on a resume in place of the company's name.
They caught the BTK killer because law enforcement told him he would be anonymous if he simply sent them a word doc.
https://en.wikipedia.org/wiki/Dennis_Rader
And by his logic, Apple is filled with assholes. Who go so far as to sue others over rounded rectangles.
Leave a small town downtown at 1 or 2 am (whatever is around the bars' closing time) with a light out -- even just a license plate light?

You may get pulled over. If you're cool about it and appear sober, you may just get a warning.

If things look more askance, you'll be put through sobriety tests.
I’ll note that I had an eye-opening moment regarding the flavor of different beans at the Tcho chocolate tour on the Embarcadero.

At the end of the tour they do a tasting of bars made from single-origin beans. With the only additives being varying amounts of milk and sugar, one bar tasted bright and citrusy, another was earthy and nutty, and another was rich and (for lack of a better term) “chocolatey”.

It makes total sense in retrospect, but I’d never considered how much the flavor of beans by themselves can make such a difference.
Sounds like you have a business idea.

Virtue signaling in marketing and as a business is a hot trend right now.
Conventions exist in every language. `car', `cons', and `cdr' are also part of certain standards (e.g. RnRS). And, honestly, they compose a bit better than `first', and `rest' for combinations like `caddr' and `caaddr'. I suspect that you're going to be even more unhappy with those constructions.

The same can be said about older languages like C, which also have standardized notations.

Why fix what isn't broken?
Thanks for the clarification. I believe UE4 is still a good example of how the PR-bias towards anything 'open-source'. All it took was a few headlines with "Unreal" and "open-source" and I naturally grouped it with the likes of Blender and Godot.
It must be of some interest to the entrepreneurial-minded folks on HN. An East Coast company that started in 2012 [0] gets a $8B buyout -- and unless I'm missing something, it doesn't even have a Wikipedia page. Reminds me of stories about all the tech startups started by non-teenagers/non-dropouts whose big exits (some near unicorn-level) don't get much attention because their origin stories or their business plan don't sound as sexy as the archetypical Silicon Valley startup myth.

[0] https://www.bloomberg.com/research/stocks/private/snapshot.a...
Even the unibody ones are a mess, if you can get under the body. That is half the point of having the body, after all.

Not to say we shouldn't shake off some baggage. Just at some point having things "tidy" is purely an indulgence.
My bad. It is at the end of that.
I think he meant it in the context of "Defending your app from copies and clones" (aka "to defend you intellectual property"). If you hold patents just to make them available for ever and free to anyone but patent trolls, that might be a different game.
I agree. I'm thinking about the commercial software I've bought - most of it doesn't include perpetual upgrades (I'm a 1Password license holder who bought into the subscription when it became available - it's easily worth the $7 I pay for my family)
How Tesla could save DHL tens of thousands of dollar per year
IT staff regularly have to lock people out of accounts/computers remotely after workers are fired or monitor everyone's internet access so they either get used to just doing what is told or don't work.
Also, petty thieves just don't care about your book of passwords. Just like they don't care about seeing if your hard drive is unencrypted when they steal your laptop - they just pawn it off.

Of course, the ideal for security is that the best options are so convenient that you might as well do them. But there sure is a lot of circlejerking that happens when someone is exposed as "doing it wrong."
Unless the hackers simply modify the service itself, and log every password a user inputs to their server.

And tada, they got your password.
It holds true also for high functioning autists. Inability to control emotions or evwn recognize them a.k.a. angry outbursts over small inconvenience/not getting your way/etc is one of symptoms for example.
Or he had some really expensive meds and bad insurance. That's pretty unlikely though.
Market cap doesn't go up based on people buying shares. You are just trading ownership.

In theory, the market cap of the company is the current value of all future returns.
Hmm, maybe I'm missing something, but I lost interest after seeing that pretty much all the 'ad hoc' solutions listed (similar non-monad based solutions is the idea I think) were nearly identical to the monadic solutions, except some syntactic differences. As someone who doesn't care that much about little syntax nuances, the motivation to look further here escapes me.
Wow you’re aggressive.

Using something like Hashi Vault, Gluu, or Shiro does not overly complicate things. They’re stable, trusted solutions.

It can also greatly simplify things. In the common scenario of having a web app for customers and a web app for admins, instead of them each having their own authentication baked in, you can choose an open source solution and deploy it twice, once for each service.

I know how salt works. Don't belittle me.

If someone gets into your web servers they’ve pretty much got carte blanche at your database the web server has access to. They also now have your code, which in a lot of cases is probably plainly readable. So they can see your salt, see how you salt and see the hashing algorithm you've chosen.

I’m saying don’t store the salt in your apps config right along with the credentials to access all of your login identifiers and hashed passwords.

You gave them a piece of the puzzle. If someone wants to grind through and crack all the salted/hashed passwords, I'd prefer them not to have the salt to help in that endeavor.
Nice ! But without GC I guess it’s just a nice hack and will have a hard time being actually useful
Delegation for Project Managers
Do you feel stressed and overloaded? If so, then you may need to brush up your delegation skills!
If you work entirely on your own, there's a limited amount that you can do, however hard you work; and if you're good at your job, people will want much more from you.
This can lead to a real sense of pressure and work overload, leaving you stressed, unhappy, and with the feeling you're letting people down.
On the positive side, however, you're being given a tremendous opportunity if you can find a way around this limitation.
One of the best ways to overcome this is to learn how to delegate your work to other people. If you do this well, you can quickly build a strong and successful team, able to meet the demands that others place.
Why People Don't Delegate
Quite simply, people don't delegate because it takes a lot of up-front effort.
Which is easier: designing and writing content that promotes a new service you helped spearhead, or having other members of your team do it?
It would be relatively simple and straightforward for you to sit down and write it. The question is, "Would it be a good use of your time?"
While on the surface it's easier to do it yourself than explain the strategy behind it to someone else, there are two key reasons it's better to delegate the task to someone else:
•	First, your skills are better used further developing strategy, and coming up with other new ideas. By doing the work yourself, you're failing to make the best use of your time.
•	Second, by meaningfully involving other people in the project, you develop those people's skills and abilities. This means the next time a similar project comes along, you can delegate the task with a higher degree of confidence that it will be done well, with much less involvement from you.
Delegation allows you to make the best use of your time and skills, and helps other people in the team grow and develop to reach their full potential in the organization.
That is directly contradicted by Cockpit's own doco, which explicitly states that Cockpit uses the systemd APIs and that "use of alternate system APIs are not currently implemented".

* http://cockpit-project.org/guide/latest/feature-systemd.html

It should of course be obvious that Cockpit does explicitly deal with systemd. Desktop Bus is a transport layer, and the important thing about it is what DBus servers are on the other side of the broker are being talked to. In the case of Cockpit they are things like systemd's own idiosyncratic API for process #1 ...

* https://github.com/cockpit-project/cockpit/blob/0dd4ee7bac14...

... systemd's hostnamed server ...

* https://github.com/cockpit-project/cockpit/blob/0dd4ee7bac14...

* https://www.freedesktop.org/wiki/Software/systemd/hostnamed/

... and systemd's timedated server.

* https://github.com/cockpit-project/cockpit/blob/dbd7f3a8487a...

* https://www.freedesktop.org/wiki/Software/systemd/timedated/

Cockpit also hardwires use of systemd's journalctl program.

* http://cockpit-project.org/guide/latest/feature-journal.html

* https://github.com/cockpit-project/cockpit/blob/0dd4ee7bac14...
How to JavaScript in 2018
Words for “yes” in Romance languages
I'm inclined to believe many of these reports are biased and still pushing agendas, even if it is out of peoples on lack of understanding of how a blockchain solution would actually work. Largely, their inability to think creatively about technical solutions.
I like how they threw “makers” (or “pro makers”, whatever that means, on the actual page) into the title. Uhhh... Yeah I’m going to spend $50 and then probably at least another $50-$100 for the breakout board, which I’ll need as a (pro|) maker because they use high-density FMC connectors on the actual module itself... At this price point and level of integration difficulty why not just use a (much more standard and better-documented) Pi Compute Module?
> my co-founder has started to complain that he has to take care of all the office stuff, human relations, etc. on his own.

Try to forge a path together. Managing people/admin problems are common early-stage growing pains. More and more companies work in distributed teams. Find a way to shift the work responsibilities.
Windows 8 and plus
The surface problem of LISP are the parenthesis. The deeper problem is that its a very potent NIH enabler: most of us are not really that talented or have the time to properly invent things; those that are tend to not quite like other people's things (and are good at spotting flaws in them) so they work on their own "better" things (e.g. see arc).
To be clear, I had read the whole post, I was just being terse since the emphasis seemed to be so heavily on an apples to bananas comparison (I believe 100% of the results cited in the prose, many in bold, are with mismatched precision and batch size), with minimal articulation of the many axes of nuance here. Precision isn't defined at all in the LSTM case, and could easily be the cause of the failure of the TPU run to converge where the GPU runs do. To a non-expert audience I think the end result is confusing and misleading.

Also, while I certainly agree that the performance/dollar comparison is highly relevant to customers at a given instant, that may only tell us that Google is subsidizing this hardware now that they've deployed it, and/or that, lacking serious competition, NVIDIA has been building crazy margins into their P100/V100 prices. In understanding fundamental technological tradeoffs, and even the limits of what the pricing in a more competitive market could be, it is relevant to compare performance per unit of hardware resources (mm^2, die/package, watt, GB of HBM, etc.)

In short, these comparisons are hard, and there is no one which tells a complete story. I pushed back because, while the post includes some nuance, it brushes a great deal under the rug and focuses primarily on problematic comparison

(Further disclosure: I'm at least the third person in this sub-thread with some Google Brain/Cloud affiliation. I am speaking in my independent academic voice. I also think TPUs are great, having them publicly available now is great, and competition and diversity of architectural approach in accelerators is great. I appreciate the effort of the authors, but think the subtlety of these comparisons requires serious care.)
Too bad Manafort and Gates didn't have an account on my unlimited Cloud Platform. They could've created an account, uploaded the .pdf, converted it to .doc, edited it online, and then converted it back to .pdf without being tracked. The only evidence would have been user-specific log files showing which user changed which filenames and when, but all those content changes would have been lost provided they delete the originals.

Hindsight is always 20/20 I guess.
I think its the other way around: When you are a millionaire you probably don't care much about patents, because you can afford to pay for the license.
A single person in Seattle can comfortably live(not own a home, mind you) on 85k assuming they don't have any massive debt obligations- not to mention we're talking about Seattle in 2004.
I think the plan is sensible, but not that realistic in terms of being able to reach a critical mass. If I was in your position I would integrate much more closely with external services (github/twitter/etc) to hopefully make it feasible to have stuff like recommendations work effectively with a much smaller user base.
> The Alex Jones Channel, Infowar's biggest YouTube account, received one strike for that video, a source with knowledge of the account told CNN. YouTube's community guidelines say if an account receives three strikes in three months, the account is terminated.

The title is misleading, as is they have to receive a lot of strikes, like 10 or 100, and they only have to receive 2 more.
Accents are a hard problem in voice recognition. If your accent is weirdly unique (like mine) there's already a deviation from the baseline data used to train those models.

That being said, I feel both G.Assistant, and Alexa both interpret what I'm saying most of the times.
In contrast, Siri rarely understands me well. When I set up reminders, 95% of the times Siri fails to comprehend me correctly.

I don't know what they are doing at Apple, but you would think they would have nailed this already (with the millions of Siri capable devices they have sold already).
> Defending your __________ from copies and clones

Fill in the blank, and the same lessons apply.

Any idea, project, business, app, website, article, podcast, TV show, media production, procedure, product, art, creation, etc are frequently copied and cloned. And he's right, ultimately nobody cares.

Sometimes a copy or clone is better than an original. Sometimes a copy or clone is much worse, but ends up successful because of positioning, luck, marketing, or savvy.

Perhaps it's better to think of the risk of being copied or cloned as part of the risk of business and creation. It just comes with the territory.
How many of those tax laws were on the level of '3 felonies a day'? The US tax laws and their penalties can be pretty horrible, and you could possibly ruin a whole bunch of older middle class people who use something equivalent to turbotax badly.
"Being able to think logically and systematically" is not a symptom of ASD.

Look: simply being smart is not in and of itself a symptom of ASD. There are a number of symptoms associated with the spectrum that actually have very little to do with intellectual ability. It's inappropriate and factually wrong to make the statement that logical and systematic thinking is symptomatic of ASD.
Can Humans and Computers Mate and Have Babies?
Interestingly, based on that same dataset, high cholesterol decreased from 20% in 1988 to 11% in 2014. Any ideas?

https://www.cdc.gov/nchs/data/hus/hus16.pdf#053
Document incompatibility is an entire industry. If you could convert Office documents easily, you wouldn't need so many office licenses.
Or you could help work on an open source technical solution so that this ridiculous corruptible process is fixed.
My personal feeling is that signup of a new user is too critical of a function to depend upon an external service. I would very much prefer a client-side library as others have stated.

This said, I can see a ton of potential for a plug & play solution, for example (but not limited to) a signup form for wordpress, a react input password component with a strength bar, etc.

If you create "a product that people love", I don't think it does really matter whether you verify on the client side, or securely via a remote service. You may explain pros and cons, and let the admin decide.

But I'd focus on the final solution, rather than just the service itself.
You (and the other repliers) seem to be confused. It's not that I don't understand monads, it's that I don't value them. It seems obvious to me that they serve mostly to harm code quality.
Disclosure: I work on Google Cloud.

Oh! You should definitely say that. It's semi-reasonable then to choose the batch size that is optimal for the part. It'd be good to make sure this isn't why your LSTM didn't converge though...
Like coffee, a lot of the flavor and smell are extremely volatile chemicals. (Not in the explosive sense lol.) They just evaporate into thin air in a small amount of time, which is one of the reasons they have such a strong smell. If you keep ground coffee sitting around for a few days, it's going to taste noticeably different for the same reason.
The press is only giving people what they want
Agreed and here's a word to the wise. For whatever reason, tools for other coders always make for the most impressive side projects, even if no one ever uses them.
I did a small investment in a food oriented start-up and I really hope they will succeed in their dream of feeding people healthy stuff. Many companies claim to want to 'change the world for the better' when actually they are just looking to make bank. These guys are driven because of their ideals, they're super nice and have a good idea + track record. Time will tell if it works out.
Statins
I identified that transition cost to exercise (for me, personally) is a barrier to exercise. Scheduling it, driving to somewhere, etc. all eat time and motivation.

I try to work around this instead by just running near where I live. After I get home, I change clothes and jump out the house for 30-45min of just running. Transition cost is just changing clothes and I'm active for the full time. This way it feels much more productive.
It's not that hard. This isn't something invented by Toth but is rather just a standard part of chocolate tasting.

You don't need a $300 or even $10 chocolate bar to benefit from this technique - it brings out the flavors of a $3 Trader Joe's 85% cacao Colombian bar just as nicely.
He was just distilling the real world implications of the 3 paths of IP in a succinct way. I agree with him on all points, and he is accurate in his statements. He's inviting you down from a pedestal you may have put you and your software on: if you create something great, expect to be copied, and expect it to be considered a standard feature when someone else does it. Because really, thats how "features" are born. You can trademark your name for it, which will make it harder to advertise the feature as the same.

I think this piece was intended as an eye opener, and a blunt one, because the world isn't going to soften its blows on you.
No, wouldn’t surprise me if people did. Clearly not what I was talking about. I’ve watched a car attempt to pass on the shoulder because two jackhats were driving side-by-side on a two lane highway going 10 under they lost control and nearly hit me. I was pissed at the driver attempting the stupid maneuver and the one blocking the left lane for miles on end.
Therein lies the problem. A given piece of code looks the same for any possible monad, but it only provides useful functionality for a specific monad. The reader of the code is left wondering _for what benefit_ the code was written, and may waste some time instantiating it over the wrong concrete monad[s], until it finally clicks.

Secondarily, I wish “monads are cool” tutorials would pay some attention on how the do syntax interacts with the rest of the language, and especially with conditionals. For example, assuming a function that computes a value and also collects some side effects, how does one turn the pure variant into a nomadic variant? This is trivial with a mutable collection, but a laborious exercise in monad world.
When you fill in a username/password combo and it pops up offering to save it as a login for you, it just doesn't know that there's a username field.

When you revisit that entry in the future. Like possibly the far future when your one-year-long session finally expires, you'll find out you only have a password.

Pretty bad UX. The popup that has [Cancel] [Save] should just show you the username and blotted out password for you to confirm.

I have a few entries where I was so paranoid that I said fuck it and copied my password right into the name of the website entry. So I'm wondering if there's a case where it only saves the username and not the password because it doesn't detect it? I just haven't registered for a website in a long time so I only remember the one case.

If you haven't encountered it, you're just lucky or, more likely, haven't yet noticed. ;)
Author here.

Thanks for your feedback. As I noted above, we will report further results with larger batch sizes (and smaller ones for the TPU). The LSTM not converging is one of the experiences we wanted to share. We are working on solving this issue and will update the post accordingly. Our goal is really a fair and valuable comparison, which is not easy, so we value all of the feedback.