4 ms·
Counter-point, these candidates foresee constant frustration and struggles because the company has a culture of NIH. Not saying that's actually the case, but si
by jscheel 5y ago
Counter-point, these candidates foresee constant frustration and struggles because the company has a culture of NIH. Not saying that's actually the case, but since their website is down, it's kinda hard to tell.
- hdhjebebeb 5y agoYeah I can't read the article, but as an applicant this would immediately trigger a yellow flag. If the CTO/director/whoever decided can justify it as a unique differentiator then maybe it's fine and it's a cost of doing business. If they just don't want to deal with k8s because they like their home grown thing, it's going to be a drag on the company long-term to maintain.
- lallysingh 5y ago> If they just don't want to deal with k8s because they like their home grown thing This is another way of saying that they don't want to read too much documentation.
- hamburglar 5y agoYeah I could totally see the director of engineering at my old company gleefully writing a smug blog post about how they don’t use technology X because they don’t go for all the hip new trends (translation: we actively avoid anything trendy even if it’s good, and we have an extreme NIH attitude). As a result, everything from search indexing to queuing to RPC to deployment is 100% homegrown and you need a training course in how to use everything, everything has specific experts that you must consult, and everything is in need of debugging sometimes when it should just be standard tools used everywhere.