231 karma · joined November 5, 2012
Keep searching.
While you don't hit it off with everyone, you'll likely find that there are some amount of folks you meet at conferences, in the community or otherwise that you could see spending time with or getting to know.
Keep updated with those people, follow them on social media, send them articles or links of things that you know they're interested in and call them from time to time.
Beyond that, if you can place facilitator of needs, awesome. You know x person has a need for a person with skill y, and you z person with y skill. Link them up!
This doesn't come without some level of intentionality. The main thing though is to build relationships and community with no expectation of a return. Genuinely do it because you want to model the type of behavior you want to see in others.
There's a lot here: - VHDL for the FPGA - DSP algorithm - A driver for the OS you are building for - Scopes and measurement devices for the hardware bits
If you tried to do it yourself you'd spend more money and have a bad time. I'd recommend getting an FPGA dev board and start there.
[edit]Communication between aircraft is a mix of RF and microwave, likely.[/edit] With regards to the camera helo -> relay helo -> fixed wing -> truck workflow, it's likely based on the ability for the camera helos not being able to 'see' the fixed wing aircraft. For instance, since the tour goes into mountainous areas, the camera helos may go down into a valley or be occluded from the fixed wing air craft at various points in time. Using the relay helo allows the fixed wing to fly a less complex flight plan, reducing potential issues with its link to the trucks.
Finally, having all of this operated by professionals who have many years of experience is required for live production. You just can't tolerate any outages, so things like drones, etc, which require longer iteration cycles for updates in flight plan, etc become less of an option.
Personally, I had pretty bad social anxiety, but worked through it with a therapist and hard work. There aren't any short cuts or magic tricks, it's hard work and it puts you out of your comfort zone.
I'll preface with saying I'm not a doctor, but, I'd avoid mediation unless you have general anxiety and/or depression. There's a lot of evidence that shows that medication and therapy are equally as efficacious for problems like this.
The main problem with doing too much from the start is that the process of defining the governance model of the organization is part of creating the organization. If you want to find people who want to be involved in something like this, it's likely that they want to be involved in the definition of the organization itself, not just part of the building of the outcome of the defined organization.
When building a community, which is effectively what you are doing here, a sense of ownership drives motivation and passion. Try to find others who would share your sense of passions around this and define the structure with them.
Assuming you have a reasonable company and you aren't infringing on any IP or trade secrets, you're probably fine and will get approval. The main thing here is that they don't want an employee releasing something that conflicts with the interests of the business.
People tend to over-inflate these myths and have never actually spoken with company council on the matter.
However, you are more likely to build relationships with individuals who can afford to give you money. You'll likely end up with better terms and you'll have a better experience. I tried to raise through a regional angel program and we backed out as their terms were troubling and their lead fund manager difficult to deal with. I've heard similar stories from others as well.
If you can, find people who care about the field you are starting up in and get to know them. This is also a good litmus test for the potential of your idea.
Quite simply, what do you offer that is unique? Everyone has that thing, find your thing and talk about that.
Intersections are often a great place to start. For example, a carpenter who also is a computer vision engineer and integrates those things. Take two skills you have, slam them together and lean into that.