You must be a US citizen to work for my company. No "US Persons" (visa holders) or foreigners allowed.
You have to be eligible for a Secret security clearance. You don't have to get one if you don't want to as there is usually plenty of uncleared work to go around, but you have to be eligible in case that goes away and we need to put you in for a clearance.
We cannot find qualified applicants.
I've had this conversation many times on HN so here are some preemptive responses:
No, we don't make weapons for the military. Well, we do but not my part of the company. The most harmful thing the products I build do is quantify in precise detail how climate change is dooming us all.
No, our positions aren't ghost positions.
Yes, we are willing to train someone who is motivated. We won't re-teach linear algebra to a developer applicant but we will pay a tech writer to go to school nights/weekends to get a degree in engineering (me, I did that).
Yes, we have extensive high school and college work-study/internships and participants make $72k/yr. with full benefits for the duration of the program. That pipeline is actually successful.
No, you can't work remotely. You (even programmers!) have to touch the things we build in order to build them and nobody has an ISO certified clean room in their house.
Yes, we pay well.
No, we don't pay as much as Meta. We build components for satellites that have been sold to space agencies and purchased by various departments/ministries of the environment, not your personal information to advertisers-- one party has more money to spend than the other.
We have shortages in mech/EE/Aero, shortages in software, and critical shortages in engineering technicians.
One issue is that we expect programmers to remember linear algebra and have more than the ability to shovel frameworks on top of each other until a phone app comes out the other side.
Regarding holepunching, our approach is a bit less pure p2p, but has quite good success rates. We copy the DERP protocol from tailscale.
I am confident that we have a better story regarding handling of large blobs. We don't just use blake3, but blake3 verified streaming to allow for range requests.
Also I wrote my own rust library for blake3 verified streaming that reduces the overhead of the verification data. https://crates.io/crates/bao-tree
I tried to get on their discord at https://veilid.com/discord, but I get an invalid invite. You know a better way to get in touch?
thanks for the links, i will get in touch personally when i try ir0h :)
They seem to do their own streams, while we are adapting QUIC to a more p2p approach. Also the holepunching approach seems to be different. But I would love to get more details.
this was the presentation at DC'31. i will also check out iroh! thanks for working in building something in this space, it is much much needed!
It is a set of open source libraries for peer to peer networking and content-addressed storage. It is written in rust, but we have bindings to many languages.
One part of iroh is a work in progress implementation of the willow spec. The lower layers include a networking library similar to libp2p and a library for content-addressed storage and replication based on blake3 verified streaming.
Most iroh developers have been active in the ipfs community for many years and have shared similar frustrations... See this talk from me in 2019 :-)
wired: ifconfig [if] autoconf up
wireless: ifconfig [if] join [ssid] wpakey [pass] autoconf up
Consistent documentation existing in man ifconfig. The sad thing is that Linux used to be designed not evolved.