skysight-inc/HackerNews huggingface dataset:
I was merely pointing out that startups are good at solving problems that arise from taking products to scale.

The organization I linked to helps families grow food forests, so they both farm and plant trees on a given piece of land.
Aah, Seeing such a good reply, so late. Does HN need notification? Probably not :-)

So, I agree with you a lot. There are no guarantees that Go will remain good for ever. It would be a challenge and need effort on the part of the language developers.

That said, I believe, when a language evolves over a period of 20 years. You get the benefit of hindsight to introduce the good things in a new language. So, Java's garbage collection is a big success. And Go developers incorporated it. Its a tradeoff with extreme (C like) performance, and devs went with convenience and security. Good call, in my opinion.

But the object oriented part of Java, in my opinion, is just a C++ inheritance, as at that point of time (mid 1990s). OO was the silver bullet, to all your sofware spaghetti problems. But as it turns out, it got more complex, if the design/architecture was bad. And good engineers design good enough without the OO.

So Go has taken that approach, which gels with me and lot other developers.

Your comment regarding the error handling part. Yes, it is cumbersome. But surprisingly, it seems to look better than exception handling when you write couple of modules with it. And for some reason, which others have articulated better than I can at this time, your programs are more stable as a result.

So overall what I like about Go, is the minimalist approach of just having the proven things which are good. And avoiding which are grey area or bad.
Land of the frivolous lawsuits, indeed. I wonder how many there would be if the loser paid the defendant's court costs.
Yes and it's quite flexible in doing so https://www.postgresql.org/docs/9.6/static/textsearch-contro...
Most people with the title "CEO" don't make all that much money.

Much strangeness happens just because of mutual funds and the general distorting effect of the public stock markets. We've decoupled the owners from the "runners".

Prior to roughly the period of time in which Micheal Eisner became CEO of Disney, compensation was mainly salary. People complained that it was too much. So more complicated arrangements emerged - options, that sort of thing.

For a modest firm of say, 1000 employees, every 100k to the CEO costs each employee $100 ( assuming all is otherwise zero-sum and perfectly linear). So it's not like there's really much that can be done to improve things for the rank and file.

I was watching the beating given to John G. Stumpf by Congress on CSPAN yesterday. It seems that incentive pay/pay for performance might be on the way out if that is any sort of bellwether.
Why should they set up time restrictions? The pokemon hunters don't care where the game sends them, so instead of putting complex rules into place for something which has functioned for a long time, it would be a lot easier if the game developer just gets asked to exclude this area from the game and then everyone can be equally happy again. Sounds like your approach is wrong to address the problem IMHO.
Yes, but an answer exists.
Coupling is an important concept but I think this concern can be mitigated by following the DRY principle. That is, if you have only one function that knows about the object’s internal structure (“couples” to it, so to speak), it doesn’t really matter where exactly that function is located – in the class itself or in some other place.

Also, your example isn't entirely valid as you mutate the objects' state.
The general case is CEOs are part of the management club, a club that protects itself much like a trade union.

CEOs fail all the time, and they aren't shunned but rewarded with golden parachutes and positions on boards of other companies, biding their time until they can "come off the bench".

The management club is something to be admired and I wish engineers would try to adopt some of its behaviors instead of viewing ourselves as mercenaries.
9 tricks to appear smart in brainstorming meetings
Below 10px radius, all programs take under 0.5 seconds, so you don't even notice the difference.

The picture in an example was made with a radius about 12px. But Photoshop and GIMP allow larger radii, so I think large radii are used sometimes, too.

BTW. it really surprised me, that Adobe Photoshop uses such a simple algorithm, while faster (and slightly more complex) algorithms exist for quite a long time.
Google Rebrands ‘Apps for Work’ to ‘G Suite’
Nothing esoteric, but I advise every person I teach git about to put this in their .bashrc:

alias s='git status'
alias l='git log --graph --oneline --decorate --all --show-signature'
alias d='git diff'
alias dc='git diff --cached'
alias c='git commit -m'
alias ca='git commit -am'
alias a='git add -p'
alias u='git checkout -p'

These probably saved me hours of typing by now. Especially `l` I think should be canon.
And the obvious developer question is:

If developer A can increase the value of your product by 1 million dollars, but developer B can only increase the value of your product by 100k.. why isn't developer A worth 900k (or at least 500k) more than developer B?

The big challenge is measurability. Stock price going up is easy. Profits going up is easy. An app being 1 million dollars better? No idea what that even means.
Thanks, this is my definition too!
I've been waiting for access for a long time. I have no idea when they will accept users other than a few hand picked beta testers.
But in terms of having money, it is. You now have $1MM to do stuff with, whereas before, you didn't. That $1MM can be put to work, or used to buy better tools or hire better employees. That's something you couldn't do when you had no money.
As pointed out elsewhere, we probably don't have enough land for that many trees, unless we figure out how to grow forests in the deserts or on floating islands in the ocean, etc. (technically possible, but not trivial). That misses the important fact, though: there are millions of acres where trees can be planted now. If we run out of land to plant trees on, we can solve that problem at that point.
TFAA?
A friend of mine was an early investor in DeepMind. For like a year and a half, because that's how long it took Google to buy them out for somewhere around $400mm.

