|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#11
|
||||
|
||||
|
Re: Some changes needed at FIRST IMO
Quote:
Perhaps FIRST needs to have a discussion (either internally or within the broader community) about the degree to which supply restrictions are intended to be part of the challenge, and the degree to which FIRST should be responsible for remedying, or perhaps more realistically, equalizing the impact on teams. After all, it wasn't so long ago that FRC rules mandated that all non-kit parts come from a (short) additional hardware list, or from the Small Parts (now Amazon Supply) catalogue. While that was great in some respects—it was an established supplier with a largely deterministic supply chain—there were unforeseen difficulties like economically and rapidly importing those parts to Canada during an FRC build season. Was it FIRST's responsibility to do something about that, or was it just part of the challenge that 188 should have anticipated? It's hard to say. What is certain is that if FIRST is going to establish any premises about the role of supply constraints, they should be clear about them, and clear about their purpose. The vendor definition in the rulebook is much better than it used to be, but I see it as fundamentally off the mark. It adequately specifies how to verify that an ordinary business is a legal vendor—but there wasn't really much question about those in the first place. The problem is that it fails to cohesively establish how to deal with a vendor that suddenly fails to meet the requirements. Should the vendor be punished or shunned? (How?) Should the team be punished or at least made to realize their error? (That's not very nice, and perhaps only inspiring in the crudest of ways.) Should FIRST bend over backward to accommodate them, even to the extent of bending a rule, or tracking down an alternative supplier? (Impractical if widespread.) I think there's real value in the surprise aspect of the competition, and FIRST needs to continue to be thoughtful about how it leverages that. There's also value in the self-containedness of the season; announce everything early, and you create a great incentive to operate year-round, because of the certainty involved. We'll probably see more design re-use (something that FIRST has managed poorly, due to consistent use of unclear constraints), and more team member burnout as a result. But we might also see many much better robots. I'm not sure if the advantages outweigh the disadvantages, because I don't think FIRST or the FIRST community have coherently established what they believe the metrics for this are. Given that it doesn't seem to be especially urgent that change happen right now, let's have that discussion, before settling prematurely on a solution. Quote:
As for the issue of price controls, it's not inherently a government issue—it's an issue of market failure in general, which can occur as a result of regulatory constraints, monopolies, uninformed consumers, etc.. From an economic perspective, the better lesson is to learn how to identify a market failure, no matter who's to blame. The solution isn't to assume that a price control is inherently a bad thing—especially in a market like FRC, which is clearly not entirely free. Quote:
In the case of equity—because it's a competition, and we typically recognize equity as one of the prime virtues of a well-orchestrated competition—FIRST might be attempting to set prices to ensure parity, instead of pricing in response to demand. This isn't profit-maximizing, but I don't think they particularly care. Alternatively, in the case of utility, FIRST might be motivated to tailor the competition "to each according to his need". This is viable if they have a good model of need—but may well fail if they don't really understand the contingencies upon which need is based. That failure wouldn't be an indictment of need-based service delivery, so much as an indictment of ill-informed policymaking. It's an open question whether it's even practical for FIRST to possess the knowledge needed to make policy on the basis of actual need—but that's worth exploration in detail rather than dismissal out of hand. Nobody ever accused me of being that kind of engineer. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|