Earlier quoted context omitted.
> "only use things that have been around for at least three years" Yikes. I can understand the desire to mitigate churn, but following this advice would be career suicide. Trying new things is essential.
Trying is not the same thing as advocating for and implementing products features using unproven tech. Ive been in this industry nearly 40 years and I have seen many many people push new tech and later fail to deliver and suffer the consequences. Experiment where it doesnt matter, everywhere else boring and old is a virtue.
New MCP Roadmap
181–183 of 183 posts
Re: New MCP Roadmap
#182Earlier quoted context omitted.
> "only use things that have been around for at least three years" Yikes. I can understand the desire to mitigate churn, but following this advice would be career suicide. Trying new things is essential.
Three years is nothing, what kind of work do you do where you need something released in the last three years? And I’m not OP, but I would assume the senior developers made a distinction between try and use.
Re: New MCP Roadmap
#183Earlier quoted context omitted.
> "only use things that have been around for at least three years" Yikes. I can understand the desire to mitigate churn, but following this advice would be career suicide. Trying new things is essential.
Keeping up with changes is valuable. At the same time, it's often smart to avoid putting things into production that haven't matured or demonstrated staying power. Or, to badly mangle Postel's law: Be liberal in what you learn, and conservative in what you deploy