At the time, I thought that sounded like an amazing exit (OK, it still sounds like an amazing exit), and wasn't clear how Google could get that value out in a reasonable timeframe.

I was so, so, wrong. The amount of value hidden and public in that acquisition is astounding. Whoever put it together deserves a massive bonus, ideally in Alphabet stock.

MS putting $1bn a year in on AI is a catch-up game. They may do very well at it, but make no mistake -- we are only seeing the public side of the value Google is generating. I don't imagine we'll ever see blogposts about how they're tuning adwords using AI, for instance. But you can bet the same sort of gains they are seeing with translations, audio generation, game playing they are seeing in the ad space.
Sure, that's what share holders do. It's however not EQUITABLE.

To slowly change this over time, we have to work at it, by ensuring fair compensation at companies we start and for our employees.

This can change - it's not a statement of the present - the status quo is pretty bad - but a desire for the future.

To get there, we have to start expressing value for where creation comes from.
That's what the entire discussion and article are about.
I like "git ready":

ready = !git checkout master && git fetch -p && git merge --ff-only

The use case is for when you're done with a particular feature branch and ready to start something new. It puts you back on master and updates it in a safe way.
Why AppLovin was acquired for $1.4B and who's next
The Eleven Dress from Stranger Things
Would you take the CEO job for your current salary?
A small utility to create bootable usb from ISO fast
Google play family plans don't work because Apps is expressly designed for non-family organizations. Ideally, they would have organizational plans, but the parameters for that are different.

Features that aren't relevant to the intended target market may be useful to people making atypical uses, but it's quite likely not commercially sensible to bother with them, and building a robust separate G Suite for Personal Domains offering that takes the right mix of features of the existing consumer and organizational offerings may itself not serve enough of a market to be worth the effort.
I'd suggest rather than look at it as you being overpaid, look at it as everyone else being underpaid - in other words, corporate profit sharing is not what it should be.
Did you guys separate out the R process (or multiple processes?) from the rest of the transaction-processing / other server infrastructure or embed the REngine (which sounds like a bad idea to me; incorrect data serialization can easily crash the whole process)?

What is a stable way to connect (and reconnect!) to R, assuming it was a separate process? I would think that an indirect communication path, such as Server <--> Database <--> R would work best, but I'd love to hear your battle hardened take on it.
Maybe they're waiting for the old ones to recoup their investment or the new ones to get cheaper?
Thankfully someone mentioned a Dyson swarm [1] in the comments :)

[1] https://en.wikipedia.org/wiki/Dyson_sphere#Dyson_swarm
it's silly folks were calling it a "down round IPO"
more than anything, people were over blowing the ratchet protection and misunderstanding the difference between allocated and issued shares.
Am I the only one surprised by the gap between GIMP and Photoshop in calculating the surface blur example?
No way. Getting a prestige gig may be difficult, but you can worst case get "empty suit" gigs in sales or consulting.

I've seen some spectacular SVP+ flameouts, and they all land on their feet. The only exceptions are substance abuse and other problems like that.
I don't know if it's common, but I'm currently employed in such a company. Basically, at the interview I asked for $X / month after benefits[0] and taxes, and what I'm being paid is ($X - benefits - taxes) / month base, + performance bonus equal to the amount that went to the government in my name. I get the bonus by default, but they can suspend it if I perform visibly badly.

[0] - don't know the right English vocabulary for that; in Poland, if your employer pays you X directly, then he actually costs you Y, where Y > X, and the difference is what he pays as a contribution to your social security and health insurance.

EDIT I was misremembering things, so I doublechecked my payslip and fixed the comment to reflect "real reality".
> do people actually find stashing easier than branching?

Branching wouldn't be enough, you'd need to commit your entire working copy to approximate a stash.

I'd say it's generally a bug-prone mistake any time you commit your entire working copy (rather than staging lines/hunks on a one-commit-per-feature/bug basis).

So branching and committing and pushing into a `backupForTomorrow` branch is fine, but you have to be sure to get rid of that commit via something like a mixed reset when you start working on it again.

If that temporary backup commit somehow stays around in the final feature branch, a stash would be much preferred.
PatchMatch is an algorithm to quickly... match similar patches in an image, it is used in a lot of texture synthesis algos. See my answer to fitzwatermellow for the difference between texture synthesis and WFC. So yes, it's related.

