Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

At a guess: Any team that's working on substrate rather than on code that customers directly interact with won't be a good fit, unless the person has a very flexible view of "customer" and "product." Like, if your team is working on performance improvements for your company's data storage layer, the mindset described in the article won't bring a lot of benefit, I think.


If the storage layers are plenty fast enough and they ask the question that gets their effort redirected to the right thing - that's gold!

Now, as an engineer I gotta say, we need MOAR speed! :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: