Actions
Forum Thread Details
  • Replies 13 replies
  • Subscribers 2563 subscribers
  • Views 1371 views
  • Users 0 members are here
Related

Rules you should probably follow when applying for a RoadTest?

hugohu

If I'm incorrect for any of these, please correct me since I haven't actually been accepted but from what I've read these are some problems.

 

a. If it's too hard, you go ask someone if you've already applied, such as Mr. Scasny, I think that he might be able to help you find a mentor or something.

b. Read the documentation and start-up guide. For instance, I'm not applying to the STWIN iOT thing since I wouldn't be able to use it very much, since it needs windows, (I only have a VM), and also because I still haven't figured out how you program it. After reading the guide 10 times. And, not even the language you use.

c. Remember you skills, and what skills you need. If it's a FPGA board, and you have no idea what FPGA is, you probably aren't going to be able to use it and end up returning it.

d. Try to actually find what you could do with it instead of looking at the price. Don't apply for something that's 6000 dollars and something you don't know how to use and don't need. If I don't need a FPGA then I'm not going to apply for one. Not even if it's 1700 dollars.

  • My personal rule is to do what you said you would when applying. Don't over promise to "win" the road test and then fail to deliver what you said you would.

  • in reply to Fred27

    Deffo.

     

    I don’t think there’s an ‘art’ to it, work within your means and make it interesting.  There’s nothing wrong with setting stretch goals as long as you’re happy to put the effort in.  I think people on Element14 want interesting and technical reviews to give them an insight into the item and a good idea of how they could use it.

  • Like the 2 replies above, I think it's simpler than your points:

    "Show that you understand what's being tested, and explain how you will test it."

    If you have a unique angle, your application may jump out of the masses.

    If you apply for an unpopular one, your chances are higher. And they sometimes are the most interesting ones.

  • I don't think there's a prescriptive set of rules that cover everything, but in addition to the above, I'd say:

    • Follow the instructions on the RoadTest application and fill everything in. Incomplete applications are ineligible.
    • Put some thought into your application to see what you can offer in terms of a review, how it fits your interests/passions/capabilities and what you can offer the community and the manufacturer. Think of how it might be different from other applications.
    • Do your research beforehand - if you go through the documentation before you apply, you will have a better idea of how a given product distinguishes itself from others in the product segment.
    • Be realistic about what you can do in two months - don't promise what you can't do within the period, but also don't promise tests where you don't have the equipment or capabilities to perform the testing - the RoadTest program generally will not provide additional parts/equipment beyond that stated in the RoadTest to help you.
    • Demonstrate your technical background and problem-solving capabilities in your application.
    • You can apply for multiple RoadTests, but don't expect to be awarded more than one RoadTest at a time.
    • Don't try to game the system - e.g. putting in multiple applications under different usernames for example.
    • Participate in the community in an active way and demonstrate your other skills by creating content such as blogs, videos, etc. Ensure you login regularly - this provides some confidence you are active and serious.
    • If you do win a RoadTest, make sure you deliver your review within the deadline (two-month) period or risk losing access to the RoadTest program entirely. In case there is an issue, contact Randall Scasny as soon as possible to negotiate any changes.
    • If you do win a RoadTest, Randall will e-mail you and you must reply within 24 hours, otherwise you will lose your offer.

     

    Additionally, I've provided a reply to you regarding programming the STWIN Sensor Tile based on the available documentation  - by the way, it's very likely the language used is C.

     

    - Gough

  • in reply to Gough Lui

      wrote:

    If you do win a RoadTest, Randall will e-mail you and you must reply within 24 hours, otherwise you will lose your offer.

    I saw the email telling me that I had been selected for the RTM3004 road test just as I was about to head out of the office for a week's holiday. image

  • in reply to Fred27

      wrote:

       wrote:

    If you do win a RoadTest, Randall will e-mail you and you must reply within 24 hours, otherwise you will lose your offer.

    I saw the email telling me that I had been selected for the RTM3004 road test just as I was about to head out of the office for a week's holiday. image

    I wouldn't want to miss out on that e-mail. On the plus side, you had something to look forward to on coming back from your week's holiday image.

     

    - Gough

  • in reply to Gough Lui

    I created this discussion to aid my "did you create a discussion part" in the application and now I am learning life lessons!

  • in reply to Gough Lui

    About the 24 hour limit- why 24? Sometimes I go 48 hours without checking email.

  • in reply to hugohu

    That's not my call - that's 's rule and it's probably because once RoadTest finalists are selected, they don't want any significant delays in contacting the finalists and getting their agreement so the items can be shipped and the RoadTest commenced. Speaking of which, if you have any queries related to the program, Randall is the person you should be asking.

     

    - Gough

  • in reply to hugohu

    Absolutely nothing wrong with that ... isn't that what discussions are for image ?

     

    - Gough