Improving interview processes is great! What do you think are the best ways to interview candidates, as opposed to whiteboarding and code challenges?
2,147 karma · joined November 2, 2012
Yup. I've pretty much only ever had bad experiences with AirBnB. At this point I've just stopped using them. There's a lot to be said for the predictability, comfort and service of a good hotel.
It's interesting that the reasons they cite for choosing Kubernetes over alternatives are entirely driven by 'developer experience' and not at all technical. It shows how critical community development, good documentation, and marketing are to building a successful open source project.
I am shocked, shocked I tell you, that you would suggest any ICO investor might let their financial position influence the way they talk about cryptocurrencies. These people are visionary investors who selflessly pour their resources into ICOs, not mere speculators looking to make a quick buck on a greater fool. /s
You make a really good point. I'm genuinely excited about blockchains and cryptocurrencies, but it's so hard to find writing about it that isn't thinly veiled asset pumping.
Maybe Google was much better at some point in time in the past, but I haven't noticed any meaningful difference these days.
Google's advantage is their massive brand awareness. They've done an outstanding job with brand marketing - positioning themselves as smart and nerdy, so people are inclined to subconsciously think of them as highly performant, even without any evidence to back it up.
That's simply not true. You can accidentally run up huge bills with EC2 instances too. One typo in your CloudFormation templates could spin up a ton of reserved p2.16xlarge's.
Of course, if you consider EC2, and other AWS services, to be "serverless" too - you're not physically managing your own racks after all - then, yeah, fair enough, it is a problem exclusive to these "serverless" IaaS/PaaS providers.
There is a huge amount of cheap, cookie-cutter housing in American suburbia. In fact, I suspect a large majority of single family suburban houses built in the last 50 years are rubber stamp clones from homebuilder planbooks.
Have you ever lived in a high-rise surrounded by open space? A lot of people, myself included, really like it.
You're stating your own personal preference as if it were some universal fact.
You also seem to have a limited understanding of housing design. For example, lots of Corbusier-inspired high-rise developments have shops and restaurants mixed in among the parks and buildings.
I suspect the bulk of the complaints people have with high-rise housing projects for low-income residents in the US are driven more by the policies and operations of low-income housing - lack of maintenance, poor security, etc. The design model has worked out quite well for higher income residents in plenty of places - even in the US, for example, near south Florida beaches.
Did you read the article? They were looking at what makes some existing CEOs more successful than other CEOs. Nowhere did they say these traits were what allowed people to become CEOs. In fact they kind of said the opposite - boards tend to over-index on different traits, like overt confidence and extroverted charisma, when hiring.
Ben Kehoe, who works at iRobot, has written quite about using serverless in production. [1] So has Paul Johnston. [2]
I've been curious about serverless adoption too, and I've thought about doing more structured research and writing. So I'm curious to know what kind of content you're interested in.
My impression is that a lot of companies are using bits and pieces of serverless tech/architectures here and there around the edges - for some data processing pipeline, for an internal tool, for a few supporting services - but very few companies have a 100% serverless stack.
[1] https://medium.com/@ben11kehoe [2] https://medium.com/@PaulDJohnston
You can say the same thing about ops people being "dumb command line users who can't debug assembly language."
Higher abstractions and fewer reinvented wheels are one of the major overarching goals of computing. If I never had to type "sudo systemctl" ever again for anything but a fun antique restoration project then I would be very happy.
That said, I completely agree that for any company other than maybe some early-stage startups to go completely NoOps today, in 2017, is not a good idea.
That's simply not true. Uber's success is due to being in the right place at the right time and executing well in the early years.
The combination of smartphones and widespread trust in online reviews as a system of enforcing good behavior were what made ride-sharing as we know it possible. Uber understood the real value prop - a seamless, low-stress way to take a car from A to B is what matters; a feel-good community "sharing" vibe only gets you so far. And they developed their business in a smart way - it's a commodity product, so you have to become the default in people's minds (like Xerox or Polaroid before), that means build brand awareness and saturate as many markets as possible as quickly as possible.
TK being an asshole is orthogonal to their success. There's a good argument to be made that it actually has held them back and limited their success. Given the size of the market why are they only a $70B company instead of a $200B or $1T company by now?
I'm sure moderating comments is hard. But when it's done well comments are great.
I agree with that statement - dedicating significant energy to finding new music is a fairly niche hobby.
However, I don't think easy-to-find necessarily equals label-owned music.
I often listen to music for hours at a time in the background while I'm working or relaxing at home. I'll aim for an artist or mood and then I'm happy to let 'related tracks' from artists I've never heard of play indefinitely. If there's a track I really like I'll look at who the artist is and make note. I listen to a ton of "indy" music this way. Mostly, I never know who the artist is. Sometimes I discover new artists. All of this is very low effort on my part.
In fact, it would be significantly more effort to listen to megastar pop music or classics. I'd have to find a way to play the tracks - YouTube most likely, which means a ton of poorly thought out ads, or else paying for the songs directly, which usually is just slow and annoying.
I'd wager the biggest hours of music listening are for background music - at work, in stores and restaurants, while studying, while lounging around the house. I'm sure some people always want to listen to the same ten albums on repeat every day, but I suspect most people are driven more by ambiance. Indy music will do that job just fine.
Of course people will always want to play nostalgic hits. But I suspect that's a smaller driver of music consumption by hour of attention (or at least partial attention) than many people assume. That means the labels have way less power than people assume.
Man, now I really want to build what SoundCloud should have been.
Twitter needs to realize that there value prop is the community using it and not the app itself. They need to make radical design and product changes to make for a better user experience if they want to grow. The vast majority of internet products evolve significantly as they grow, surfing the wave of changing user behavior and taste as they reach new markets.
This. I also suspect that for developers whose first language - or primary language these days - is JavaScript it's a lot more comfortable to reach for a Node backend framework when they need it. Also, Go has become pretty popular for somewhat more custom or complex backend tasks. Plus, there are more and more high-level third-party services offering different pieces of backend functionality.
Sure, sometimes they do. But more often than not they introduce more problems than they fix, or at best, they fail to fix the original problems.
Most of the benefits that people who choose microservices are looking for come more from good design and are completely orthogonal to microservices vs monolith. For example, separating code out into separate repos and deployments doesn't automatically separate concerns. But microservices inherently introduce a lot of challenges in orchestration, managing state, testing, deployment and all kinds of things that are much easier with a monolith.
Microservices is one of the most cargo-culted ideas in software development these days. I suspect there will be a backlash against it before too much longer. Will there be a resurgance of interest in Rails? Probably not. I suspect something at a much higher abstraction level will take over.
My sense is that for a small team a microservices architecture might be more trouble than it's worth, but I can definitely see how some kinds of applications - or even kinds of teams - it could be a good fit.
When I sign up for a service like Code Climate it's very clear that I am giving them access to some of my code. I also have easy control over what code they can see. They are honest and upfront about what they are doing and why.
Kite has been trying to hide what they are doing, with the goal of tricking developers into doing things they otherwise wouldn't. They're taking advantage of the huge amount of trust in the open source community. Kite must know that abusing this trust has a high chance of hurting the community, but they don't seem to care, as long as they can make a quick buck or two for themselves.
A lot of people here really cherish that trust and goodwill among strangers in the open source world, and are understandably pretty pissed when someone comes along and messes with it.
The bottom line though is being honest and upfront with developers. I suspect Kite could have been a bit more forward about what they were doing and the developer community would have reacted with much less outrage.
That said, you might want to add a few sentences describing VisualTips, and maybe the backstory, on your submission. A lot of people click into the comments to get a bit more context and decide whether or not they actually want to click into the submitted item itself.
Also, it would be helpful to have some kind of visual description on your homepage. I have a pretty good image in my mind from the text, but for such a _visual_ product it would be really helpful to see screenshots or, even better, a gif of it in action. Those visuals would likely help people get more excited about it.