Would it be fair to say that the biggest challenge with the buy button is the lack of last mile fulfillment (like shipping, returns etc) from Google/FB/Pinterest. Amazon on the other does a job at this
The last mile is still being handled by retailers.
The buy button primarily fixes the UX friction of having to leave the experience, go through a horrible mobile web checkout flow, enter your information again, etc...
Imagine those replaced with a streamlined flow (ala amazon single click buy buttons)
I agree completely. When I shop online, I like going with amazon since I know from experience their return process is so painless if something goes bad.
I can't imagine shopping for physical goods from Google. From what I hear, their customer service is pretty bad. I think overall that this is a risky proposition for these companies, in that if they mess something up they will have a lot of bad publicity.
In Google's defense their support for people who are paying money for a service tends to be better - both AdWords and Google Apps have had pretty solid support teams when I've needed them.
net.ipv4.tcp_tw_recycle causes problems with NAT-ed clients.
tcp_tw_recycle (Boolean; default: disabled; since Linux 2.4)
Enable fast recycling of TIME_WAIT sockets. Enabling this option is not recommended since this causes problems when working with NAT (Network Address Translation).
net.ipv4.tcp_tw_reuse seems fine to use, but literature about its real effects is sparse.
Zenefits and zenpayroll have easy to spot ads running on google right now.
Most startup's spend an enormous amount on marketing to get any traction. I'm sure there is more examples like Slack that did not use much marketing, but they are very rare.
If you build a startup and hope to iterate your way into being viral, this is bad planning in my opinion, no matter how awesome what your building is. Unfortunately, one that I had to learn the hard way.
Developers have a tendency to get overly excited about speed. Fast database, fast search, fast framework, etc. The truth of the matter is that speed should be evaluated within a spectrum. As long as your application latency is within a spectrum, you should be just fine
Thank you.. for me React/Flux and the like just felt better than Angular 1.x while being fast enough. The tooling and support for something like Polymer just doesn't fit as well.
React with a flux-like flow is simply easier to reason with... When I've used Angular, I always hit points of frustration or weirdness that simply didn't make sense... the more advanced bits of React are less surprising in my mind. It's a shift in thinking about larger component based applications.
It's also worth noting that Angular was started some time ago in 2009 and likely in development farther back than that... this is before CommonJS or AMD were widespread, and jQuery was a rising star. This is very much reflected in Angular 1.x.
React is a different approach with a slightly more functional mindset (though I'm still not 100% sold on the structure). With a flux-like workflow, it's very easy to reason/structure your events and data.. yes events take some extra declaration, but your workflows become a lot easier.
Actually, I worked for a the UC system where all salaries were made public in an easily searchable database. The sky didn't fall.
My only real problem with it is that I feel it puts the UC system at an unfair disadvantage. Imagine if you could look up salaries for your competitor's workers, but they couldn't look up yours? This is essentially the situation for UC relative to a lot of private universities, even though massive amounts of government funding flow into private universities (with a tax exemption on endowment growth, too).
I actually think that all companies that make use government subsidies program should be required to disclose employee salaries the same way that state government do. And I absolutely do think that the H1B program should count as a government subsidy (Milton Friedman recognized it as a subsidy, because it was changing the rules for only a certain segment of the economy).
Overall, I actually think it would be beneficial to publish all salaries, and I really don't think it would cause the kind of problems people worry about. It would also real even the playing field between employers and employees.
Think about it this way - all real estate transactions are made public. But imagine if you were bidding on a house, but only the real estate agents actually knew what every house in your neighborhood had sold for. You were forced to go by little bits of gossip here and there. You'd be at a terrible disadvantage!
I worked for the State of Virginia a some years ago, and at least two years running the local paper did a FOIA request for everyone's salaries and then published anyone earning above the median in a searchable database. ( http://www.richmond.com/data-center/salaries-virginia-state-... )
Many of my coworkers were upset, but the only real practical result I saw was that some people that were underpaid relative to their peers had evidence of it, and those that were overpaid relative to their peers were held to more responsibilities by others.
On the whole my experience was positive with it. (That said, your point that we have varying levels of "justice" is completely valid).
I am an advocate for open salaries, because it eliminates or helps to eliminate the information asymmetry between employers and employees, that absolutely favors the former. Partially giving this information just deepends the information asymmetry between colleagues.
This needs to be transparent like it or not. These companies are arguing that there isn't any talent for them to hire so they have to get someone from overseas. If this information wasn't publicly available they would be paying some of these guys 9 dollars an hour.
That is senseless, you dont need citizen control to check that the salaries are prevailing wages, that is a job that can be done by the government with multiple different agencies at a very low level of cost or risk. Also, it doesnt make sense because it doesnt include US employees salary of the same companies which is what you need to make that fair/unfair comparison. Even worse, the immigrants themselves can't make that check, which is the most important one you need.
The fact that this information is available to citizens is a purely exclusion measure, that makes clear that immigrant workers don't have the same rights as US citizens.
The fact that this information is available to citizens is a purely exclusion measure,
No it's not. The records in question aren't public because they involve foreign workers. They are public because the records involve a program run by the government.
You obviously don't know anything about the US government. Without transparency there is corruption. Why do you think everyone is upset over the Trans-Pacific Partnership deal being done in secret? The US government can not be trusted.
The only information in this case relevant to check is the salary itself. You can avoid the company name entirely, have only title and location, and get that information as well, and that protects the identity of foreign workers considerably.
This not an 'immigrant' thing, it is a H1B requirement. When I initially began working in the US under Trad NAFTA there was no such requirement, but when I changed to a permanent track the job had to be posted. It is part of the process to prove that there is not a qualified person already available to fill the position. The whole underlying proposition of H1B is there is a shortage, disclosing the salary is just part of the process of proving it, which falls to the company making the petition. Really, I never gave it a second thought.
Well, I suppose that if the employer and employee couldn't normally work together but had entered into a special arrangement with the government dictating (among other things) that their salary be made public in exchange for being able to employ/be employed, I'd be just fine with it.
Yes it could. You would either need to have redis slave replication setup and then only load balance your read-replicas, or else you would need to use sticky sessions to always send requests back to the right node.. I'm not sure if sticky sessions is possible with TCP loadbalancing in nginx but I assume it is.
I'm disagree with his comparison of scala community to "league of legends". I've found the scala community, especially, the #scala IRC to be friendliest so far. Folks are always there to help you out irrespective of your level of proficiency with language or programming in general
I second that, I don't know where he went, but at least in reddit.com/r/scala people are very nice and helpful, and Martin Odersky visits there frequently and answers questions. I was in touch with several people in the community and from typesafe / EPFL and really don't know where the league of legends comparison comes from.
In any case, I do suggest anyone who haven't seen or tried Scala to give it a shot. It's a fun and productive language. And the community is pretty great in my experience...
I've found the Scala community to be exceptionally helpful and friendly in general, with the occasional you're doing it wrong we know better vibe from a minority. Most of the contention seems to be on forums like reddit programming where 1 or 2 specific (and disproportionately active) users have almost turned Scala-bashing into a profession.
Yes, you right, Scala comunity tend to be friendly and helpful when you want to learn something. But only until you criticize something about Scala :) That's at least my experience. After some critique I even had some private emails saying that "yes, I feel the same" but nobody dared to step in and say it publically. Maybe they just learned the lesson.