Photoshop's implementation of PatchMatch handles constraints perfectly, yes.
No need to install Windows to get R in a database, you can run with PL/R on Postgres (unless you have a particular desire to run it within SQL Server, of course, but doesn't it run on Linux now?).

http://www.joeconway.com/plr/
If I set up a game on your street which attracts 100s of players and you and your neighbors struggle to find a parking on your street and get home then what would you do? Would your solution be to set up complex rules for visitors and parking tickets, or would you just tell the players to go and play somewhere else because they actually don't care if they play on your street or in the park? Sometimes its better so keep it to simple solutions, don't you think so?
this is not software engineering or production. It is batch jobs / exploratory analysis. It requires little or no structure apart from the analysis itself.

also in anything that has not been coded in C directly underneath, Python is 20x faster and C is 500× faster. R is literally the slowest mainstream language today by a long shot. That's a key consideration for production.
I don't know if you're aware, so this is just a friendly suggestion: if you define these as git aliases instead, you won't use your shell's namespace and have it available for other aliases. As git aliases you would run it like `git s` or `git ca`. If you also alias git to g it will be `g ca`. If you do that, don't forget to call `__git_complete g __git_main` in .bashrc for it to auto-complete aliases for `g` and not just `git`. For example, to define `ca`, run this

git config --global alias.ca 'commit -am'
As a diabetic, storing my insulin in others' fridges when on trips is already a real concern - if the insulin isn't refrigerated well enough for long periods of time or is frozen it can become less effective.

So if someone hacked my fridge and froze my insulin each night it'd start to harm my health. I assume other medications will have an even more severe impact for their users when frozen or not properly refrigerated.
If it's C#, you could also make Position be a struct that can't be null. Generally things like Points and Vectors are structs anyway in a lot of cases for performance reasons.
I am surprised too that Mopub has slipped so much. It would be awesome to see a time series of all the SDK install base over time.
Say 99% of players take the appropriate, personally-responsible actions while playing the game.

You'll still have 1% of a very large population being encouraged to take some problematic action.

While I don't know the specifics, it's even possible that it's not a problem if a small group of people check out the dunes now and then, but it becomes a problem with traffic.
A Guide to guarantor loans: Everything you need to know
Yep, and then the follow up is just as difficult...is this dev not delivering value because she's not a good dev, or because those above her aren't giving her opportunities in high value projects?
Storage Drivers in Docker: A Deep Dive
A Guide to Incident Response for Those Who Hate Being Paged
What is involved in being a guarantor for a loan?
Let's call the whole thing off
Yeah, that tracks with reality...
https://en.wikipedia.org/wiki/Tony_Hayward

:P
It's divide and conquer.

Engineers are too impressed by their own intelligence.
C# has some advantages over JS but Xaml styles and templates are so much easier than CSS.

Around 2010 when I was a WPF dev moving back to web I looked so hard for a tool that would do this.

I'm guessing this renders as SVG but CSS (mainly flexbox) and tools have improved so much that it's not needed so much now.

Still going to have a good look into it though.
While it will end up being a little longer, these can all be defined as aliases within git (see https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases). Some users might prefer the aliases there rather than in their shell configuration.
I had the experience of working in healthcare doing data visualization for doctors. The first version of my software I took a very "engineering" approach, a simple, no-frills just-the-facts visualization of the data, defaulting to showing as much data as possible so the well-qualified doctors could decide for themselves what was important. I found very quickly that did not work well at all. Giving a "dumb" scale of graphed data obscured the fact that your blood pressure can vary 20% in a normal conversation, while a change of 10% (F) in your temperature would be generally fatal, that streams of information from redundant sensors make it hard to discern variations in unrelated ones, that a sudden spike in heart rate is likely medically interesting, while a sudden spike in blood pressure is often an artifact of the way that information is collected. In order to effectively present information even to a highly informed audience I needed to contextualize, prune, edit and carefully present that data because by not doing the system was actually creating more confusion and misleading through data overload.

The challenge I'm sure that these climate scientists have is, they see this data not as dry, boring information, but more like health information for the planet. They would like the rate of increase of CO2 to slow and give the planet (which they live on) more time to adapt to the rapid warming which is potentially disastrous. They are trying to properly frame the fact that these are all quite bad signs so we take appropriate actions. A doctor with a patient with a fever of 107º should not present the patient with a report saying "The 2 week moving-average of your temperature is looking normal", or "your temperature is up 9% today", or "while your brain temperature is trending higher, your extremities are cooling so your average temperature is staying even". Those all might be true, but would be medical malpractice.
While that may be true, it doesn't make the article's claim any less disingenuous.
What you don’t know about PPC Ads and need to
There are three-dimensional views of music, e.g. time-frequency-amplitude. See https://en.wikipedia.org/wiki/Spectrogram
Ask HN: Resources for Learning about IoT?
Does anyone have good resources (tutorials, articles, courses, blogs, documentation, github projects) or personal knowledge about IoT best practices, frameworks, or introductory information? Google didn't get me very far and I'm sure many HN readers and contributors know of some good places to start.

I want to keep messing around with this stuff in my home lab, but understand the current state and best practices of IoT devices and communication before I go any farther with my current makeshift mess of a home automation system.
So your issue is with the implementation? I can understand that, I guess. Personally I don't like either dynamic scoping or DI; it had just never occurred to me that someone might prefer one to the other.
"The enemy gate is down."
That's months of continuous use. If you have periods when you don't use it, then you'd have to take the occupation percentage into consideration. It's pretty wasteful not to use a 50K$ server at maximum.
Timekeeping on Mars
Photopea and Gimp do compute the same thing (Surface Blur by definition). However, in Photoshop, the results at the radius >= 50px are slightly different. I have a suspicion, that Photoshop uses an approximation algorithm.

N*10 algorithm has an overhead, it needs a little more time (and memory) per pixel, but it does not depend on the radius. It is an exact algorithm (no approximation).
Am I missing the question? Maybe, maybe not. The simple answer is build your new "server" and install some version linux, like Ubuntu. Set up the accounts and make it so you can login using a private key. Turn off remote login with password so that you can only login with the private key. Install Fail2Ban to block automated hacking attempts---almost the second you expose your server to remote traffic you will start seeing attempts. Configure your internet router so that incoming port 22 traffic is routed to the server (or all ports if you don't care about security). Signup for a free dynamic DNS service for when your IP changes. Now you can login to your home server from anywhere using a your hostname which is tied to your home server external ip address. Its secure because there is no password to brute force and Fail2Ban is killing external attempts. You can secure it further using more research, but this is the basic answer.
usually this is my 1st stop to understand current topics re: ICANN etc. ::

Milton Mueller at Internet Governance Project (1).

his latest blog post may shed some light (2).

1. http://www.internetgovernance.org

2. http://www.internetgovernance.org/2016/09/28/its-over-yestoi...
I'm recently thinking a lot about email because of project[0], and yes, I do agree that it would be great to tunnel SMTP inside HTTP(S). (But yes, I'd go with a SRV entry, not a constant name.)

But no, it's not a great idea to let HTTP replace SMTP. SMTP is a stateful protocol, and while that brings some problems, it also brings some gains. For example, backend servers can keep connections open between them, peers can negotiate resource usage in real time, and the entire extension model is only possible because of connection state.

You'd lose all of those (or replace them with ugly hacks) by tunneling over stateless HTTP. It's a worth trade-off on some situations (like when you are behind a bad proxy), but not always.

[0] sealgram.com
Sure, but isn't that also the mechanism that can lead to the next bank collapsing, and then the next... Like with bubbles, individually beneficial action will result in doom if done by everyone at the same time.
This is such a pernicious justification for CEO compensation.

You don't need to "jump to another CEO role" to continue to be fabulously wealthy.

Failing spectacularly as a CEO often does nothing to impact your employability for future roles.

https://en.wikipedia.org/wiki/Tony_Hayward

Or Carly Fiorina or loads of others we could sit here and review if we were so inclined.

There is, ultimately, no justification for the compensation CEOs receive. They don't deserve it. They haven't earned it. And often their actions are degrading to the company they are hired for, yet they still get paid exorbitant amounts and go on to other positions of responsibility and high compensation.
I guess I'm missing the part where I'm supposed to care that CEOs are in the long, long line of people fleecing dumb investors.
Send a Condom to Space; Swedish Association for Sexuality Education Urges NASA
It's not enough to jail executives. It's also important that all institutional lenders (money market funds etc) that has financed the bank (in addition to all equity holders) take a hit.
This is great. I took accela into Penn Station for 4 years from DC. I always wish they could revitalize that whole area. They can do so much with it. Today it's feels like a 3rd world train station.
It looks like the attack is still growing too. https://twitter.com/olesovhcom/status/781547479879802880

I can't see this ending well.
I don't disagree, because I have a similar feeling. But I recognize that it comes from a bit of a 'No True Scotsman' in regard to computation.

By which I mean that looking up values in a table is actually a part of computation. That's pretty much how anything with a trigonometric function works [we've just replaced books with integrated circuits]. Back in the days of using a slide rule, there was a looking it up in a table element as well, it's just that the table was in a flexible form.

Practically, speaking if the easiest way to calculate the first fifty million primes might be: https://primes.utm.edu/lists/small/millions/

Philosophically, I don't have the same feeling querying for some nth prime at https://primes.utm.edu/nthprime/index.php but it's probably doing all its calculations for mundane things like network packets and none of it sieving natural numbers.
And most people will troubleshoot this problem by restarting their router. And when that doesn't solve the problem, complain about cosmic rays, or humid weather.