anon2020dot00
Joined 5 years ago
Joined 5 years ago
I'd argue that people who open-source code expect other people to learn from it in a small way of snippets and that constitutes fair-use.
For open-source projects, CoPilot is in the realm of fair-use for snippets but it can be mis-used just like Github can be mis-used if someone blatantly copies a repository.
But at that point, it would be just like someone cloning the Github code without following the license and in that case, it should become obvious that there is a clear violation harming the creators. But in most use cases of CoPilot, where-in people are just using it to build their own product, I doubt there is a cause for damages.
He hasn't mentioned any struggles to deliver or challenges with his past tasks; it just comes across that he is much less busy than his peers and he is wondering why. Maybe he is not liked and that's why I mention freezing him out, I guess one can classify that as a "communication issue" or the other possibility is that it just takes time to be integrated in a big company like other commentators have said.
By freezing-out, I don't mean that his teammates are actively hostile against him but just that maybe they don't trust him yet to give more tasks, just like how any newcomer is treated with some unfamiliarity at the start. I guess that counts as a "communication issue".
You seem to like to point the blame at the employee only while others have mentioned that it just takes time to build trust and to be given tasks and others have mentioned that he might have already lost the trust of his teammates which I guess does point to a failing in his part if so.
In a big company, there is also usually more room to coast and that is another possibility in that the manager is just not pushing that much and that is normal for a new-hire. I think there are just more possibilities than the fact that the employee is incompetent which seems to be your immediate conclusion without sufficient evidence.
At this point, he is being frozen-out by his teammates or maybe it is just normal ebb and flow like usually newcomers take some time to be integrated in a big company but it depends.
Your message sounds like a spiel from a CTO given to his employee in order to motivate them and it's like you used this opportunity to practice a spiel that you have to give instead of looking at the OP's situation.
The difficult part is creating a deck and crafting the answers and questions. Because usually this is a time-consuming process. So if it was a community-effort then it would be a win-win.
This is probably not an original idea and if anyone knows already where to find such decks, that would be cool.
Most regrets stem from poor information or prediction capability such as the story of the one that went into game development during college instead of a better course or the one that didn't focus on programming until late in life.
I think the biggest regrets doesn't come from lack of prediction or information but just from the lack of willingness to take risks.
Life is finite and so whether we take risks or not, we all end-up in the same place; but to those who took risks and it paid-off, the journey is much more pleasant and the reckoning at the end is much more fruitful.
Of course this is just a platitude and isn't really that helpful, since there are a lot of risk-takers that just end-up dead or worse-off.
But the idea is that a person can't win by not taking risks since we're all dead anyways and so maybe a calculated risk is the answer.