Hacker News new | past | comments | ask | show | jobs | submit login

Darkhive.com | United States | REMOTE | Full-time | $150-220k + early shares, employee #10-15

There are two kinds of drone companies on the market. DJI and everyone else you haven't heard of. If you want to change that, particularly in the US, check us out. We are creating a palm-sized, autonomous drones to help de-escalate dangerous situations.

If ROS2, sUAS, GTSAM, SolidWorks, aerospace, hard realtime systems, and drones are things you're familiar with or interested in, let's chat. Shipped a consumer product in volume? Let's chat.

Maybe you're working an another UAS/Drone company that's larger and want to flex your brain to have more direct impact and ownership of your creations. Apply below and mention HackerNews.

Let's make drones more affordable and accessible to public safety, humanitarian, and defense applications.

- Position can be 100% remote (US Only). Relocation to San Antonio, TX would be awesome.

- We do in person meetings when needed. We are just 14 people.

- We're a startup, but we have funding and contracts. We're all mid-career so we want a sustainable, mature, diverse working environment.

- This position will involve defense work. However, we will never build drones that can harm people.

Hit me up direct at { sturner at darkhive dot com }




Curious about your choice of using ROS. From my experience it works for a proof of concept but slows you down a lot after that.


(Not with the company) My observation is that ROS 2 is the go-to solution for new projects. Established co's have sunk cost in proprietary stacks and tend to spread the "ROS is slow and bulky" meme, but the reality is a sane, seasoned stack that has thousands of contributors offers a time-to-market advantage that is worth more than saving a bit on hardware. Most of the really time-critical code (actuator firmware, video capture etc) is done by C/C++ libraries anyway.

It's parallel to the general situation where Python is at the top of the stack in spite of being dog-ass slow.


ROS2 is also not ROS. I believe they fixed some of the mistakes. I'm not sure about catkin though, it's the worst build system I've experienced. And it sure likes to integrate itself everywhere, making it really hard to move away from it.


The only big change which isn't just churn is changing the messaging system to DDS. My problems with ROS1 aren't related to the implementation details of the messaging system. It's the build system, the difficulty of adding tests, the difficulty of writing deterministic systems with their messages being inserted in the middle of everything, needing to put everything through their messages, and in the end the fact that I can't use ROS for a system and non-ROS for another system and have them work together nicely.


Couldn't have put it better.

ROS metastasizes in your system.

I'm anti-framework in general though. I think it's better to get a good build system and a good messaging library and do your own stuff.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: