Not when the teams can't bring anything from those projects into F1.dans79 wrote:Their is a big difference between someone bring knowledge attained during the course of their career, and teams trying to intentionally circumvent the budget cap by putting people on very technically relevant projects that live outside the cap.
If someone working on a hypercar project, then that counts as "knowledge attained during the course of their career" too. In fact, i would like for you to explain how it doesn't. Working on a Hypercar-project isn't a part of your career or what?
As long as you can't bring in any concrete data or designs from these projects, then the only thing teams are doing then is essentially training their staff outside of the cost cap. And in that case, i fail to see the distinction. Any expertise you impart on any individual, including via training, belongs to that individual. It doesn't belong to the team. It's the individuals expertise. And it doesn't really matter where that experience comes from. I fail to see how improving the expertise of engineers is any different than hiring someone who has, say, previous experience working in F1 (typically for previous teams), beyond the fact that it's potentially more expensive:
- You still have to pay them a wage that matches their level of expertise
- They can take their expertise elsewhere if they like (which is always a risk teams have to deal with).
- Anything they do outside of F1 doesn't help the F1 team at the given moment. If an engineer is working 50% in F1 and 50% elsewhere, that's 50% of the time he isn't contributing to the F1 project.
Så unless you would like to argue that you believe that teams are actually sneaking data into the F1 projects in clear violation of the rules, then i don't think you've made a compelling case to why these side projects are an issue.