That's quite enlightening. My comment was due to my industry-related naiveté. I thought a principal PM has the final say on both the features and the business side of a product. I didn't realize VPs add additional filters.
This app has a UI flaw. My friend was testing how cash request works. Her request arrived when I was already inside the app (just exploring it). And without giving me even a warning it started the process of verifying my SSN and all that. When the process was over, I had apparently given the green light to transfer the money with no recourse possible. This is stupid and frankly dangerous. I understand seamlessness has its prices but the workflow should be adjusted to avoid large cash transfers without giving the person to think about it.
This comes out at a time when I've finally decided to start digging into ElasticSearch. Since it's a side project, I don't have to worry about scaling and management issues. So just from the standpoint of functionalities, is there any advantage of this Search as a Service over an ElasticSearch cluster on Azure's Virtual Machines?
In my opinion, techies make as much of a big deal of outfits as do the finance/business guys. They just do it by shouting about how much they are against dress codes.
Getting one degree in engineering increases the likelihood that the person will be higher than average in her software engineering skills. When you have 1000s of applicants and your approach to everything is fairly conservative compared to the private sector, you won't go out on a limb and hire a dropout unless that dropout has a stellar portfolio of some extraordinary work. And it's the dropout's responsibility to get that work noticed in the marketplace.
This might a stupid question but is this competing with Neo4j or Giraph? I didn't see a mention of comparison with either in the docs. I believe graph data storage and graph processing are two different things - is TItan doing both?
As far as I am concerned (and I suspect it applies to many others), giving up my privacy to a machine that generates customized ads (or even risking losing it to third parties for more ads without my consent) is a much smaller price to pay than the inconvenience of going through paywalls and stuff. This is true especially when there's no guarantee that the article/post/whatever-content being accessed is gonna be of super-high quality. These things have been well captured through theories like Privacy Calculus [0] which basically posit that privacy concerns can often be trumped by the benefits of sharing resulting in a net positive utility.
But if it can be done easily in a high-level language, then the control plane can be integrated better with a lot of applications written in the same language, no? I was thinking if that can serve as an impetus for SDN adoption.
I'm thinking of the implication of something awesome like this. Hopefully in the long-run it will boost the likes of light LTE-enabled Chromebooks, at least for tech professionals. That of course requires high-speed LTE infrastructure and ISP backbones.
Your "userland TCP/IP" comment got me excited and I started digging around. I wonder if there's some benefit in trying to port something like TCP Daytona [1,2] in a high-level language like Python. I'm curious if that will somehow advance the adoption of SDNs.
Do they usually pursue side projects that help them get better at their troubleshooting/automation skills or do they tend to keep them complementary to avoid burn-out?
I believe the point being made here is that it is easy to not be in it for the money when you have already made enough money and have achieved enough security and stability. And I personally don't think there's anything wrong with that. It just riles up people when you start pontificating about "show up and try" without context.
Typo in the WaPo article - site reliabilty manager.
Perhaps off-topic but are (Google) SREs the Ops-equivalent of Data Scientists in terms of expectation of cross-domain skills? Mikey Dickerson's LinkedIn profile [0] shows he's a champ in S/W Engg + Distributed Systems + Sys-Admin + what-not. I know calling each of them a "domain" is a bit of a stretch but I couldn't come up with a better term.
Isn't NAT anti-economics? Sure, it helps reuse a limited set of IP addresses, but it also introduces unnecessary layers which doesn't seem cost-effective beyond a certain scale.
I feel like the authors (or someone else) can do a lot more justice to their overall objective (i.e. tease out patterns) by applying some kind of a qualitative content analysis of case studies [0].
BuzzFeed readers are happy. You can feel bad for consumers only when a traditional news outlet turns into a BuzzFeed. I guess the ones that handle that transition delicately will survive.
I'm not sure about the "demand" angle here. Demand is sorted out at the interview stage on a company-level. Once the position has been filled up, it shouldn't be counted towards demand. Hence it should not be subject to lottery. The fact that US has more job opportunities for foreigners compared to, say, Germany in high-tech only means that industry is more thriving in the former. I doubt jobs are created BECAUSE more people wanna move to the US. And by the way, the job search process itself is partly a lottery - it's never 100% about merits.