Hacker News new | past | comments | ask | show | jobs | submit login

> In our team, we try and prevent anyone from working on the same code, product or dataset for more than three months. This period is a bit arbitrary and perhaps too short for larger companies. But we generally believe in fast rotations.

To contrast, here is Rich Hickey on Mastery: (https://gist.github.com/prakhar1989/1b0a2c9849b2e1e912fb)

A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.




TL;DR: "I work at a startup that provides aids for learning new things aimed at developers. Here's a 1000 words advertisement."

It may very well loving learning as a person, but the whole pice is incredibly onedirectional and single minded.

What about build automation? Testing? Deployment of all those unrelated technologies?

What about every line of code becoming "legacy" in six month?




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

Search: